This patch series adds support for the Variscite DART-MX91 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.

v3->v4:
 - Fix space between BUCK4/BUCK5 aned parenthesis
 - Remove unused pinctrl groups

v2->v3:
 - Rebased the series to fix DTS apply issues.

v1->v2:
 - Ordering by hex and node name.

Stefano Radaelli (3):
  dt-bindings: arm: fsl: add Variscite DART-MX91 Boards
  arm64: dts: freescale: Add support for Variscite DART-MX91
  arm64: dts: imx91-var-dart: Add support for Variscite Sonata board

 .../devicetree/bindings/arm/fsl.yaml          |   6 +
 arch/arm64/boot/dts/freescale/Makefile        |   1 +
 .../dts/freescale/imx91-var-dart-sonata.dts   | 471 ++++++++++++++++++
 .../boot/dts/freescale/imx91-var-dart.dtsi    | 468 +++++++++++++++++
 4 files changed, 946 insertions(+)
 create mode 100644 arch/arm64/boot/dts/freescale/imx91-var-dart-sonata.dts
 create mode 100644 arch/arm64/boot/dts/freescale/imx91-var-dart.dtsi


base-commit: a251f9ed77f01f16adaaa1b3d2f568fc1b5acbfd
-- 
2.47.3

On Wed, Mar 04, 2026 at 05:59:52PM +0100, Stefano Radaelli wrote:
> This patch series adds support for the Variscite DART-MX91 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.
>
> v3->v4:
>  - Fix space between BUCK4/BUCK5 aned parenthesis
>  - Remove unused pinctrl groups
>
> v2->v3:
>  - Rebased the series to fix DTS apply issues.
>
> v1->v2:
>  - Ordering by hex and node name.
>
> Stefano Radaelli (3):
>   dt-bindings: arm: fsl: add Variscite DART-MX91 Boards
>   arm64: dts: freescale: Add support for Variscite DART-MX91
>   arm64: dts: imx91-var-dart: Add support for Variscite Sonata board

Can you rebase to my for-next tree
https://git.kernel.org/pub/scm/linux/kernel/git/frank.li/linux.git/log/?h=for-next

And new file, run https://github.com/lznuaa/dt-format to keep node nice
ordered.

Frank

>
>  .../devicetree/bindings/arm/fsl.yaml          |   6 +
>  arch/arm64/boot/dts/freescale/Makefile        |   1 +
>  .../dts/freescale/imx91-var-dart-sonata.dts   | 471 ++++++++++++++++++
>  .../boot/dts/freescale/imx91-var-dart.dtsi    | 468 +++++++++++++++++
>  4 files changed, 946 insertions(+)
>  create mode 100644 arch/arm64/boot/dts/freescale/imx91-var-dart-sonata.dts
>  create mode 100644 arch/arm64/boot/dts/freescale/imx91-var-dart.dtsi
>
>
> base-commit: a251f9ed77f01f16adaaa1b3d2f568fc1b5acbfd
> --
> 2.47.3
>

Hi Frank,

On Fri, Mar 13, 2026 at 11:13:35AM -0400, Frank Li wrote:
> 
> Can you rebase to my for-next tree
> https://git.kernel.org/pub/scm/linux/kernel/git/frank.li/linux.git/log/?h=for-next
> 
> And new file, run https://github.com/lznuaa/dt-format to keep node nice
> ordered.
> 

Sure, I will rebase the series on top of your for-next branch and send an
updated version.
If possible, it would be great if the series could be merged as soon as
possible, to avoid having to rebase it again on newer changes.

Regarding dt-format, I can run it, but in my experience it is a bit buggy.
It sometimes moves comments to completely unrelated locations and does not
always keep a logical ordering of nodes. For example, I saw cases where
usdhc3_wlan was moved before usdhc3_sleep, and pinctrl nodes were not kept
at the end of the file.

Best regards,
Stefano

On Fri, Mar 13, 2026 at 04:54:42PM +0100, Stefano Radaelli wrote:
> Hi Frank,
>
> On Fri, Mar 13, 2026 at 11:13:35AM -0400, Frank Li wrote:
> >
> > Can you rebase to my for-next tree
> > https://git.kernel.org/pub/scm/linux/kernel/git/frank.li/linux.git/log/?h=for-next
> >
> > And new file, run https://github.com/lznuaa/dt-format to keep node nice
> > ordered.
> >
>
> Sure, I will rebase the series on top of your for-next branch and send an
> updated version.
> If possible, it would be great if the series could be merged as soon as
> possible, to avoid having to rebase it again on newer changes.

I try best. I go though as reverse order patchwork order.

https://patchwork.kernel.org/project/imx/list/?series=&submitter=&state=1&q=&archive=&delegate=

Small fix go high priority.

>
> Regarding dt-format, I can run it, but in my experience it is a bit buggy.

Put bugg in issue list, I will fix it.

> It sometimes moves comments to completely unrelated locations and does not
> always keep a logical ordering of nodes.

Logical order is hard to follow. Each one have difference opinion about
logic group. I am trying to normalize and machine script. I use same rule
for every new dts file.  property order is not so important. The key is
node orders, which try to avoid add duplicate one in future.

> For example, I saw cases where usdhc3_wlan was moved before usdhc3_sleep,

> and pinctrl nodes were not kept
> at the end of the file.

About pinctrl nodes at end of the file, we don't stick this rule. There will
be more than one pinctrl nodes.

Frank
>
> Best regards,
> Stefano

Hi Frank,

On Fri, Mar 13, 2026 at 12:50:49PM -0400, Frank Li wrote:
> On Fri, Mar 13, 2026 at 04:54:42PM +0100, Stefano Radaelli wrote:
> > Hi Frank,
> >
> > On Fri, Mar 13, 2026 at 11:13:35AM -0400, Frank Li wrote:
> > >
> > > Can you rebase to my for-next tree
> > > https://git.kernel.org/pub/scm/linux/kernel/git/frank.li/linux.git/log/?h=for-next
> > >
> > > And new file, run https://github.com/lznuaa/dt-format to keep node nice
> > > ordered.
> > >
> >
> > Sure, I will rebase the series on top of your for-next branch and send an
> > updated version.
> > If possible, it would be great if the series could be merged as soon as
> > possible, to avoid having to rebase it again on newer changes.
> 
> I try best. I go though as reverse order patchwork order.
> 
> https://patchwork.kernel.org/project/imx/list/?series=&submitter=&state=1&q=&archive=&delegate=
> 
> Small fix go high priority.
> 
> >
> > Regarding dt-format, I can run it, but in my experience it is a bit buggy.
> 
> Put bugg in issue list, I will fix it.
> 
> > It sometimes moves comments to completely unrelated locations and does not
> > always keep a logical ordering of nodes.
> 
> Logical order is hard to follow. Each one have difference opinion about
> logic group. I am trying to normalize and machine script. I use same rule
> for every new dts file.  property order is not so important. The key is
> node orders, which try to avoid add duplicate one in future.
> 
> > For example, I saw cases where usdhc3_wlan was moved before usdhc3_sleep,
> 
> > and pinctrl nodes were not kept
> > at the end of the file.
> 
> About pinctrl nodes at end of the file, we don't stick this rule. There will
> be more than one pinctrl nodes.
> 

Thank you for the clarification and for the work you are putting into
reviewing and maintaining these patches.

Regarding dt-format, I will open issues for the cases where I noticed
incorrect behavior (such as comments being moved to unrelated sections),
so they can be tracked and fixed.

Thanks again for your support and for maintaining the i.MX tree.

Best regards,
Stefano