summaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/export-to-postgresql.py
diff options
context:
space:
mode:
authorSimon Horman <horms+renesas@verge.net.au>2017-10-18 09:00:22 +0200
committerUlf Hansson <ulf.hansson@linaro.org>2017-10-30 11:50:39 +0100
commit54839d012d5f98cde2fa102fdcd22e1da661d138 (patch)
tree1dca52d91899e1d3a2a7c507a8c53a63a8db3017 /tools/perf/scripts/python/export-to-postgresql.py
parent95e91ade6900547a74ac8e3ce35213aacfbdd0d3 (diff)
dt-bindings: mmc: renesas_sdhi: add R-Car Gen[123] fallback compatibility strings
Add fallback compatibility strings for R-Car Gen 1, 2 and 3. 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 is being adopted for drivers for Renesas SoCs. Signed-off-by: Simon Horman <horms+renesas@verge.net.au> Reviewed-by: Geert Uytterhoeven <geert+renesas@glider.be> Acked-by: Wolfram Sang <wsa+renesas@sang-engineering.com> Signed-off-by: Ulf Hansson <ulf.hansson@linaro.org>
Diffstat (limited to 'tools/perf/scripts/python/export-to-postgresql.py')
0 files changed, 0 insertions, 0 deletions