From: Krzysztof Kozlowski <krzk@kernel.org>
To: Stefano Radaelli <stefano.radaelli21@gmail.com>
Cc: Frank Li <Frank.Li@nxp.com>,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
pierluigi.p@variscite.com,
Stefano Radaelli <stefano.r@variscite.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Andrew Lunn <andrew+netdev@lunn.ch>,
"David S. Miller" <davem@davemloft.net>,
Eric Dumazet <edumazet@google.com>,
Jakub Kicinski <kuba@kernel.org>, Paolo Abeni <pabeni@redhat.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
Heiner Kallweit <hkallweit1@gmail.com>,
Russell King <linux@armlinux.org.uk>,
Shawn Guo <shawnguo@kernel.org>, Joseph Guo <qijian.guo@nxp.com>,
Josua Mayer <josua@solid-run.com>,
Ernest Van Hoecke <ernest.vanhoecke@toradex.com>,
Mehmet Fide <mehmet.fide@screeningeagle.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Markus Niebel <Markus.Niebel@ew.tq-group.com>,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
Stefan Eichenberger <eichest@gmail.com>,
netdev@vger.kernel.org
Subject: Re: [PATCH v4 03/13] dt-bindings: arm: fsl: Add Variscite i.MX6ULZ board variants
Date: Thu, 1 Oct 2026 11:38:19 +0200 [thread overview]
Message-ID: <c329c4dd-a004-4ea7-918c-3731738e43b6@kernel.org> (raw)
In-Reply-To: <ar4jkNZc0eoF-EhL@Lord-Beerus.station>
On 01/10/2026 11:10, Stefano Radaelli wrote:
> On Thu, Oct 01, 2026 at 10:09:22AM +0200, Krzysztof Kozlowski wrote:
>> On Tue, Sep 29, 2026 at 05:17:30PM +0200, Stefano Radaelli wrote:
>>> + - const: variscite,dart-6ul-imx6ulz
>>> + - const: fsl,imx6ull
>>> + - const: fsl,imx6ulz
>>
>> Is this the right order? Which one is superset of which?
>>
>
> I followed the compatible order used by the existing i.MX6ULZ EVK
> and had also noticed the comment questioning whether `fsl,imx6ull`
> should come last.
> On review, I agree: i.MX6ULZ is the reduced-feature variant, while
> i.MX6ULL is the more general compatible.
> We can use `fsl,imx6ulz` followed by `fsl,imx6ull` for the new
Yes
> Variscite entries. I can also propose a separate patch to update
> the existing EVK compatible order to match, what do you think?
That probably should stay as is, because there could be a user checking
last fallback. Shouldn't, but could be.
Best regards,
Krzysztof
next prev parent reply other threads:[~2026-10-01 9:38 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-29 15:17 [PATCH v4 00/13] ARM: dts: imx6ul: Add Variscite VAR-SOM-6UL and DART-6UL Stefano Radaelli
2026-09-29 15:17 ` [PATCH v4 01/13] dt-bindings: arm: fsl: Add Variscite i.MX6UL board variants Stefano Radaelli
2026-10-01 7:46 ` Krzysztof Kozlowski
2026-09-29 15:17 ` [PATCH v4 02/13] dt-bindings: arm: fsl: Add Variscite i.MX6ULL " Stefano Radaelli
2026-10-01 8:07 ` Krzysztof Kozlowski
2026-09-29 15:17 ` [PATCH v4 03/13] dt-bindings: arm: fsl: Add Variscite i.MX6ULZ " Stefano Radaelli
2026-10-01 8:09 ` Krzysztof Kozlowski
2026-10-01 9:10 ` Stefano Radaelli
2026-10-01 9:38 ` Krzysztof Kozlowski [this message]
2026-09-29 15:17 ` [PATCH v4 04/13] net: phy: micrel: Check RMII clock select property presence Stefano Radaelli
2026-09-29 15:17 ` [PATCH v4 05/13] dt-bindings: net: micrel: Fix RMII clock select property type Stefano Radaelli
2026-10-07 20:35 ` Rob Herring (Arm)
2026-09-29 15:17 ` [PATCH v4 06/13] ARM: dts: imx6ul: Add Variscite SoM and DART base files Stefano Radaelli
2026-09-29 16:15 ` Hugo Villeneuve
2026-09-29 15:17 ` [PATCH v4 07/13] ARM: dts: imx6ul: Add Variscite audio codec files Stefano Radaelli
2026-09-29 15:17 ` [PATCH v4 08/13] ARM: dts: imx6ul: Add Variscite storage and wireless files Stefano Radaelli
2026-09-29 15:17 ` [PATCH v4 09/13] ARM: dts: imx6ul: Add Variscite carrier board files Stefano Radaelli
2026-09-29 15:17 ` [PATCH v4 10/13] ARM: dts: imx6ul: Reuse Variscite DTSI files for Concerto Stefano Radaelli
2026-09-29 15:17 ` [PATCH v4 11/13] ARM: dts: imx6ul: Add Variscite i.MX6UL board variants Stefano Radaelli
2026-09-29 15:17 ` [PATCH v4 12/13] ARM: dts: imx6ull: Add Variscite i.MX6ULL " Stefano Radaelli
2026-09-29 15:17 ` [PATCH v4 13/13] ARM: dts: imx6ulz: Add Variscite i.MX6ULZ " Stefano Radaelli
2026-09-29 16:14 ` [PATCH v4 00/13] ARM: dts: imx6ul: Add Variscite VAR-SOM-6UL and DART-6UL Hugo Villeneuve
2026-09-29 17:41 ` Stefano Radaelli
2026-10-01 18:43 ` Hugo Villeneuve
2026-10-02 11:58 ` Stefano Radaelli
2026-10-02 15:17 ` Hugo Villeneuve
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=c329c4dd-a004-4ea7-918c-3731738e43b6@kernel.org \
--to=krzk@kernel.org \
--cc=Frank.Li@nxp.com \
--cc=Markus.Niebel@ew.tq-group.com \
--cc=andrew+netdev@lunn.ch \
--cc=conor+dt@kernel.org \
--cc=davem@davemloft.net \
--cc=devicetree@vger.kernel.org \
--cc=edumazet@google.com \
--cc=eichest@gmail.com \
--cc=ernest.vanhoecke@toradex.com \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=hkallweit1@gmail.com \
--cc=hvilleneuve@dimonoff.com \
--cc=imx@lists.linux.dev \
--cc=josua@solid-run.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=kuba@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=mehmet.fide@screeningeagle.com \
--cc=netdev@vger.kernel.org \
--cc=pabeni@redhat.com \
--cc=pierluigi.p@variscite.com \
--cc=qijian.guo@nxp.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=stefano.r@variscite.com \
--cc=stefano.radaelli21@gmail.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 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.