diff options
author | Simon Horman <horms+renesas@verge.net.au> | 2016-03-07 10:58:41 +0900 |
---|---|---|
committer | Kishon Vijay Abraham I <kishon@ti.com> | 2016-04-29 14:40:07 +0530 |
commit | cde7bc367f09e97deef143ebab3271153d87df00 (patch) | |
tree | 0f25e5e19b34a707e124e7acf1e36952e726b4c9 /drivers/phy/Kconfig | |
parent | 7777cb8ba08dabcab8dc0e91ac0a26dde675edb6 (diff) | |
download | talos-op-linux-cde7bc367f09e97deef143ebab3271153d87df00.tar.gz talos-op-linux-cde7bc367f09e97deef143ebab3271153d87df00.zip |
phy: rcar-gen3-usb2: 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>
Acked-by: Yoshihiro Shimoda <yoshihiro.shimoda.uh@renesas.com>
Signed-off-by: Kishon Vijay Abraham I <kishon@ti.com>
Diffstat (limited to 'drivers/phy/Kconfig')
0 files changed, 0 insertions, 0 deletions