From: Frank Li <Frank.li@nxp.com>
To: Peng Fan <peng.fan@nxp.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Shawn Guo <shawnguo@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
"open list:OPEN FIRMWARE AND FLATTENED DEVICE TREE BINDINGS"
<devicetree@vger.kernel.org>,
"open list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<imx@lists.linux.dev>,
"moderated list:ARM/FREESCALE IMX / MXC ARM ARCHITECTURE"
<linux-arm-kernel@lists.infradead.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 3/7] arm64: dts: imx95-19x19-evk: Add audio related nodes
Date: Mon, 1 Jul 2024 11:45:40 -0400 [thread overview]
Message-ID: <ZoLPJPR8r1+XaRAB@lizhi-Precision-Tower-5810> (raw)
In-Reply-To: <AM6PR04MB5941C1138E4F33AA3FA49AA388D02@AM6PR04MB5941.eurprd04.prod.outlook.com>
On Fri, Jun 28, 2024 at 12:03:27AM +0000, Peng Fan wrote:
> > Subject: [PATCH 3/7] arm64: dts: imx95-19x19-evk: Add audio related
> > nodes
> >
> > Add sai1, sai2. Add i2c4 and wm8962 and other dependent nodes.
> >
> > Signed-off-by: Frank Li <Frank.Li@nxp.com>
> > ---
> > .../boot/dts/freescale/imx95-19x19-evk.dts | 238
> > ++++++++++++++++++
> > 1 file changed, 238 insertions(+)
> >
> > diff --git a/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts
> > b/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts
> > index d14a54ab4fd47..660e623f4f964 100644
> > --- a/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts
> > +++ b/arch/arm64/boot/dts/freescale/imx95-19x19-evk.dts
> > @@ -17,6 +17,11 @@ aliases {
> > serial0 = &lpuart1;
> > };
> >
...
> > + 0x0000 /* 4:FN_DMICCDAT */
> > + 0x0000 /* 5:Default */
> > + >;
> > + };
> > +
> > + i2c4_gpio_expander_21: gpio@21 {
>
> Use gpio-expander@21?
> It is easy to duplicate the node if other i2c bus also
> has one.
It should be fine, parent node is difference. gpio-expander@21 can't
resolve your problem.
i2c2
{
gpio-expander@21 {};
}
i2c3
{
gpio-expander@21 {};
}
It should be same situation as gpio@21.
DT should allow the same name under difference parent.
Frank
>
> Regards,
> Peng.
>
next prev parent reply other threads:[~2024-07-01 15:45 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-27 21:59 [PATCH 1/7] arm64: dts: imx95: add edma[1..3] nodes Frank Li
2024-06-27 21:59 ` [PATCH 2/7] arm64: dts: imx95: add sai[1..6], xcvr and micfill Frank Li
2024-06-28 0:00 ` Peng Fan
2024-06-27 21:59 ` [PATCH 3/7] arm64: dts: imx95-19x19-evk: Add audio related nodes Frank Li
2024-06-28 0:03 ` Peng Fan
2024-07-01 15:45 ` Frank Li [this message]
2024-07-02 0:02 ` Peng Fan
2024-06-27 21:59 ` [PATCH 4/7] arm64: dts: imx95: add flexspi node Frank Li
2024-06-28 0:04 ` Peng Fan
2024-06-27 21:59 ` [PATCH 5/7] arm64: dts: imx95-19x19-evk: add flexspi and child node Frank Li
2024-06-28 0:58 ` Peng Fan
2024-06-27 22:00 ` [PATCH 6/7] arm64: dts: imx95: add thermal_zone label Frank Li
2024-06-28 0:59 ` Peng Fan
2024-06-27 22:00 ` [PATCH 7/7] arm64: dts: imx95-19x19-evk: add pwm fan control Frank Li
2024-06-28 0:59 ` Peng Fan
2024-06-27 23:59 ` [PATCH 1/7] arm64: dts: imx95: add edma[1..3] nodes Peng Fan
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=ZoLPJPR8r1+XaRAB@lizhi-Precision-Tower-5810 \
--to=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=peng.fan@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@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