From: Yannic Moog <y.moog@phytec.de>
To: "Frank.li@nxp.com" <Frank.li@nxp.com>
Cc: "Teresa Remmet" <t.remmet@phytec.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"Stefan Riedmüller" <s.riedmueller@phytec.de>,
"festevam@gmail.com" <festevam@gmail.com>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"robh@kernel.org" <robh@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"upstream@lists.phytec.de" <upstream@lists.phytec.de>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"imx@lists.linux.dev" <imx@lists.linux.dev>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>
Subject: Re: [PATCH 3/4] arm64: dts: imx8mp-phyboard-pollux: Enable i2c3
Date: Wed, 22 Oct 2025 06:20:21 +0000 [thread overview]
Message-ID: <8269481ecde6757a18f08ab76e35a8689f48a58e.camel@phytec.de> (raw)
In-Reply-To: <aPZXaC8HL+Rg7rax@lizhi-Precision-Tower-5810>
On Mon, 2025-10-20 at 11:38 -0400, Frank Li wrote:
> On Mon, Oct 20, 2025 at 03:11:24PM +0200, Yannic Moog wrote:
> > From: Stefan Riedmueller <s.riedmueller@phytec.de>
> >
> > On the phyBOARD-Pollux the i2c3 node is used on the CSI1 interface to
> > connect to imaging sensors. Thus define it so it can be easily enabled if
> > required.
> Nit:
>
> The i2c3 of the phyBOARD-Pollux is used ...
Sorry, I can't follow. Would you like me to rephrase the commit message?
Yannic
>
> Reviewed-by: Frank Li <Frank.Li@nxp.com>
>
> >
> > Signed-off-by: Stefan Riedmueller <s.riedmueller@phytec.de>
> > Signed-off-by: Teresa Remmet <t.remmet@phytec.de>
> > Signed-off-by: Yannic Moog <y.moog@phytec.de>
> > ---
> > .../dts/freescale/imx8mp-phyboard-pollux-rdk.dts | 23 ++++++++++++++++++++++
> > 1 file changed, 23 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/freescale/imx8mp-phyboard-pollux-rdk.dts
> > b/arch/arm64/boot/dts/freescale/imx8mp-phyboard-pollux-rdk.dts
> > index 6203e39bc01be476f16f5ac80b6365bce150ae37..7d34b820e3213a3832c5be47444d4e9c636a6202 100644
> > --- a/arch/arm64/boot/dts/freescale/imx8mp-phyboard-pollux-rdk.dts
> > +++ b/arch/arm64/boot/dts/freescale/imx8mp-phyboard-pollux-rdk.dts
> > @@ -228,6 +228,15 @@ led-3 {
> > };
> > };
> >
> > +&i2c3 {
> > + clock-frequency = <400000>;
> > + pinctrl-names = "default", "gpio";
> > + pinctrl-0 = <&pinctrl_i2c3>;
> > + pinctrl-1 = <&pinctrl_i2c3_gpio>;
> > + sda-gpios = <&gpio5 18 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> > + scl-gpios = <&gpio5 19 (GPIO_ACTIVE_HIGH | GPIO_OPEN_DRAIN)>;
> > +};
> > +
> > &ldb_lvds_ch1 {
> > remote-endpoint = <&panel1_in>;
> > };
> > @@ -442,6 +451,20 @@ MX8MP_IOMUXC_I2C2_SDA__GPIO5_IO17 0x1e2
> > >;
> > };
> >
> > + pinctrl_i2c3: i2c3grp {
> > + fsl,pins = <
> > + MX8MP_IOMUXC_I2C3_SCL__I2C3_SCL 0x400001c2
> > + MX8MP_IOMUXC_I2C3_SDA__I2C3_SDA 0x400001c2
> > + >;
> > + };
> > +
> > + pinctrl_i2c3_gpio: i2c3gpiogrp {
> > + fsl,pins = <
> > + MX8MP_IOMUXC_I2C3_SCL__GPIO5_IO18 0x1e2
> > + MX8MP_IOMUXC_I2C3_SDA__GPIO5_IO19 0x1e2
> > + >;
> > + };
> > +
> > pinctrl_lvds1: lvds1grp {
> > fsl,pins = <
> > MX8MP_IOMUXC_SD2_WP__GPIO2_IO20 0x12
> >
> > --
> > 2.51.0
> >
next prev parent reply other threads:[~2025-10-22 6:20 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-20 13:11 [PATCH 0/4] arm64: dts: additions for phyboard-pollux Yannic Moog
2025-10-20 13:11 ` [PATCH 1/4] arm64: dts: imx8mp-phyboard-pollux: add fan-supply Yannic Moog
2025-10-20 15:35 ` Frank Li
2025-10-20 13:11 ` [PATCH 2/4] arm64: dts: imx8mp-phycore-som: add spi-nor supply vcc Yannic Moog
2025-10-20 15:36 ` Frank Li
2025-10-22 6:18 ` Yannic Moog
2025-10-20 13:11 ` [PATCH 3/4] arm64: dts: imx8mp-phyboard-pollux: Enable i2c3 Yannic Moog
2025-10-20 15:38 ` Frank Li
2025-10-22 6:20 ` Yannic Moog [this message]
2025-10-20 13:11 ` [PATCH 4/4] arm64: dts: imx8mp-phyboard-pollux: add PEB-WLBT-05 expansion board Yannic Moog
2025-10-20 15:40 ` Frank Li
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=8269481ecde6757a18f08ab76e35a8689f48a58e.camel@phytec.de \
--to=y.moog@phytec.de \
--cc=Frank.li@nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=s.riedmueller@phytec.de \
--cc=shawnguo@kernel.org \
--cc=t.remmet@phytec.de \
--cc=upstream@lists.phytec.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