Move OMAP2+ over to use COMMON clock
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 29 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 29 patches the cover letter announces are in this archive.
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 11 lines · Paul Walmsley
Quoted 7 lines · Rajendra Nayak
OMAP3 has suspend broken in mainline, so I tested it on an older kernel (3.4-rc4 using my RFC series)
Idle and OFF mode however seem to be broken for a long time, I wasn;t able to get it working even on 3.4 major. See my logs '3630 Beagle-Xm broken idle/off on 3.4' if I am doing anything wrong. I have CPUidle enabled in the kernel config.
Thanks Paul. I re-tested my branch [1] after applying the 32K sync timer fix [2] and using timer based wakeup [3] instead of UART. Both retention and off work fine on my 3630 Beagle-Xm on my CCF conversion branch.
Updated logs can be found here http://pastebin.com/u/rnayak
regards,
Rajendra
[1] git://github.com/rrnayak/linux.git clk-next-omap-3.5-rc2
[2] http://marc.info/?l=linux-omap&m=134000053229888&w=2
[3] http://marc.info/?l=linux-omap&m=134001387702336&w=2
Quoted 3 lines
- Paul