From: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
To: Peng Fan <peng.fan@nxp.com>,
"Peng Fan (OSS)" <peng.fan@oss.nxp.com>,
"robh+dt@kernel.org" <robh+dt@kernel.org>,
"krzysztof.kozlowski+dt@linaro.org"
<krzysztof.kozlowski+dt@linaro.org>,
"conor+dt@kernel.org" <conor+dt@kernel.org>,
"abelvesa@kernel.org" <abelvesa@kernel.org>,
"mturquette@baylibre.com" <mturquette@baylibre.com>,
"sboyd@kernel.org" <sboyd@kernel.org>,
"shawnguo@kernel.org" <shawnguo@kernel.org>,
"s.hauer@pengutronix.de" <s.hauer@pengutronix.de>,
"kernel@pengutronix.de" <kernel@pengutronix.de>,
"festevam@gmail.com" <festevam@gmail.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
dl-linux-imx <linux-imx@nxp.com>,
"linux-clk@vger.kernel.org" <linux-clk@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] dt-bindings: clock: support NXP i.MX95
Date: Tue, 23 Jan 2024 14:55:28 +0100 [thread overview]
Message-ID: <78e296fb-a3dc-4e00-94bc-91dab7294887@linaro.org> (raw)
In-Reply-To: <DU0PR04MB9417A8F4230D2C7C76D1550988742@DU0PR04MB9417.eurprd04.prod.outlook.com>
On 23/01/2024 14:08, Peng Fan wrote:
> Hi Conor, Krzysztof
>
> I replied you both here.
>
>> Subject: Re: [PATCH] dt-bindings: clock: support NXP i.MX95
>>
>> On 21/01/2024 12:46, Peng Fan (OSS) wrote:
>>> From: Peng Fan <peng.fan@nxp.com>
>>>
>>> Add i.MX95 clock dt-binding header file
>>>
>>> Signed-off-by: Peng Fan <peng.fan@nxp.com>
>>
>> This should be squashed with respective binding patch.
>
> i.MX95 use SCMI firmware, the SCP processor handles
> clock/power/pinmux/reset/performance and etc.
>
> I just add the index that SCMI exports, and Linux/UBoot
> will use the index and go through SCMI to do real HW
> configuration.
>
> In such case, should I still add HW information in
> a yaml binding doc? I am not sure what should be added
> if yes.
Then why do you need it in the binding? I don't see any use of this.
Best regards,
Krzysztof
_______________________________________________
linux-arm-kernel mailing list
linux-arm-kernel@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-arm-kernel
next prev parent reply other threads:[~2024-01-23 13:56 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-21 11:46 [PATCH] dt-bindings: clock: support NXP i.MX95 Peng Fan (OSS)
2024-01-22 10:02 ` Krzysztof Kozlowski
2024-01-23 13:08 ` Peng Fan
2024-01-23 13:55 ` Krzysztof Kozlowski [this message]
2024-01-23 13:59 ` Peng Fan
2024-01-23 15:07 ` Krzysztof Kozlowski
2024-01-23 15:13 ` Peng Fan
2024-01-23 15:22 ` Krzysztof Kozlowski
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=78e296fb-a3dc-4e00-94bc-91dab7294887@linaro.org \
--to=krzysztof.kozlowski@linaro.org \
--cc=abelvesa@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=festevam@gmail.com \
--cc=kernel@pengutronix.de \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-imx@nxp.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=peng.fan@oss.nxp.com \
--cc=robh+dt@kernel.org \
--cc=s.hauer@pengutronix.de \
--cc=sboyd@kernel.org \
--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