aboutsummaryrefslogtreecommitdiff
path: root/tools/perf/scripts/python/event_analyzing_sample.py
diff options
context:
space:
mode:
authorSimon Horman <[email protected]>2016-02-24 10:56:32 +0900
committerMarc Kleine-Budde <[email protected]>2016-02-26 08:43:18 +0100
commit0dfa61bba38513957240660a9cad82dd408789ca (patch)
treef6231663c7697cbae1eeae25b70f760cd8e0cf87 /tools/perf/scripts/python/event_analyzing_sample.py
parent59097ac9b20a0318b2b99b3338c0bb066309583e (diff)
can: rcar: add gen[12] fallback compatibility strings
Add fallback compatibility string for R-Car Gen 1 and Gen2. In the case of Renesas R-Car hardware we know that there are generations of SoCs, e.g. Gen 1 and Gen 2. But beyond that its not clear what the relationship between IP blocks might be. For example, I believe that r8a7779 is older than r8a7778 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. Signed-off-by: Simon Horman <[email protected]> Acked-by: Rob Herring <[email protected]> Acked-by: Geert Uytterhoeven <[email protected]> Signed-off-by: Marc Kleine-Budde <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python/event_analyzing_sample.py')
0 files changed, 0 insertions, 0 deletions