From: Stefano Radaelli <stefano.radaelli21@gmail.com>
To: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Cc: pierluigi.p@variscite.com,
Stefano Radaelli <stefano.r@variscite.com>,
Shawn Guo <shawnguo@kernel.org>,
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
Subject: [PATCH v7 0/2] Add support for Variscite DART-MX95 and Sonata board
Date: Fri, 13 Mar 2026 18:47:01 +0100 [thread overview]
Message-ID: <20260313174707.26902-1-stefano.r@variscite.com> (raw)
This patch series adds support for the Variscite DART-MX95 system on
module and the Sonata carrier board.
The series includes:
- Device tree bindings documentation for both SOM and carrier board
- SOM device tree with on-module peripherals
- Sonata carrier board device tree with board-specific features
The implementation follows the standard SOM + carrier board pattern
where the SOM dtsi contains only peripherals mounted on the module,
while carrier-specific interfaces are enabled in the board dts.
v7:
- Order nodes in symphony dts
v6:
- Order by node name instead of by label
v5:
- Fix newlines and nodes order
v4:
- Fix typo in spacing
- Remove vpu and cm7 reserved memory
- Add GPIO_OPEN_DRAIN to i2c gpios
- Move pinmux to eof
v3:
- Fix specific node names with generic ones
- Remove fixed-link property for SFP
- Audio regulator cleanup
v2:
- Add SFP cage node for enetc_port2 following sff,sfp.yaml binding
Stefano Radaelli (2):
arm64: dts: freescale: Add support for Variscite DART-MX95
arm64: dts: imx95-var-dart: Add support for Variscite Sonata board
arch/arm64/boot/dts/freescale/Makefile | 1 +
.../dts/freescale/imx95-var-dart-sonata.dts | 591 ++++++++++++++++++
.../boot/dts/freescale/imx95-var-dart.dtsi | 425 +++++++++++++
3 files changed, 1017 insertions(+)
create mode 100644 arch/arm64/boot/dts/freescale/imx95-var-dart-sonata.dts
create mode 100644 arch/arm64/boot/dts/freescale/imx95-var-dart.dtsi
base-commit: 40fbbd64bba6c6e7a72885d2f59b6a3be9991eeb
prerequisite-patch-id: 7ed0e453f554c70d0fafd5147d4d9b62cac6c10f
--
2.47.3
next reply other threads:[~2026-03-13 17:47 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-13 17:47 Stefano Radaelli [this message]
2026-03-13 17:47 ` [PATCH v7 1/2] arm64: dts: freescale: Add support for Variscite DART-MX95 Stefano Radaelli
2026-03-13 17:47 ` [PATCH v7 2/2] arm64: dts: imx95-var-dart: Add support for Variscite Sonata board Stefano Radaelli
2026-03-13 18:56 ` [PATCH v7 0/2] Add support for Variscite DART-MX95 and " Frank Li
2026-03-24 19:48 ` Frank Li
2026-03-25 12:21 ` Francesco Dolcini
2026-03-25 14:50 ` Frank Li
2026-03-25 15:25 ` Stefano Radaelli
2026-03-25 18:06 ` Francesco Dolcini
2026-03-25 19:02 ` Frank Li
2026-03-24 18:45 ` 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=20260313174707.26902-1-stefano.r@variscite.com \
--to=stefano.radaelli21@gmail.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=pierluigi.p@variscite.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefano.r@variscite.com \
/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