[<prev] [next>] [thread-next>] [day] [month] [year] [list]
Message-Id: <20221107165027.54150-1-fabrizio.castro.jz@renesas.com>
Date: Mon, 7 Nov 2022 16:50:25 +0000
From: Fabrizio Castro <fabrizio.castro.jz@...esas.com>
To: Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Geert Uytterhoeven <geert+renesas@...der.be>
Cc: Fabrizio Castro <fabrizio.castro.jz@...esas.com>,
Magnus Damm <magnus.damm@...il.com>,
Biju Das <biju.das.jz@...renesas.com>,
Wolfram Sang <wsa@...nel.org>, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, linux-renesas-soc@...r.kernel.org,
Chris Paterson <Chris.Paterson2@...esas.com>,
Biju Das <biju.das@...renesas.com>,
Laurent Pinchart <laurent.pinchart@...asonboard.com>,
Jacopo Mondi <jacopo@...ndi.org>
Subject: [PATCH v2 0/2] Fix r9a09g011 specific I2C compatible string
Dear All,
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.
Since it's early days for r9a09g011.dtsi, and compatible
renesas,i2c-r9a09g011 isn't being actively used at the moment,
I think it's safe to change to make compatible strings less
confusing.
v2 - Improved changelogs
Thanks,
Fab
Fabrizio Castro (2):
dt-bindings: i2c: renesas,rzv2m: Fix SoC specific string
arm64: dts: renesas: r9a09g011: Fix I2C SoC specific strings
Documentation/devicetree/bindings/i2c/renesas,rzv2m.yaml | 4 ++--
arch/arm64/boot/dts/renesas/r9a09g011.dtsi | 4 ++--
2 files changed, 4 insertions(+), 4 deletions(-)
--
2.34.1
Powered by blists - more mailing lists