summaryrefslogtreecommitdiffstats
path: root/virt
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2017-07-11 14:38:30 +0200
committerLinus Walleij <linus.walleij@linaro.org>2017-08-14 15:01:12 +0200
commitdbd1dad2ab8ffca57e0aa386df0d7ec621c26ca8 (patch)
tree6d87d418de756eaa773decaf1364dd9895cb0811 /virt
parent4a5c886e7cc913b60b68825846cd43dcfe7a2be0 (diff)
downloadlinux-stable-dbd1dad2ab8ffca57e0aa386df0d7ec621c26ca8.tar.gz
linux-stable-dbd1dad2ab8ffca57e0aa386df0d7ec621c26ca8.tar.bz2
linux-stable-dbd1dad2ab8ffca57e0aa386df0d7ec621c26ca8.zip
gpio: rcar: add gen[123] fallback compatibility strings
Add fallback compatibility string for R-Car Gen 1, 2 and 3. In the case of Renesas R-Car hardware we know that there are generations of SoCs, f.e. Gen 1 and 2. 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. Also deprecate renesas,gpio-rcar as its name is more generic than its implementation. Signed-off-by: Simon Horman <horms+renesas@verge.net.au> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> Signed-off-by: Linus Walleij <linus.walleij@linaro.org>
Diffstat (limited to 'virt')
0 files changed, 0 insertions, 0 deletions