Move OMAP2+ over to use COMMON clock
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest1 of 29 patches 0 repliesNew
1 of 29 patches is in this archive. The cover letter announces 29.
Patches in v1 No applies recorded yet
| # | Subject and files | Size | Replies | Applied |
|---|---|---|---|---|
| 4/29 | ARM: omap: clk: use clk_prepare_enable and clk_disable_unprepare | +0 | 3 replies |
Reviews trailers per patch
No Reviewed-by, Acked-by or Tested-by trailers for v1 yet.
Cover letter [PATCH 00/29] Move OMAP2+ over to use COMMON clock
Quoted 17 lines · Paul Walmsley
Quoted 15 lines · Paul Walmsley
Then the branch was PM-tested to determine whether it can suspend and serial-resume properly, and whether dynamic idle works. These tests didn't go so well:
- 3530ES3 Beagleboard here was able to enter retention-idle suspend, and leave it with serial wakeup, but the CORE powerdomain never entered a low-power state. Dynamic retention-idle with serial wakeup never resumed, and the test stopped there:
- 37xx EVM and 3730 Beagle XM fared better; they made it through the whole test program, but the CORE powerdomain also never entered a low-power state:
Quoted 7 lines
Quoted 2 lines
http://www.pwsan.com/omap/testlogs/common_clk_testing_devel_3.7/20120911000742/boot/37xxevm/37xxevm_log.txt
http://www.pwsan.com/omap/testlogs/common_clk_testing_devel_3.7/20120911000742/boot/3730beaglexm/3730beaglexm_log.txtThanks to debugging work by some TI LDC engineers, these two issues have been resolved. Some clockdomain associations had been removed that were necessary for the OMAP power management code to function correctly. The obvious ones have been restored to the clock data, and the branch updated.
That's good news. Does that mean we should try to merge these patches for v3.7 then? Or do we still have issues remaining?
Regards,
Tony