summaryrefslogtreecommitdiffstats
path: root/Documentation/vgaarbiter.txt
diff options
context:
space:
mode:
authorSimon Horman2016-03-07 02:58:40 +0100
committerKishon Vijay Abraham I2016-04-29 11:10:07 +0200
commit7777cb8ba08dabcab8dc0e91ac0a26dde675edb6 (patch)
treea60abf0326b102ccf97795e1f2a72fc25a7a0fc7 /Documentation/vgaarbiter.txt
parentphy: rockchip-emmc: adapt binding to specifiy register offset and length (diff)
downloadkernel-qcow2-linux-7777cb8ba08dabcab8dc0e91ac0a26dde675edb6.tar.gz
kernel-qcow2-linux-7777cb8ba08dabcab8dc0e91ac0a26dde675edb6.tar.xz
kernel-qcow2-linux-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/vgaarbiter.txt')
0 files changed, 0 insertions, 0 deletions