From: Shawn Guo <shawnguo@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.nxp.com>
Cc: s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com, linux-imx@nxp.com,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org, Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH] arm64: dts: imx8mn-evk: update i2c pinctrl to match dtschema
Date: Mon, 27 Mar 2023 13:14:09 +0800 [thread overview]
Message-ID: <20230327051409.GO3364759@dragon> (raw)
In-Reply-To: <20230323111924.102541-1-peng.fan@oss.nxp.com>
On Thu, Mar 23, 2023 at 07:19:24PM +0800, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> The dtschema requires 'grp' in the end, so update the name.
>
> Signed-off-by: Peng Fan <peng.fan@nxp.com>
> ---
> arch/arm64/boot/dts/freescale/imx8mn-evk.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/freescale/imx8mn-evk.dtsi b/arch/arm64/boot/dts/freescale/imx8mn-evk.dtsi
> index 8fef980c4ab2..876eb5da5e2d 100644
> --- a/arch/arm64/boot/dts/freescale/imx8mn-evk.dtsi
> +++ b/arch/arm64/boot/dts/freescale/imx8mn-evk.dtsi
> @@ -389,7 +389,7 @@ MX8MN_IOMUXC_I2C2_SDA_I2C2_SDA 0x400001c3
> >;
> };
>
> - pinctrl_i2c2_gpio: i2c2grp-gpio {
> + pinctrl_i2c2_gpio: i2c2gpriogrp {
i2c2gpiogrp
Shawn
> fsl,pins = <
> MX8MN_IOMUXC_I2C2_SCL_GPIO5_IO16 0x1c3
> MX8MN_IOMUXC_I2C2_SDA_GPIO5_IO17 0x1c3
> @@ -403,7 +403,7 @@ MX8MN_IOMUXC_I2C3_SDA_I2C3_SDA 0x400001c3
> >;
> };
>
> - pinctrl_i2c3_gpio: i2c3grp-gpio {
> + pinctrl_i2c3_gpio: i2c3gpiogrp {
> fsl,pins = <
> MX8MN_IOMUXC_I2C3_SCL_GPIO5_IO18 0x1c3
> MX8MN_IOMUXC_I2C3_SDA_GPIO5_IO19 0x1c3
> --
> 2.37.1
>
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2023-03-27 5:15 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-03-23 11:19 [PATCH] arm64: dts: imx8mn-evk: update i2c pinctrl to match dtschema Peng Fan (OSS)
2023-03-27 5:14 ` Shawn Guo [this message]
2023-03-27 10:00 ` Peng Fan
2023-03-27 10:10 ` Fabio Estevam
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=20230327051409.GO3364759@dragon \
--to=shawnguo@kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=s.hauer@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).