Thread (3 messages) 3 messages, 3 authors, 2016-12-01

Re: [PATCH/RFC i2c/for-next] i2c: rcar: Add per-Generation fallback bindings

From: Simon Horman <horms@verge.net.au>
Date: 2016-12-01 15:32:08
Also in: linux-i2c, linux-renesas-soc

On Thu, Dec 01, 2016 at 04:18:14PM +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 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.

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.

Signed-off-by: Simon Horman <redacted>
Sorry, I seem to have omitted the driver (C code) portion of this change.
I send v2.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help