aboutsummaryrefslogtreecommitdiffstats
path: root/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2016-03-07 10:58:40 +0900
committerKishon Vijay Abraham I <kishon@ti.com>2016-04-29 14:40:07 +0530
commit7777cb8ba08dabcab8dc0e91ac0a26dde675edb6 (patch)
treea60abf0326b102ccf97795e1f2a72fc25a7a0fc7 /Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
parentphy: rockchip-emmc: adapt binding to specifiy register offset and length (diff)
downloadlinux-dev-7777cb8ba08dabcab8dc0e91ac0a26dde675edb6.tar.xz
linux-dev-7777cb8ba08dabcab8dc0e91ac0a26dde675edb6.zip
phy: rcar-gen2: add fallback binding
In the case of Renesas R-Car hardware we know that there are generations of SoCs, e.g. Gen 2 and Gen 3. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7790 is older than r8a7791 but that doesn't imply that the latter is a descendant of the former or vice versa. We can, however, by examining the documentation and behaviour of the hardware at run-time observe that the current driver implementation appears to be compatible with the IP blocks on SoCs within a given generation. For the above reasons and convenience when enabling new SoCs a per-generation fallback compatibility string scheme being adopted for drivers for Renesas SoCs. Signed-off-by: Simon Horman <horms+renesas@verge.net.au> Acked-by: Geert Uytterhoeven <geert+renesas@glider.be> Acked-by: Rob Herring <robh@kernel.org> Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Diffstat (limited to 'Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt')
-rw-r--r--Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt8
1 files changed, 7 insertions, 1 deletions
diff --git a/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt b/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
index d564ba4f1cf6..91da947ae9b6 100644
--- a/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
+++ b/Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
@@ -7,6 +7,12 @@ Required properties:
- compatible: "renesas,usb-phy-r8a7790" if the device is a part of R8A7790 SoC.
"renesas,usb-phy-r8a7791" if the device is a part of R8A7791 SoC.
"renesas,usb-phy-r8a7794" if the device is a part of R8A7794 SoC.
+ "renesas,rcar-gen2-usb-phy" for a generic R-Car Gen2 compatible device.
+
+ When compatible with the generic version, nodes must list the
+ SoC-specific version corresponding to the platform first
+ followed by the generic version.
+
- reg: offset and length of the register block.
- #address-cells: number of address cells for the USB channel subnodes, must
be <1>.
@@ -34,7 +40,7 @@ the USB channel; see the selector meanings below:
Example (Lager board):
usb-phy@e6590100 {
- compatible = "renesas,usb-phy-r8a7790";
+ compatible = "renesas,usb-phy-r8a7790", "renesas,rcar-gen2-usb-phy";
reg = <0 0xe6590100 0 0x100>;
#address-cells = <1>;
#size-cells = <0>;