diff options
author | Simon Horman <horms+renesas@verge.net.au> | 2016-02-24 10:56:32 +0900 |
---|---|---|
committer | Marc Kleine-Budde <mkl@pengutronix.de> | 2016-02-26 08:43:18 +0100 |
commit | 0dfa61bba38513957240660a9cad82dd408789ca (patch) | |
tree | f6231663c7697cbae1eeae25b70f760cd8e0cf87 /Documentation/devicetree/bindings/net/marvell-orion-net.txt | |
parent | 59097ac9b20a0318b2b99b3338c0bb066309583e (diff) | |
download | linux-0dfa61bba38513957240660a9cad82dd408789ca.tar.gz |
can: rcar: add gen[12] fallback compatibility strings
Add fallback compatibility string for R-Car Gen 1 and Gen2.
In the case of Renesas R-Car hardware we know that there are generations of
SoCs, e.g. Gen 1 and Gen 2. But beyond that its not clear what the
relationship between IP blocks might be. For example, I believe that
r8a7779 is older than r8a7778 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: Rob Herring <robh@kernel.org>
Acked-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
Diffstat (limited to 'Documentation/devicetree/bindings/net/marvell-orion-net.txt')
0 files changed, 0 insertions, 0 deletions