From: Francesco Dolcini <francesco@dolcini.it>
To: Frank Li <Frank.li@oss.nxp.com>
Cc: Ernest Van Hoecke <ernestvanhoecke@gmail.com>,
Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
Subject: Re: [PATCH 0/4] arm64: dts: freescale: Add Toradex iMX95 overlays
Date: Tue, 22 Sep 2026 18:58:46 +0200 [thread overview]
Message-ID: <20260922165846.GA290956@francesco-nb> (raw)
In-Reply-To: <arKn0LhC5fty7dHN@SMW015318>
On Tue, Sep 22, 2026 at 11:07:44AM -0500, Frank Li wrote:
> On Tue, Sep 22, 2026 at 04:33:45PM +0200, Ernest Van Hoecke wrote:
> > This series adds device tree overlays for the Toradex Verdin, Aquila,
> > and SMARC iMX95 SoMs.
> >
> > The series adds support for:
> > - NAU8822 Bridge Tied Load configuration on the Verdin Development Board
> > - UART_4 reservation for Cortex-M7 firmware on Verdin and Aquila
> > - SER0 reservation for Cortex-M7 firmware on SMARC
> >
> > The UART overlays mark the port as reserved so Linux does not claim it.
> > Firmware remains responsible for configuring the UART and its pads.
> >
> > The Makefile entries build standalone DTBOs and ready-to-use composed
> > DTBs for the corresponding Development Boards.
> >
> > Signed-off-by: Ernest Van Hoecke <ernest.vanhoecke@toradex.com>
> > ---
> > Ernest Van Hoecke (4):
> > arm64: dts: freescale: imx95-verdin: Add NAU8822 Bridge Tied Load
> > arm64: dts: freescale: imx95-verdin: Add Cortex-M7 UART_4 overlay
> > arm64: dts: freescale: imx95-aquila: Add Cortex-M7 UART_4 overlay
>
> both reserved lpuart2, can you share one dtso?
The comment in the DT file must be different because it's important to
reference the actual board it applies to.
So to fulfill this request we would need to add a common dtsi, include
it from two different dtso files.
This to save 2 lines of duplicated code, `&lpuart2 { status = "reserved"; };`.
To me this is just worst than the current proposal.
Francesco
next prev parent reply other threads:[~2026-09-22 16:58 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-22 14:33 Ernest Van Hoecke
2026-09-22 14:33 ` [PATCH 1/4] arm64: dts: freescale: imx95-verdin: Add NAU8822 Bridge Tied Load Ernest Van Hoecke
2026-09-22 14:33 ` [PATCH 2/4] arm64: dts: freescale: imx95-verdin: Add Cortex-M7 UART_4 overlay Ernest Van Hoecke
2026-09-22 14:33 ` [PATCH 3/4] arm64: dts: freescale: imx95-aquila: " Ernest Van Hoecke
2026-09-22 14:33 ` [PATCH 4/4] arm64: dts: freescale: imx95-toradex-smarc: Add Cortex-M7 SER0 overlay Ernest Van Hoecke
2026-09-22 16:07 ` [PATCH 0/4] arm64: dts: freescale: Add Toradex iMX95 overlays Frank Li
2026-09-22 16:58 ` Francesco Dolcini [this message]
2026-09-22 18:31 ` Frank Li
2026-09-23 8:41 ` Francesco Dolcini
2026-09-23 15:06 ` Frank Li
2026-09-24 10:13 ` Francesco Dolcini
2026-09-24 14:33 ` 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=20260922165846.GA290956@francesco-nb \
--to=francesco@dolcini.it \
--cc=Frank.Li@nxp.com \
--cc=Frank.li@oss.nxp.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=ernest.vanhoecke@toradex.com \
--cc=ernestvanhoecke@gmail.com \
--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 \
/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
all inboxes | Powered by JetHome®