ARM: OMAP: SmartReflex: pass device dependent data via platform data
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 2 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 2 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 0/2] ARM: OMAP: SmartReflex: pass device dependent data via platform data
Quoted 8 lines · [email protected] writes:
From: Jean Pihet <[email protected]>
Remove the device dependent code (ex.
cpu_is_xxx()) and settings from the driver code and instead pass them via the platform data. This allows a clean separation of the driver code and the platform code, as required by the move of the platform header files toinclude/linux/platform_data.
Quoted 6 lines
Note about the smartreflex functional clocks: the smartreflex fclks are derived from
sys_clkand have the same name as themain_clkfrom the hwmod entry, in order for the SmartReflex driver to request the fclk (usingclk_get(dev, "fck")).Based on mainline 3.6.0. Boot tested on OMAP3&4 platforms.
Thanks, queuing this version for v3.8 (branch: for_3.8/pm/sr)
Kevin
P.S. in the future, It helps reviewers and maintainers if there's some versioning in the patches (e.g. PATCH v3 0/2]), especially when updated versions come in quick succession. Thanks.