phy: rcar-gen2: add fallback binding
authorSimon Horman <horms+renesas@verge.net.au>
Mon, 7 Mar 2016 01:58:40 +0000 (10:58 +0900)
committerKishon Vijay Abraham I <kishon@ti.com>
Fri, 29 Apr 2016 09:10:07 +0000 (14:40 +0530)
commit7777cb8ba08dabcab8dc0e91ac0a26dde675edb6
treea60abf0326b102ccf97795e1f2a72fc25a7a0fc7
parent5128de85124c728cdbb6b35bd9dc7410f02c0ca1
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>
Documentation/devicetree/bindings/phy/rcar-gen2-phy.txt
drivers/phy/phy-rcar-gen2.c
This page took 0.03199 seconds and 5 git commands to generate.