i2c: rcar: Add per-Generation fallback bindings
authorSimon Horman <horms+renesas@verge.net.au>
Tue, 6 Dec 2016 16:01:28 +0000 (17:01 +0100)
committerWolfram Sang <wsa@the-dreams.de>
Sun, 11 Dec 2016 21:48:53 +0000 (22:48 +0100)
commitad4a8dc3fec6485b18654d1090ef8012fcfc37b8
treeea4789755c3134f89629799925f3dad4f85598cd
parenta55fa9d0e42e31b0292540e6324d481aad307644
i2c: rcar: Add per-Generation fallback bindings

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+renesas@verge.net.au>
Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be>
Signed-off-by: Wolfram Sang <wsa@the-dreams.de>
Documentation/devicetree/bindings/i2c/i2c-rcar.txt
drivers/i2c/busses/i2c-rcar.c