Watchdog: OMAP3: bootstatus fix and changes for the current watchdog framework
Get series with b4
b4 am [email protected]Versions newest first · linked by author and title
- v3 Latest1 of 3 patches 0 repliesNew
- v20 of 2 patches 0 repliesSuperseded
1 of 3 patches is in this archive. The cover letter announces 3.
Patches in v3 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 1/3 | Watchdog: Omap: Changes for the new watchdog framework | +0 | 0 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v3 yet.
Cover letter [PATCH RESEND V3 0/3] Watchdog: OMAP3: bootstatus fix and changes for the current watchdog framework
Quoted 12 lines · Zumeng Chen
Hello,
The following patches based on the 3.5-rc6 from Wim, which focus on:
1. bootstatus fix for omap3,
2. omap-wdt framework update cater for the current framework as Shubhrajyoti comments mentioned.
V3 changes:
Quoted 9 lines
1. New comments updated as Kevin mentioned in the third patch;
2. 3530evm works well,
AM33xx seems work well with the following changes:
+ if (cpu_is_am335x())
+ return omap2_prm_read_mod_reg(AM33XX_PRM_DEVICE_MOD,
+AM33XX_PRM_RSTST_OFFSET) &0x7f;
But since some definitions not ready for am33xx, so I don't give the patch, if they have been updated, feel free to take these.
Did you test it on any of AM33xx platform? If you use linux-omap/master pr linux-next branch as a baseline you should have basic things (except hwmod data) available.
I will test it and send a patch for this on your behalf (if you are ok with it).
Note: Change in convention, cpu_is_am335x() => soc_is_am335x()
Thanks,
Vaibhav