watchdog: K3: Add RTI watchdog support
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v2 Latest posting 6/60 of 3 patches 0 repliesNew
- v2 posting 5/60 of 3 patches 0 repliesSuperseded
- v2 posting 4/60 of 3 patches 0 repliesSuperseded
Earlier versions · 4
| Version | Posted | Patches | Replies | Status |
|---|---|---|---|---|
| v2 posting 3/6 | 0 of 3 patches | 0 replies | Superseded | |
| v2 posting 2/6 | 0 of 3 patches | 0 replies | Superseded | |
| v2 posting 1/6 | 3 patches | 0 replies | Superseded | |
| v1 | 3 patches | 0 replies | Superseded |
Patches in v2 posting 6/6 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.
Cover letter [PATCH v2 0/3] watchdog: K3: Add RTI watchdog support
Quoted 77 lines · Jan Kiszka
Quoted 62 lines · Lokesh Vutla
Quoted 59 lines · Jan Kiszka
Quoted 43 lines · Lokesh Vutla
Hi Jan,
Quoted 32 lines · Jan Kiszka
Quoted 23 lines · Lokesh Vutla
Quoted 20 lines · Jan Kiszka
Quoted 18 lines · Lokesh Vutla
Quoted 4 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.Quoted 8 lines
Tested on the AM65x EVM and the IOT2050 (also AM65x-based, upstream
support will be posted soon).Changes in v2:
???? - keep watchdog powered when handing over to Linux ???? - drop unneeded explicit power-on
???? - account for RTI firmware locking the power domainPatch 1 and 3 merged applied.
Quoted 7 lines
Quoted 1 line
Thanks. Still taking workable suggestions for loading the firmware.
FIT image is the one that I can think off. Since SPL is loading the FIT image,
SPL_HANDOFFcan be used to pass on the loadaddr from SPL to U-Boot and U-Boot
can start the remote cores using this info.Quoted 4 lines
OK, just the ensure I got the idea correctly:
???- extend struct
spl_handofforarch_spl_handoffwith the fit image ???? loadaddr that spl is processingYes
Quoted 1 line
Quoted 7 lines
Quoted 4 lines
???- stick the watchdog firmware into the u-boot proper fit image ???? (generated by
tools/k3_fit_atf.shor shipped via the board folder, as
???? in our case)IMHO, not via board folder.
k3_fit_atfis used to generate a53 spl images. MayYeah, right. We also have a fit image for u-boot proper, that confused me.
Quoted 3 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?Quoted 9 lines
Quoted 6 lines
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.
I will definitely try to switch our SPI flash image generation to binman, but I didn't figure out how to use it for appending a binary to u-boot-nodtb.bin.
Quoted 5 lines
To my current understanding of the tool, it is only able to write back the offsets of image elements to a single dtb. That breaks when you have multiple configurations to choose from. I also have to handle
https://github.com/siemens/u-boot/blob/jan/iot2050/board/siemens/iot2050/u-boot.its,
not just u-boot.dtb.
Just updated the branch to use binman for the flash image and also for replacing u-boot.its [1][2]. However, I still don't see how to use it for adding a firmware image into the fit parts AND finding it later on from U-Boot proper. Adding Simon, in case he has some idea.
Jan
[1]
https://github.com/siemens/u-boot/commit/951e5294f14196a502e7fe238c23c49de49b8e29
[2]
https://github.com/siemens/u-boot/blob/951e5294f14196a502e7fe238c23c49de49b8e29/arch/arm/dts/iot2050-boot-image.dtsi
Signature · 2 lines
Siemens AG, Corporate Technology, CT RDA IOT SES-DE Corporate Competence Center Embedded Linux