Skip to content

watchdog: K3: Add RTI watchdog support

Lokesh Vutla u-boot 4 versions New

Get series with b4
b4 am [email protected]

Versions newest first · linked by author and title

  1. v2 Latest posting 4/40 of 3 patches 0 repliesNew
  2. v2 posting 3/40 of 3 patches 0 repliesSuperseded
  3. v2 posting 2/40 of 3 patches 0 repliesSuperseded
Earlier versions · 1
VersionPostedPatchesRepliesStatus
v2 posting 1/43 patches0 repliesSuperseded

Patches in v2 posting 4/4 No applies recorded yet

None of the 3 patches the cover letter announces are in this archive.

Reviews trailers per patch

No Reviewed-by, Acked-by or Tested-by trailers for v2 yet.

Read the v2 thread

Cover letter [PATCH v2 0/3] watchdog: K3: Add RTI watchdog support
Quoted 48 lines · Jan Kiszka
Quoted 36 lines · Lokesh Vutla

Hi Jan,

Quoted 24 lines · Jan Kiszka
Quoted 23 lines · Lokesh Vutla
Quoted 19 lines · Jan Kiszka
Quoted 9 lines · Lokesh Vutla
Quoted 6 lines · Jan Kiszka

This brings watchdog support for the TI K3 SoCs, derived from the Linux kernel, augmented with firmware loading as needed on the AM65x.

Tested on the AM65x EVM and the IOT2050 (also AM65x-based, upstream support will be posted soon).

Quoted 7 lines
Quoted 4 lines

Changes in v2:
??? - keep watchdog powered when handing over to Linux ??? - drop unneeded explicit power-on
??? - account for RTI firmware locking the power domain

Patch 1 and 3 merged applied.

Thanks. Still taking workable suggestions for loading the firmware.

Quoted 8 lines
Quoted 3 lines

FIT image is the one that I can think off. Since SPL is loading the FIT image, SPL_HANDOFF can be used to pass on the loadaddr from SPL to U-Boot and U-Boot can start the remote cores using this info.

OK, just the ensure I got the idea correctly:

??- extend struct spl_handoff or arch_spl_handoff with the fit image ??? loadaddr that spl is processing

Quoted 8 lines

Yes

Quoted 4 lines

??- stick the watchdog firmware into the u-boot proper fit image ??? (generated by tools/k3_fit_atf.sh or shipped via the board folder, as ??? in our case)

IMHO, not via board folder. k3_fit_atf is used to generate a53 spl images. May

Yeah, right. We also have a fit image for u-boot proper, that confused me.

Quoted 7 lines
Quoted 2 lines

be create a new one that packs fit image with u-boot and firmware. Or can you check if binman in u-boot works for you?

You mean, pack the u-boot proper with the firmware? Then we could stick the result in an signed fit image when needed. And I could read the offset of the firmware from the generated dtb - provided binman can deal with multiple configurations like we have.

If that is possible I am okay with it.

Thanks and regards,
Lokesh

Quoted 3 lines

Jan