diff options
author | David S. Miller <davem@davemloft.net> | 2017-10-20 08:32:49 +0100 |
---|---|---|
committer | David S. Miller <davem@davemloft.net> | 2017-10-20 08:32:49 +0100 |
commit | 6575f35415c406b58e9f6235df4b8272f8696131 (patch) | |
tree | 358330761822571f18db0952abddaef3b6fb59ac /net/tipc/server.c | |
parent | 7a0947e755084b918e33242fd558e55cb443408e (diff) | |
parent | b4804e0c71c144b673b6c53ca4acfcac6eb98704 (diff) | |
download | linux-6575f35415c406b58e9f6235df4b8272f8696131.tar.gz linux-6575f35415c406b58e9f6235df4b8272f8696131.tar.bz2 linux-6575f35415c406b58e9f6235df4b8272f8696131.zip |
Merge branch 'sh_eth-fallback-compat-strings'
Simon Horman says:
====================
net: sh_eth: add R-Car Gen[12] fallback compatibility strings
Add fallback compatibility strings for R-Car Gen 1 and 2.
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 is being adopted for
drivers for Renesas SoCs.
Changes since v1:
* Correct typos in changelogs
* Consistently use tabs for indentation in bindings document
* Enhance readability of description of bindings usage
====================
Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'net/tipc/server.c')
0 files changed, 0 insertions, 0 deletions