summaryrefslogtreecommitdiff
path: root/crypto/cts.c
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2017-10-18 09:21:28 +0200
committerDavid S. Miller <davem@davemloft.net>2017-10-20 08:32:24 +0100
commitb4804e0c71c144b673b6c53ca4acfcac6eb98704 (patch)
tree358330761822571f18db0952abddaef3b6fb59ac /crypto/cts.c
parent6c4b2f7e675cf11587182f51adcf0e129005e2f9 (diff)
downloadlinux-rt-b4804e0c71c144b673b6c53ca4acfcac6eb98704.tar.gz
net: sh_eth: implement R-Car Gen[12] fallback compatibility strings
Implement 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> Acked-by: Sergei Shtylyov <sergei.shtylyov@cogentembedded.com> Signed-off-by: David S. Miller <davem@davemloft.net>
Diffstat (limited to 'crypto/cts.c')
0 files changed, 0 insertions, 0 deletions