On Tue, Oct 17, 2017 at 09:47:44AM +0200, Simon Horman wrote: > 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 being adopted for > drivers for Renesas SoCs. > > Simon Horman (3): > dt-bindings: net: sh_eth: add R-Car Gen[12] fallback compatibility > strings > net: sh_eth: rename name structures as rcar_gen[12]_* > net: sh_eth: implement R-Car Gen[12] fallback compatibility strings There have been a few comments on this series, I will post v2.
