Skip to contentSkip to conversation

ARM: shmobile: Use SoC-specific clock source compat strings

PATCH New Simon Horman 2 participants 8 messages Sep 8, 2014 – Sep 9, 2014

Subsystems (2)
lore
Share & tools
lore
#0 lore raw

cover ARM: shmobile: Use SoC-specific clock source compat strings

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.

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 string

 arch/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(-)
Signature · 1 line
2.0.1
#1 lore raw

PATCH 1/5 ARM: shmobile: r8a7740: Use SoC-specific 48-bit CMT compat string

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 patch is to make use of the SoC-specific CMT compat string for the r8a7740 48-bit CMT clock source.

---
 arch/arm/boot/dts/r8a7740.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/boot/dts/r8a7740.dtsi +1 -1
index 1067a96..d46c213 100644
@@ -42,7 +42,7 @@
 	};
 
 	cmt1: timer at e6138000 {
-		compatible = "renesas,cmt-48";
+		compatible = "renesas,cmt-48-r8a7740", "renesas,cmt-48";
 		reg = <0xe6138000 0x170>;
 		interrupts = <0 58 IRQ_TYPE_LEVEL_HIGH>;
 		clocks = <&mstp3_clks R8A7740_CLK_CMT1>;
Signature · 1 line
2.0.1
#2 lore raw

PATCH 2/5 ARM: shmobile: r8a7790: Use SoC-specific 48-bit CMT compat string

In reply to 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 patch is to make use of the SoC-specific CMT compat string for the r8a7790 48-bit CMT clock source.

---
 arch/arm/boot/dts/r8a7790.dtsi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/boot/dts/r8a7790.dtsi +2 -2
index a3cd307..d0e1773 100644
@@ -211,7 +211,7 @@
 	};
 
 	cmt0: timer at ffca0000 {
-		compatible = "renesas,cmt-48-gen2";
+		compatible = "renesas,cmt-48-r8a7790", "renesas,cmt-48-gen2";
 		reg = <0 0xffca0000 0 0x1004>;
 		interrupts = <0 142 IRQ_TYPE_LEVEL_HIGH>,
 			     <0 143 IRQ_TYPE_LEVEL_HIGH>;
@@ -224,7 +224,7 @@
 	};
 
 	cmt1: timer at e6130000 {
-		compatible = "renesas,cmt-48-gen2";
+		compatible = "renesas,cmt-48-r8a7790", "renesas,cmt-48-gen2";
 		reg = <0 0xe6130000 0 0x1004>;
 		interrupts = <0 120 IRQ_TYPE_LEVEL_HIGH>,
 			     <0 121 IRQ_TYPE_LEVEL_HIGH>,
Signature · 1 line
2.0.1
#3 lore raw

PATCH 3/5 ARM: shmobile: r8a7791: Use SoC-specific 48-bit CMT compat string

In reply to 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 patch is to make use of the SoC-specific CMT compat string for the r8a7791 48-bit CMT clock source.

---
 arch/arm/boot/dts/r8a7791.dtsi | 4 ++--
 1 file changed, 2 insertions(+), 2 deletions(-)
arch/arm/boot/dts/r8a7791.dtsi +2 -2
index 8a07505..e06c11f 100644
@@ -193,7 +193,7 @@
 	};
 
 	cmt0: timer at ffca0000 {
-		compatible = "renesas,cmt-48-gen2";
+		compatible = "renesas,cmt-48-r8a7791", "renesas,cmt-48-gen2";
 		reg = <0 0xffca0000 0 0x1004>;
 		interrupts = <0 142 IRQ_TYPE_LEVEL_HIGH>,
 			     <0 143 IRQ_TYPE_LEVEL_HIGH>;
@@ -206,7 +206,7 @@
 	};
 
 	cmt1: timer at e6130000 {
-		compatible = "renesas,cmt-48-gen2";
+		compatible = "renesas,cmt-48-r8a7791", "renesas,cmt-48-gen2";
 		reg = <0 0xe6130000 0 0x1004>;
 		interrupts = <0 120 IRQ_TYPE_LEVEL_HIGH>,
 			     <0 121 IRQ_TYPE_LEVEL_HIGH>,
Signature · 1 line
2.0.1
#4 lore raw

PATCH 4/5 ARM: shmobile: r7s72100: Use SoC-specific MTU2 compat string

In reply to 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 patch is to make use of the SoC-specific CMT compat string for the r7s72100 MTU2 clock source.

---
 arch/arm/boot/dts/r7s72100.dtsi | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)
arch/arm/boot/dts/r7s72100.dtsi +1 -1
index 1d28d01..801a556 100644
@@ -230,7 +230,7 @@
 	};
 
 	mtu2: timer at fcff0000 {
-		compatible = "renesas,mtu2";
+		compatible = "renesas,mtu2-r7s72100", "renesas,mtu2";
 		reg = <0xfcff0000 0x400>;
 		interrupts = <0 107 IRQ_TYPE_LEVEL_HIGH>;
 		interrupt-names = "tgi0a";
Signature · 1 line
2.0.1
#5 lore raw

PATCH 5/5 ARM: shmobile: r8a7779: Use SoC-specific TMU compat string

In reply to 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 patch is to make use of the SoC-specific CMT compat string for the r8a7779 TMU clock source.

---
 arch/arm/boot/dts/r8a7779.dtsi | 6 +++---
 1 file changed, 3 insertions(+), 3 deletions(-)
arch/arm/boot/dts/r8a7779.dtsi +3 -3
index d25ed7b..7cfba9a 100644
@@ -261,7 +261,7 @@
 	};
 
 	tmu0: timer at ffd80000 {
-		compatible = "renesas,tmu";
+		compatible = "renesas,tmu-r8a7779", "renesas,tmu";
 		reg = <0xffd80000 0x30>;
 		interrupts = <0 32 IRQ_TYPE_LEVEL_HIGH>,
 			     <0 33 IRQ_TYPE_LEVEL_HIGH>,
@@ -275,7 +275,7 @@
 	};
 
 	tmu1: timer at ffd81000 {
-		compatible = "renesas,tmu";
+		compatible = "renesas,tmu-r8a7779", "renesas,tmu";
 		reg = <0xffd81000 0x30>;
 		interrupts = <0 36 IRQ_TYPE_LEVEL_HIGH>,
 			     <0 37 IRQ_TYPE_LEVEL_HIGH>,
@@ -289,7 +289,7 @@
 	};
 
 	tmu2: timer at ffd82000 {
-		compatible = "renesas,tmu";
+		compatible = "renesas,tmu-r8a7779", "renesas,tmu";
 		reg = <0xffd82000 0x30>;
 		interrupts = <0 40 IRQ_TYPE_LEVEL_HIGH>,
 			     <0 41 IRQ_TYPE_LEVEL_HIGH>,
Signature · 1 line
2.0.1
#6 lore raw

cover ARM: shmobile: Use SoC-specific clock source compat strings

In reply to 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.

This series is based on
renesas-next-20140904v2-v3.17-rc2

The bindings used are proposed in
"[PATCH v3 0/3] clocksource: Document Renesas SoC specific bindings"

Quoted 17 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 string

 arch/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(-)
Signature · 1 line
2.0.1
#7 lore raw

cover 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-rc2

The 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 string

 arch/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.