summaryrefslogtreecommitdiff
path: root/Documentation/devicetree/bindings/net/broadcom-bluetooth.txt
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2017-10-18 10:21:26 +0300
committerDavid S. Miller <davem@davemloft.net>2017-10-20 10:32:24 +0300
commit87d9fa647020fb65985ec08826f6c77b9b4084af (patch)
tree8c534df8d9554d791b9f4f9409ac0b9ea7d1d617 /Documentation/devicetree/bindings/net/broadcom-bluetooth.txt
parent7a0947e755084b918e33242fd558e55cb443408e (diff)
downloadlinux-87d9fa647020fb65985ec08826f6c77b9b4084af.tar.xz
dt-bindings: 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. Note that R-Car Gen2 and RZ/G1 have many compatible IP blocks. The approach that has been consistently taken for other IP blocks is to name common code, compatibility strings and so on after R-Car Gen2. Signed-off-by: Simon Horman <horms+renesas@verge.net.au> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> Reviewed-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'Documentation/devicetree/bindings/net/broadcom-bluetooth.txt')
0 files changed, 0 insertions, 0 deletions