From: Yann Gautier <yann.gautier@foss.st.com>
To: Rodolfo Giometti <giometti@enneenne.com>, <linux-kernel@vger.kernel.org>
Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Alexandre Torgue <alexandre.torgue@foss.st.com>,
Eric Fourmont <eric.fourmont-ext@st.com>
Subject: Re: [V1 1/2] arm stm32mp131.dtsi: add "encoding_mode" nvmem definition
Date: Tue, 20 May 2025 18:29:43 +0200 [thread overview]
Message-ID: <25eec2f8-8883-489e-a68b-3f80056bdc76@foss.st.com> (raw)
In-Reply-To: <f1ffb147-459a-4b3b-b109-9b07b25c99ac@foss.st.com>
On 5/20/25 10:26, Yann Gautier wrote:
> On 5/19/25 15:08, Rodolfo Giometti wrote:
>> This patch adds the definition for the nvmem location "encoding_mode"
>> related to the "cpu0" node.
>>
>> Signed-off-by: Rodolfo Giometti <giometti@enneenne.com>
>> ---
>> arch/arm/boot/dts/st/stm32mp131.dtsi | 7 +++++++
>> 1 file changed, 7 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/st/stm32mp131.dtsi
>> b/arch/arm/boot/dts/st/stm32mp131.dtsi
>> index e555717c0048..52bf497e26bb 100644
>> --- a/arch/arm/boot/dts/st/stm32mp131.dtsi
>> +++ b/arch/arm/boot/dts/st/stm32mp131.dtsi
>> @@ -24,6 +24,9 @@ cpu0: cpu@0 {
>> clocks = <&scmi_perf 0>;
>> clock-names = "cpu";
>> #cooling-cells = <2>;
>> +
>> + nvmem-cells = <&encoding_mode_otp>;
>> + nvmem-cell-names = "encoding_mode";
>> };
>> };
>> @@ -1167,6 +1170,10 @@ part_number_otp: part-number-otp@4 {
>> reg = <0x4 0x2>;
>> bits = <0 12>;
>> };
>> + encoding_mode_otp: encoding-mode-otp@4 {
>
> This node should end with @0 instead of 4.
> It should also be placed before part-number-otp node.
I forgot that this node already was in TF-A, with a different name.
This is better to align it here, the the node would become:
cfg0_otp: cfg0-otp@0 {
reg = <0x0 0x2>;
bits = <0 9>;
};
Best regards,
Yann
>
>> + reg = <0x0 0x1>;
>
> If I'm not mistaken, this should be:
> reg = <0x0 0x2>;
>
>
> Best regards,
> Yann
>
>> + bits = <0 9>;
>> + };
>> vrefint: vrefin-cal@52 {
>> reg = <0x52 0x2>;
>> };
>
next prev parent reply other threads:[~2025-05-20 16:32 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-19 13:08 [V1 0/2] Add SoC support for stm32mp13xx CPUs Rodolfo Giometti
2025-05-19 13:08 ` [V1 1/2] arm stm32mp131.dtsi: add "encoding_mode" nvmem definition Rodolfo Giometti
2025-05-19 18:35 ` Krzysztof Kozlowski
2025-05-19 18:36 ` Krzysztof Kozlowski
2025-05-20 8:26 ` Yann Gautier
2025-05-20 16:29 ` Yann Gautier [this message]
2025-05-19 13:08 ` [V1 2/2] drivers soc: add support for ST stm32mp13xx family Rodolfo Giometti
2025-05-19 18:34 ` Krzysztof Kozlowski
2025-05-20 9:01 ` Rodolfo Giometti
2025-05-20 9:15 ` Krzysztof Kozlowski
2025-05-20 8:55 ` Alexandre TORGUE
2025-05-26 10:56 ` Rodolfo Giometti
2025-05-20 16:58 ` Yann Gautier
2025-05-21 15:44 ` Rodolfo Giometti
2025-05-21 16:37 ` 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=25eec2f8-8883-489e-a68b-3f80056bdc76@foss.st.com \
--to=yann.gautier@foss.st.com \
--cc=alexandre.torgue@foss.st.com \
--cc=eric.fourmont-ext@st.com \
--cc=giometti@enneenne.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mcoquelin.stm32@gmail.com \
/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
all inboxes | Powered by JetHome®