From: Matthias Brugger <matthias.bgg@gmail.com>
To: Fabien Parent <fparent@baylibre.com>, Rob Herring <robh+dt@kernel.org>
Cc: devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 4/4] arm64: dts: mediatek: mt8192: fix i2c node names
Date: Wed, 17 Nov 2021 18:09:39 +0100 [thread overview]
Message-ID: <acf4a474-7abf-49e5-aa4e-a25d101fb3d8@gmail.com> (raw)
In-Reply-To: <20211110194959.20611-4-fparent@baylibre.com>
On 10/11/2021 20:49, Fabien Parent wrote:
> Fix the i2c node names to be compliant to the YAML schema. The
> I2C node name should match the following pattern: "^i2c@[0-9a-f]+$".
>
> Signed-off-by: Fabien Parent <fparent@baylibre.com>
Applied to v5.16-next/dts64
Thanks
> ---
>
> v3: rebased
> v2: new patch
>
> arch/arm64/boot/dts/mediatek/mt8192.dtsi | 20 ++++++++++----------
> 1 file changed, 10 insertions(+), 10 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/mediatek/mt8192.dtsi b/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> index c7c7d4e017ae..53d790c335f9 100644
> --- a/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> +++ b/arch/arm64/boot/dts/mediatek/mt8192.dtsi
> @@ -479,7 +479,7 @@ audsys: clock-controller@11210000 {
> #clock-cells = <1>;
> };
>
> - i2c3: i2c3@11cb0000 {
> + i2c3: i2c@11cb0000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11cb0000 0 0x1000>,
> <0 0x10217300 0 0x80>;
> @@ -498,7 +498,7 @@ imp_iic_wrap_e: clock-controller@11cb1000 {
> #clock-cells = <1>;
> };
>
> - i2c7: i2c7@11d00000 {
> + i2c7: i2c@11d00000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11d00000 0 0x1000>,
> <0 0x10217600 0 0x180>;
> @@ -511,7 +511,7 @@ i2c7: i2c7@11d00000 {
> status = "disabled";
> };
>
> - i2c8: i2c8@11d01000 {
> + i2c8: i2c@11d01000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11d01000 0 0x1000>,
> <0 0x10217780 0 0x180>;
> @@ -524,7 +524,7 @@ i2c8: i2c8@11d01000 {
> status = "disabled";
> };
>
> - i2c9: i2c9@11d02000 {
> + i2c9: i2c@11d02000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11d02000 0 0x1000>,
> <0 0x10217900 0 0x180>;
> @@ -543,7 +543,7 @@ imp_iic_wrap_s: clock-controller@11d03000 {
> #clock-cells = <1>;
> };
>
> - i2c1: i2c1@11d20000 {
> + i2c1: i2c@11d20000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11d20000 0 0x1000>,
> <0 0x10217100 0 0x80>;
> @@ -556,7 +556,7 @@ i2c1: i2c1@11d20000 {
> status = "disabled";
> };
>
> - i2c2: i2c2@11d21000 {
> + i2c2: i2c@11d21000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11d21000 0 0x1000>,
> <0 0x10217180 0 0x180>;
> @@ -569,7 +569,7 @@ i2c2: i2c2@11d21000 {
> status = "disabled";
> };
>
> - i2c4: i2c4@11d22000 {
> + i2c4: i2c@11d22000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11d22000 0 0x1000>,
> <0 0x10217380 0 0x180>;
> @@ -588,7 +588,7 @@ imp_iic_wrap_ws: clock-controller@11d23000 {
> #clock-cells = <1>;
> };
>
> - i2c5: i2c5@11e00000 {
> + i2c5: i2c@11e00000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11e00000 0 0x1000>,
> <0 0x10217500 0 0x80>;
> @@ -607,7 +607,7 @@ imp_iic_wrap_w: clock-controller@11e01000 {
> #clock-cells = <1>;
> };
>
> - i2c0: i2c0@11f00000 {
> + i2c0: i2c@11f00000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11f00000 0 0x1000>,
> <0 0x10217080 0 0x80>;
> @@ -620,7 +620,7 @@ i2c0: i2c0@11f00000 {
> status = "disabled";
> };
>
> - i2c6: i2c6@11f01000 {
> + i2c6: i2c@11f01000 {
> compatible = "mediatek,mt8192-i2c";
> reg = <0 0x11f01000 0 0x1000>,
> <0 0x10217580 0 0x80>;
>
next prev parent reply other threads:[~2021-11-17 17:09 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-10 19:49 [PATCH v3 1/4] dt-bindings: i2c: i2c-mt65xx: convert doc to yaml schema format Fabien Parent
2021-11-10 19:49 ` [PATCH v3 2/4] dt-bindings: i2c: i2c-mt65xx: add binding for MT8365 SoC Fabien Parent
2021-11-10 19:49 ` [PATCH v3 3/4] i2c: i2c-mt65xx: add MT8365 SoC support Fabien Parent
2021-11-10 19:49 ` [PATCH v3 4/4] arm64: dts: mediatek: mt8192: fix i2c node names Fabien Parent
2021-11-17 17:09 ` Matthias Brugger [this message]
2021-11-11 14:57 ` [PATCH v3 1/4] dt-bindings: i2c: i2c-mt65xx: convert doc to yaml schema format Rob Herring
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=acf4a474-7abf-49e5-aa4e-a25d101fb3d8@gmail.com \
--to=matthias.bgg@gmail.com \
--cc=devicetree@vger.kernel.org \
--cc=fparent@baylibre.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=robh+dt@kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome