From: Shawn Guo <shawnguo2@yeah.net>
To: stefan.prisacariu@prevas.dk
Cc: Frank.li@nxp.com, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org, shawnguo@kernel.org,
s.hauer@pengutronix.de, kernel@pengutronix.de,
festevam@gmail.com
Subject: Re: [PATCH v2] ARM: dts: imx6qdl: make VAR-SOM SoM SoC-agnostic
Date: Sun, 16 Nov 2025 21:04:05 +0800 [thread overview]
Message-ID: <aRnLxcWKk5Q48y6H@dragon> (raw)
In-Reply-To: <20251112144441.1827336-1-stefan.prisacariu@prevas.dk>
On Wed, Nov 12, 2025 at 03:44:16PM +0100, stefan.prisacariu@prevas.dk wrote:
> From: Stefan Prisacariu <stefan.prisacariu@prevas.dk>
>
> Make SoM .dtsi SoC-agnostic by moving SoC include to board level
>
> imx6qdl-var-som.dtsi currently includes imx6q.dtsi, which makes this SoM
> description Quad/Dual specific and prevents reuse from i.MX6DL boards.
>
> Changes:
> - Move imx6q.dtsi include from imx6qdl-var-som.dtsi to
> imx6q-var-mx6customboard.dts.
> - Remove /dts-v1/; from imx6qdl-var-som.dtsi (dtsi files should not declare
> version)
>
> This keeps the SoM .dtsi SoC-agnostic (it already relies on imx6qdl.dtsi for
> family-common parts) and allows boards using the DualLite or Solo to include
> imx6dl.dtsi instead.
>
> Why this is needed:
> To reuse imx6qdl-var-som.dtsi on i.MX6DL board.
>
> No functional changes for imx6q-var-mx6customboard are intended.
>
> Signed-off-by: Stefan Prisacariu <stefan.prisacariu@prevas.dk>
> Link: https://lore.kernel.org/all/20250925104942.4148376-1-stefan.prisacariu@prevas.dk/
Applied, thanks!
prev parent reply other threads:[~2025-11-16 13:04 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-12 14:44 [PATCH v2] ARM: dts: imx6qdl: make VAR-SOM SoM SoC-agnostic stefan.prisacariu
2025-11-16 13:04 ` Shawn Guo [this message]
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=aRnLxcWKk5Q48y6H@dragon \
--to=shawnguo2@yeah.net \
--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=shawnguo@kernel.org \
--cc=stefan.prisacariu@prevas.dk \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.