ARM: shmobile: Use SoC-specific clock source compat strings
Get series with b4
b4 am [email protected]Versions newest first
- v1 Latest0 of 5 patches 0 repliesNew
Patches in v1 No applies recorded yet
None of the 5 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/5] ARM: shmobile: Use SoC-specific clock source compat strings
Quoted 12 lines · Simon Horman
Quoted 10 lines · Simon Horman
In general Renesas hardware is not documented to the extent where the relationship between IP blocks on different SoCs can be assumed although they may appear to operate the same way. Furthermore the documentation typically does not specify a version for individual IP blocks. For these reasons a convention of using the SoC name in place of a version and providing SoC-specific compat strings has been adopted.
Although not universally liked this convention is used in the bindings for a number of drivers for Renesas hardware. The purpose of this series is to make use of SoC specific clock source strings.
Quoted 19 lines
This series is based on
renesas-next-20140904v2-v3.17-rc2The bindings used are proposed in
"[PATCH v3 0/3] clocksource: Document Renesas SoC specific bindings"Quoted 13 lines
Simon Horman (5):
ARM: shmobile: r8a7740: Use SoC-specific 48-bit CMT compat string
ARM: shmobile: r8a7790: Use SoC-specific 48-bit CMT compat string
ARM: shmobile: r8a7791: Use SoC-specific 48-bit CMT compat string
ARM: shmobile: r7s72100: Use SoC-specific MTU2 compat string
ARM: shmobile: r8a7779: Use SoC-specific TMU compat stringarch/arm/boot/dts/r7s72100.dtsi | 2 +- arch/arm/boot/dts/r8a7740.dtsi | 2 +- arch/arm/boot/dts/r8a7779.dtsi | 6 +++--- arch/arm/boot/dts/r8a7790.dtsi | 4 ++-- arch/arm/boot/dts/r8a7791.dtsi | 4 ++-- 5 files changed, 9 insertions(+), 9 deletions(-)
I have queued up these changes.