From: Krzysztof Kozlowski <krzk@kernel.org>
To: "Peng Fan (OSS)" <peng.fan@oss.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>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org,
Peng Fan <peng.fan@nxp.com>
Subject: Re: [PATCH 1/2] dt-bindings: arm: fsl: Update i.MX95 compatible
Date: Sat, 4 Jan 2025 15:43:37 +0100 [thread overview]
Message-ID: <4666f8e9-d19e-45bd-be9c-a7f111168d66@kernel.org> (raw)
In-Reply-To: <20250104-imx9-machine-v1-1-18a78e41456b@nxp.com>
On 04/01/2025 13:13, Peng Fan (OSS) wrote:
> From: Peng Fan <peng.fan@nxp.com>
>
> i.MX95 features a System Controller and SCMI Spec 3.2 compatible
> firmware System Manager(SM) runs on the controller.
> Add "fsl,imx-sm" compatible string as fallback for "fsl,imx95" to
> indicate it is compatible with i.MX System Manager.
I see little value in generic compatible like that. All these are
aarch64 so why not adding that compatible?
How this generic compatible would be used?
And by what exactly?
All this must be explained in the commit msg.
Best regards,
Krzysztof
next prev parent reply other threads:[~2025-01-04 14:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-04 12:13 [PATCH 0/2] update i.MX95 machine compatible Peng Fan (OSS)
2025-01-04 12:13 ` [PATCH 1/2] dt-bindings: arm: fsl: Update i.MX95 compatible Peng Fan (OSS)
2025-01-04 14:43 ` Krzysztof Kozlowski [this message]
2025-01-06 2:51 ` Peng Fan
2025-01-06 6:12 ` Krzysztof Kozlowski
2025-01-09 2:40 ` Peng Fan
2025-01-13 11:35 ` Krzysztof Kozlowski
2025-01-04 12:13 ` [PATCH 2/2] arm64: dts: imx95-19x19-evk: Update machine compatible Peng Fan (OSS)
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=4666f8e9-d19e-45bd-be9c-a7f111168d66@kernel.org \
--to=krzk@kernel.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=peng.fan@oss.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