summaryrefslogtreecommitdiff
path: root/arch/arm/boot/dts/r7s72100.dtsi
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2014-09-08 09:27:47 +0900
committerSimon Horman <horms+renesas@verge.net.au>2014-09-09 11:50:04 +0900
commitf401ce481082de6327d12a8dc5528d2f7a4a4445 (patch)
treeec8277972a2cef43dd7ef7c372909d0b9eaae8ea /arch/arm/boot/dts/r7s72100.dtsi
parent37757030b0f9f107cd428ae7dcb34a778a8e5d57 (diff)
ARM: shmobile: r7s72100: Use SoC-specific MTU2 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 r7s72100 MTU2 clock source. Signed-off-by: Simon Horman <horms+renesas@verge.net.au>
Diffstat (limited to 'arch/arm/boot/dts/r7s72100.dtsi')
-rw-r--r--arch/arm/boot/dts/r7s72100.dtsi2
1 files changed, 1 insertions, 1 deletions
diff --git a/arch/arm/boot/dts/r7s72100.dtsi b/arch/arm/boot/dts/r7s72100.dtsi
index 1d28d01c163c..801a556e264b 100644
--- a/arch/arm/boot/dts/r7s72100.dtsi
+++ b/arch/arm/boot/dts/r7s72100.dtsi
@@ -230,7 +230,7 @@
};
mtu2: timer@fcff0000 {
- compatible = "renesas,mtu2";
+ compatible = "renesas,mtu2-r7s72100", "renesas,mtu2";
reg = <0xfcff0000 0x400>;
interrupts = <0 107 IRQ_TYPE_LEVEL_HIGH>;
interrupt-names = "tgi0a";