diff options
| author | Fabrizio Castro <fabrizio.castro.jz@renesas.com> | 2022-11-07 16:50:27 +0000 |
|---|---|---|
| committer | Geert Uytterhoeven <geert+renesas@glider.be> | 2022-11-08 14:33:09 +0100 |
| commit | 2ac909916b520df09a23f152bb9016d7b892b496 (patch) | |
| tree | 4ba22772a158d9c2d175f2aac9e0727ba80f8415 /tools/perf/scripts/python/exported-sql-viewer.py | |
| parent | 4662d6e8c9b0035581ffc31cab80ea5963bd9f24 (diff) | |
arm64: dts: renesas: r9a09g011: Fix I2C SoC specific strings
The preferred form for Renesas' compatible strings is:
"<vendor>,<family>-<module>"
Somehow the compatible string for the r9a09g011 I2C IP was upstreamed
as renesas,i2c-r9a09g011 instead of renesas,r9a09g011-i2c, which
is really confusing, especially considering the generic fallback
is renesas,rzv2m-i2c.
The first user of renesas,i2c-r9a09g011 in the kernel is not yet in
a kernel release, it will be in v6.1, therefore it can still be
fixed in v6.1.
Even if we don't fix it before v6.2, I don't think there is any
harm in making such a change.
s/renesas,i2c-r9a09g011/renesas,r9a09g011-i2c/g for consistency.
Fixes: 54ac6794df9d ("arm64: dts: renesas: r9a09g011: Add i2c nodes")
Signed-off-by: Fabrizio Castro <fabrizio.castro.jz@renesas.com>
Link: https://lore.kernel.org/r/20221107165027.54150-3-fabrizio.castro.jz@renesas.com
Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>
Diffstat (limited to 'tools/perf/scripts/python/exported-sql-viewer.py')
0 files changed, 0 insertions, 0 deletions