ARM: OMAP2+: hwmod module clock type support
Get series with b4
b4 am [email protected]Versions newest first
- v2 Latest0 of 28 patches 0 repliesNew
Patches in v2 No applies recorded yet
None of the 28 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 [PATCHv2 00/28] ARM: OMAP2+: hwmod module clock type support
Quoted 4 lines · Tero Kristo
Hi,
v2 contains following changes in comparison to v1:
Quoted 15 lines
- Patch ordering changed a bit, clk/ti, mach-omap2, dts patches are now mostly grouped together, with the exception of the introduction of clock helper API, which is needed by everything else. Please note that the ordering must be preserved between mach-omap2/clk-driver/dts to avoid boot problems.
- Dropped hwmod data removal patches for now, this allows booting with either new or old DTS data.
- Fixed a typo in the hwmod clock driver timeout handling, the comparison for timeout againstktime_us_deltawas wrong causing too short timeouts, this was apparent with cpuidle enabled on OMAP4
- Added patch #6 to fetch hwmod main clock based on the hwmod name itself, if found, ignoremain_clk/ clkctrl setup for the hwmod
- Added patch #7 to fix issue in omap2 timer caused by patch #6, with dynamic parsing of main clock, the hwmod must be setup before attempting to accessmain_clk.
What's the general design goal of this series? This cover letter is more like a change and test log instead of an overall argument for why the series should be merged so I'm left to piecing together the commit text from the 28 different patches. I suspect it's to get rid of DT_CLK macros and do something with hwmod in a more generic way, but that's all I got.
Signature · 2 lines
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project