diff options
author | Simon Horman <horms+renesas@verge.net.au> | 2016-12-06 17:01:28 +0100 |
---|---|---|
committer | Wolfram Sang <wsa@the-dreams.de> | 2016-12-11 22:48:53 +0100 |
commit | ad4a8dc3fec6485b18654d1090ef8012fcfc37b8 (patch) | |
tree | ea4789755c3134f89629799925f3dad4f85598cd /include/acpi/video.h | |
parent | a55fa9d0e42e31b0292540e6324d481aad307644 (diff) |
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>
Diffstat (limited to 'include/acpi/video.h')
0 files changed, 0 insertions, 0 deletions