public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Peng Fan <peng.fan@nxp.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Shawn Guo <shawnguo@kernel.org>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	Pengutronix Kernel Team <kernel@pengutronix.de>,
	Fabio Estevam <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>
Subject: Re: [PATCH 1/2] arm64: dts: imx8mm-var-som: drop unused top-level compatible
Date: Mon, 2 Sep 2024 12:19:50 +0200	[thread overview]
Message-ID: <7fbc4549-79e0-4fb0-9468-41a0babae95a@linaro.org> (raw)
In-Reply-To: <PAXPR04MB8459FB36872E71E1605DDC2088922@PAXPR04MB8459.eurprd04.prod.outlook.com>

On 02/09/2024 12:13, Peng Fan wrote:
>> Subject: [PATCH 1/2] arm64: dts: imx8mm-var-som: drop unused top-
>> level compatible
>>
>> The Variscite VAR-SOM-MX8MM System-on-Module cannot be used
>> alone without motherboard, so drop the top-level compatible field to
>> avoid any false impression that such usage is possible.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>> ---
>>  arch/arm64/boot/dts/freescale/imx8mm-var-som.dtsi | 1 -
>>  1 file changed, 1 deletion(-)
>>
>> diff --git a/arch/arm64/boot/dts/freescale/imx8mm-var-som.dtsi
>> b/arch/arm64/boot/dts/freescale/imx8mm-var-som.dtsi
>> index d7830df5b6f9..cdfacbc35db5 100644
>> --- a/arch/arm64/boot/dts/freescale/imx8mm-var-som.dtsi
>> +++ b/arch/arm64/boot/dts/freescale/imx8mm-var-som.dtsi
>> @@ -8,7 +8,6 @@
>>
>>  / {
>>  	model = "Variscite VAR-SOM-MX8MM module";
>> -	compatible = "variscite,var-som-mx8mm", "fsl,imx8mm";
>>
>>  	chosen {
>>  		stdout-path = &uart4;
>> --
>> 2.43.0
>>
> 
> Should the " variscite,var-som-mx8mm " also removed from
> imx8mm-var-som-symphony.dts?

No, why?

Best regards,
Krzysztof


  reply	other threads:[~2024-09-02 10:19 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-09-02  7:52 [PATCH 1/2] arm64: dts: imx8mm-var-som: drop unused top-level compatible Krzysztof Kozlowski
2024-09-02  7:52 ` [PATCH 2/2] dt-bindings: arm: fsl: drop usage of VAR-SOM-MX8MM SoM compatible alone Krzysztof Kozlowski
2024-09-02 10:15   ` Peng Fan
2024-09-02 10:20     ` Krzysztof Kozlowski
2024-09-02 12:26   ` Peng Fan
2024-09-03 15:14   ` Rob Herring (Arm)
2024-09-02 10:13 ` [PATCH 1/2] arm64: dts: imx8mm-var-som: drop unused top-level compatible Peng Fan
2024-09-02 10:19   ` Krzysztof Kozlowski [this message]
2024-09-02 12:27 ` Peng Fan
2024-09-03  6:53 ` Shawn Guo

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=7fbc4549-79e0-4fb0-9468-41a0babae95a@linaro.org \
    --to=krzysztof.kozlowski@linaro.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=festevam@gmail.com \
    --cc=imx@lists.linux.dev \
    --cc=kernel@pengutronix.de \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=peng.fan@nxp.com \
    --cc=robh@kernel.org \
    --cc=s.hauer@pengutronix.de \
    --cc=shawnguo@kernel.org \
    /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