From: Marek Vasut <marex@denx.de>
To: Alexandre TORGUE <alexandre.torgue@foss.st.com>,
linux-arm-kernel@lists.infradead.org
Cc: Christophe Roullier <christophe.roullier@foss.st.com>,
Conor Dooley <conor+dt@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Maxime Coquelin <mcoquelin.stm32@gmail.com>,
Rob Herring <robh@kernel.org>,
devicetree@vger.kernel.org, kernel@dh-electronics.com,
linux-stm32@st-md-mailman.stormreply.com
Subject: Re: [PATCH] ARM: dts: stm32: Add phandle to nvmem efuse into STM32MP13xx ethernet DT node
Date: Fri, 28 Jun 2024 02:56:12 +0200 [thread overview]
Message-ID: <a1529d38-ce85-43e9-929e-017a42628b64@denx.de> (raw)
In-Reply-To: <8fb70911-a278-43b3-bcaf-c88b43bddb73@foss.st.com>
On 6/27/24 2:13 PM, Alexandre TORGUE wrote:
> Hi Marek
Hi,
> On 6/23/24 21:15, Marek Vasut wrote:
>> The efuses on STM32MP13xx can be populated with ethernet MAC address.
>> Add the nvmem-cells/nvmem-cell-name DT properties to ethernet MAC DT
>> nodes to describe the placement of both MAC address fields within the
>> efuses, so the ethernet MAC driver can access the efuses and populate
>> the correct MAC address into the hardware.
>>
>> Signed-off-by: Marek Vasut <marex@denx.de>
>> ---
>> Cc: Alexandre Torgue <alexandre.torgue@foss.st.com>
>> Cc: Christophe Roullier <christophe.roullier@foss.st.com>
>> Cc: Conor Dooley <conor+dt@kernel.org>
>> Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
>> Cc: Maxime Coquelin <mcoquelin.stm32@gmail.com>
>> Cc: Rob Herring <robh@kernel.org>
>> Cc: devicetree@vger.kernel.org
>> Cc: kernel@dh-electronics.com
>> Cc: linux-arm-kernel@lists.infradead.org
>> Cc: linux-stm32@st-md-mailman.stormreply.com
>> ---
>> arch/arm/boot/dts/st/stm32mp131.dtsi | 2 ++
>> arch/arm/boot/dts/st/stm32mp133.dtsi | 2 ++
>> 2 files changed, 4 insertions(+)
>>
>> diff --git a/arch/arm/boot/dts/st/stm32mp131.dtsi
>> b/arch/arm/boot/dts/st/stm32mp131.dtsi
>> index f41508195eb51..55f4150524f3c 100644
>> --- a/arch/arm/boot/dts/st/stm32mp131.dtsi
>> +++ b/arch/arm/boot/dts/st/stm32mp131.dtsi
>> @@ -1528,6 +1528,8 @@ ethernet1: ethernet@5800a000 {
>> <&rcc ETH1RX>,
>> <&rcc ETH1STP>,
>> <&rcc ETH1CK_K>;
>> + nvmem-cell-names = "mac-address";
>> + nvmem-cells = <ðernet_mac1_address>;
>
> It should not be defined in soc dtsi file but rather in board file. OTP
> are provisioned by the end customer not by ST. If you order a SoC to ST
> it will not be provisioned OTP MAC addr will be set to 0.
That's right, but at least the MAC address will be in the same locations
in OTP, and if the MAC from OTP is all zeroes, than it wouldn't be
considered a valid MAC address.
In any case, I'll do board specific V2 shortly.
prev parent reply other threads:[~2024-06-28 1:49 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-23 19:15 [PATCH] ARM: dts: stm32: Add phandle to nvmem efuse into STM32MP13xx ethernet DT node Marek Vasut
2024-06-27 12:13 ` Alexandre TORGUE
2024-06-28 0:56 ` Marek Vasut [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=a1529d38-ce85-43e9-929e-017a42628b64@denx.de \
--to=marex@denx.de \
--cc=alexandre.torgue@foss.st.com \
--cc=christophe.roullier@foss.st.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@dh-electronics.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-stm32@st-md-mailman.stormreply.com \
--cc=mcoquelin.stm32@gmail.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).