From: Krzysztof Kozlowski <krzk@kernel.org>
To: Tarang Raval <tarang.raval@siliconsignals.io>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"krzk+dt@kernel.org" <krzk+dt@kernel.org>,
"robh@kernel.org" <robh@kernel.org>,
"festevam@gmail.com" <festevam@gmail.com>
Cc: Conor Dooley <conor+dt@kernel.org>,
Sascha Hauer <s.hauer@pengutronix.de>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Gregor Herburger <gregor.herburger@ew.tq-group.com>,
Francesco Dolcini <francesco.dolcini@toradex.com>,
Hugo Villeneuve <hvilleneuve@dimonoff.com>,
Hiago De Franco <hiago.franco@toradex.com>,
Joao Paulo Goncalves <joao.goncalves@toradex.com>,
Mathieu Othacehe <m.othacehe@gmail.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Parthiban Nallathambi <parthiban@linumiz.com>,
Yannic Moog <y.moog@phytec.de>, Josua Mayer <josua@solid-run.com>,
Li Yang <leoyang.li@nxp.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>
Subject: Re: [PATCH 2/2] dt-bindings: arm: fsl: Add Variscite Symphony board and VAR-SOM-MX8MP SoM
Date: Sun, 1 Sep 2024 12:26:55 +0200 [thread overview]
Message-ID: <084bc911-a51c-4257-b5bb-25bed445f3b9@kernel.org> (raw)
In-Reply-To: <PN3P287MB182994A2AA56868084D70CC28B902@PN3P287MB1829.INDP287.PROD.OUTLOOK.COM>
On 31/08/2024 15:51, Tarang Raval wrote:
> Hi ,
>
>>> - toradex,verdin-imx8mp-wifi # Verdin iMX8M Plus Wi-Fi / BT Modules
>>> + - variscite,var-som-mx8mp # i.MX8MP Variscite VAR-SOM-MX8M Plus module
>>
>> That's not correct. You cannot use this SoM alone.
>
> I took the reference from var-som-imx8mm, where they use "variscite,var-som-mx8mm" in a similar manner. However, if you still believe it's incorrect, I will change it.
I posted that patch, but I don't think it was correct.
>
> One more thing: should I change "VAR-SOM-MX8M Plus" to "VAR-SOM-MX8MP" in the DTSI model name and in the YAML file as well, or keep it as it is?
No clue, these comments are basically repeating compatible name so not
much helpful anyway.
Best regards,
Krzysztof
prev parent reply other threads:[~2024-09-01 10:28 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-31 11:07 [PATCH 0/2] Add support for Variscite Symphony board and VAR-SOM-MX8MP SoM Tarang Raval
2024-08-31 11:07 ` [PATCH 1/2] arm64: dts: imx8mp-var-som-symphony: Add " Tarang Raval
2024-08-31 13:19 ` Krzysztof Kozlowski
2024-08-31 11:07 ` [PATCH 2/2] dt-bindings: arm: fsl: " Tarang Raval
2024-08-31 13:19 ` Krzysztof Kozlowski
2024-08-31 13:51 ` Tarang Raval
2024-09-01 10:26 ` Krzysztof Kozlowski [this message]
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=084bc911-a51c-4257-b5bb-25bed445f3b9@kernel.org \
--to=krzk@kernel.org \
--cc=alexander.stein@ew.tq-group.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=francesco.dolcini@toradex.com \
--cc=gregor.herburger@ew.tq-group.com \
--cc=hiago.franco@toradex.com \
--cc=hvilleneuve@dimonoff.com \
--cc=imx@lists.linux.dev \
--cc=joao.goncalves@toradex.com \
--cc=josua@solid-run.com \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=m.othacehe@gmail.com \
--cc=parthiban@linumiz.com \
--cc=robh@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=shawnguo@kernel.org \
--cc=tarang.raval@siliconsignals.io \
--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;
as well as URLs for NNTP newsgroup(s).