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

On Fri, 13 Mar 2026 18:47:01 +0100, Stefano Radaelli wrote:
> 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
> 
> [...]

Applied, thanks!

[1/2] arm64: dts: freescale: Add support for Variscite DART-MX95
      commit: 5953966f26f5f825cf1fed6f96c1f3138bee6d6b
[2/2] arm64: dts: imx95-var-dart: Add support for Variscite Sonata board
      commit: b5fede0246d012e0fe66588e85825c2bfac626eb

Best regards,
-- 
Frank Li <Frank.Li@nxp.com>

On Fri, Mar 13, 2026 at 06:47:01PM +0100, Stefano Radaelli wrote:
> 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

Can you run https://github.com/lznuaa/dt-format for new file to easy
track and check by script later.

Frank

> 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
>

On Fri, Mar 13, 2026 at 02:56:03PM -0400, Frank Li wrote:
> On Fri, Mar 13, 2026 at 06:47:01PM +0100, Stefano Radaelli wrote:
> > 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
>
> Can you run https://github.com/lznuaa/dt-format for new file to easy
> track and check by script later.

I applied with below change
- update copywrite to 2026
- move reg after compatible at ethernet phy node
- order button-n,

Next time,  run dt-format,  keep node orders, just adjust some property.
I will enhance script check graduatelly.

Frank

>
> Frank
>
> > 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
> >

On Tue, Mar 24, 2026 at 03:48:29PM -0400, Frank Li wrote:
> On Fri, Mar 13, 2026 at 02:56:03PM -0400, Frank Li wrote:
> > On Fri, Mar 13, 2026 at 06:47:01PM +0100, Stefano Radaelli wrote:
> > > 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
> >
> > Can you run https://github.com/lznuaa/dt-format for new file to easy
> > track and check by script later.
> 
> I applied with below change
> - update copywrite to 2026

How do you know that the correct copyright year is 2026?
The copyright years does not change to today just because it is the year
it was submitted.

I think that you should refrain yourself for doing these kind of changes
to the code when you apply patches.

Thanks
Francesco

On Wed, Mar 25, 2026 at 01:21:04PM +0100, Francesco Dolcini wrote:
> On Tue, Mar 24, 2026 at 03:48:29PM -0400, Frank Li wrote:
> > On Fri, Mar 13, 2026 at 02:56:03PM -0400, Frank Li wrote:
> > > On Fri, Mar 13, 2026 at 06:47:01PM +0100, Stefano Radaelli wrote:
> > > > 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
> > >
> > > Can you run https://github.com/lznuaa/dt-format for new file to easy
> > > track and check by script later.
> >
> > I applied with below change
> > - update copywrite to 2026
>
> How do you know that the correct copyright year is 2026?
> The copyright years does not change to today just because it is the year
> it was submitted.

At least it should include 2026 because it is new files in kernel tree.

>
> I think that you should refrain yourself for doing these kind of changes
> to the code when you apply patches.

If original owner have concern, I can update it in my tree.

Frank
>
> Thanks
> Francesco
>
>

On Wed, Mar 25, 2026 at 10:50:57AM -0400, Frank Li wrote:
> On Wed, Mar 25, 2026 at 01:21:04PM +0100, Francesco Dolcini wrote:
> > On Tue, Mar 24, 2026 at 03:48:29PM -0400, Frank Li wrote:
> > > On Fri, Mar 13, 2026 at 02:56:03PM -0400, Frank Li wrote:
> > > > On Fri, Mar 13, 2026 at 06:47:01PM +0100, Stefano Radaelli wrote:
> > > > > 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
> > > >
> > > > Can you run https://github.com/lznuaa/dt-format for new file to easy
> > > > track and check by script later.
> > >
> > > I applied with below change
> > > - update copywrite to 2026
> >
> > How do you know that the correct copyright year is 2026?
> > The copyright years does not change to today just because it is the year
> > it was submitted.
> 
> At least it should include 2026 because it is new files in kernel
> tree.

The copyright year is not changing nor being updated just because you
are adding the file to the linux kernel tree.

Francesco

On Wed, Mar 25, 2026 at 07:06:04PM +0100, Francesco Dolcini wrote:
> On Wed, Mar 25, 2026 at 10:50:57AM -0400, Frank Li wrote:
> > On Wed, Mar 25, 2026 at 01:21:04PM +0100, Francesco Dolcini wrote:
> > > On Tue, Mar 24, 2026 at 03:48:29PM -0400, Frank Li wrote:
> > > > On Fri, Mar 13, 2026 at 02:56:03PM -0400, Frank Li wrote:
> > > > > On Fri, Mar 13, 2026 at 06:47:01PM +0100, Stefano Radaelli wrote:
> > > > > > 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
> > > > >
> > > > > Can you run https://github.com/lznuaa/dt-format for new file to easy
> > > > > track and check by script later.
> > > >
> > > > I applied with below change
> > > > - update copywrite to 2026
> > >
> > > How do you know that the correct copyright year is 2026?
> > > The copyright years does not change to today just because it is the year
> > > it was submitted.
> >
> > At least it should include 2026 because it is new files in kernel
> > tree.
>
> The copyright year is not changing nor being updated just because you
> are adding the file to the linux kernel tree.

It is impossible zero modify before submit patch. If update copywrite year,
it needs include current years, I omit it when review it and find at apply.

And original owner Stefano Radaelli's agree on update to 2026.

Frank

>
> Francesco
>
>

On Wed, Mar 25, 2026 at 10:50:57AM -0400, Frank Li wrote:
> >
> > How do you know that the correct copyright year is 2026?
> > The copyright years does not change to today just because it is the year
> > it was submitted.
> 
> At least it should include 2026 because it is new files in kernel tree.
> 
> >
> > I think that you should refrain yourself for doing these kind of changes
> > to the code when you apply patches.
> 
> If original owner have concern, I can update it in my tree.
> 

Hi Francesco, hi Frank,

thanks for the clarification.

In this specific case, I'm fine with keeping 2026 for these new files
introduced in the kernel tree.

Thank you all for taking care of this!

Best regards,
Stefano