Linux kernel and device drivers for NXP i.MX platforms
 help / color / mirror / Atom feed
From: Josua Mayer <josua@solid-run.com>
To: Daniel Baluta <daniel.baluta@gmail.com>, Sherry Sun <sherry.sun@nxp.com>
Cc: Krzysztof Kozlowski <krzk@kernel.org>,
	Frank Li <frank.li@nxp.com>, "robh@kernel.org" <robh@kernel.org>,
	"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
	"conor+dt@kernel.org" <conor+dt@kernel.org>,
	"shawnguo@kernel.org" <shawnguo@kernel.org>,
	Daniel Baluta <daniel.baluta@nxp.com>,
	"dario.binacchi@amarulasolutions.com"
	<dario.binacchi@amarulasolutions.com>,
	"alexander.stein@ew.tq-group.com"
	<alexander.stein@ew.tq-group.com>,
	"Markus.Niebel@tq-group.com" <Markus.Niebel@tq-group.com>,
	"matthias.schiffer@tq-group.com" <matthias.schiffer@tq-group.com>,
	"y.moog@phytec.de" <y.moog@phytec.de>,
	Francesco Dolcini <francesco.dolcini@toradex.com>,
	"primoz.fiser@norik.com" <primoz.fiser@norik.com>,
	"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
	"festevam@gmail.com" <festevam@gmail.com>,
	"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"imx@lists.linux.dev" <imx@lists.linux.dev>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>,
	"kernel@pengutronix.de" <kernel@pengutronix.de>
Subject: Re: [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board
Date: Wed, 21 Jan 2026 10:06:11 +0000	[thread overview]
Message-ID: <b604d66e-d7c6-492d-9213-8d7e748dcc29@solid-run.com> (raw)
In-Reply-To: <CAEnQRZDCNXcAH7kBCPLJm2pPrJ9akXX+ZMW98H7MO8Hptjp3TA@mail.gmail.com>

Hi Daniel,

On 21/01/2026 11:51, Daniel Baluta wrote:
> <snip>
>
>>>>>> +              - fsl,imx93w-evk            # i.MX93W EVK Board
>>>>> Is 93w 11x11 or 14x14? can you add suffix to keep align existing one.
>>>>>
>>>> Hi Frank,
>>>>
>>>> IMX93W-EVK is the official board name, it basically reuse the  i.MX93
>>>> 11x11 EVK board, as described in the cover letter and dts patch. I
>>>> prefer to still use this name (imx93w-evk) to keep align with the board
>>> official name.
>>> It's second case, previous was frdm, with the same argument. I don't care
>>> what you prefer internally. You must align to upstream and all NXP boards are
>>> called soc-foo. Not socfoo.
>> Hi Krzysztof,
>>
>> The soc name is imx93w, the board is basically reuse the i.MX93 11x11 EVK,
>> so do you suggest we name it fsl,imx93w-11x11-evk or fsl,imx93w-evk?
> As per my understanding from Krzysztof comment this should be  fsl,imx93-w-evk.
> Like soc-foo not socfoo.
If the soc is "imx93w", the physical size / variant is "11x11" and the 
board is "evk",
then I'd define compatible as "fsl,imx93w-11x11-evk", "fsl,imx93w", 
"fsl,imx93".

  reply	other threads:[~2026-01-21 10:06 UTC|newest]

Thread overview: 17+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-01-20 10:26 [PATCH 0/2] Add i.MX93W EVK board support Sherry Sun
2026-01-20 10:26 ` [PATCH 1/2] dt-bindings: arm: fsl: Add i.MX93W EVK board Sherry Sun
2026-01-20 16:34   ` Frank Li
2026-01-21  3:18     ` Sherry Sun
2026-01-21  7:30       ` Krzysztof Kozlowski
2026-01-21  8:05         ` Sherry Sun
2026-01-21  9:51           ` Daniel Baluta
2026-01-21 10:06             ` Josua Mayer [this message]
2026-01-21 10:17               ` Sherry Sun
2026-01-21  9:57           ` Krzysztof Kozlowski
2026-01-21 10:14             ` Sherry Sun
2026-01-22  4:54               ` Sherry Sun
2026-01-21  8:32       ` Daniel Baluta
2026-01-21  9:26         ` Sherry Sun
2026-01-20 10:26 ` [PATCH 2/2] arch: arm64: imx93-wevk: Add i.MX93W EVK board support Sherry Sun
2026-01-20 16:37   ` Frank Li
2026-01-21  6:41     ` Sherry Sun

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=b604d66e-d7c6-492d-9213-8d7e748dcc29@solid-run.com \
    --to=josua@solid-run.com \
    --cc=Markus.Niebel@tq-group.com \
    --cc=alexander.stein@ew.tq-group.com \
    --cc=conor+dt@kernel.org \
    --cc=daniel.baluta@gmail.com \
    --cc=daniel.baluta@nxp.com \
    --cc=dario.binacchi@amarulasolutions.com \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=francesco.dolcini@toradex.com \
    --cc=frank.li@nxp.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=krzk@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=matthias.schiffer@tq-group.com \
    --cc=primoz.fiser@norik.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    --cc=sherry.sun@nxp.com \
    --cc=y.moog@phytec.de \
    /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