On Tue, Dec 06, 2016 at 05:01:28PM +0100, Simon Horman wrote: > In the case of Renesas R-Car hardware we know that there are generations of > SoCs, e.g. Gen 2 and Gen 3. But beyond that it's 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. > > Also: > * Deprecate renesas,i2c-rcar. It seems poorly named as it is only > compatible with R-Car Gen 1. It also appears unused in mainline. > * Add some text to describe per-SoC bindings > > Signed-off-by: Simon Horman <horms+rene...@verge.net.au> > Reviewed-by: Geert Uytterhoeven <geert+rene...@glider.be>
Changed '//' comment to '/*' comment and applied to for-next, thanks!
signature.asc
Description: PGP signature
