From: Daniel Golle <daniel@makrotopia.org>
To: AngeloGioacchino Del Regno <angelogioacchino.delregno@collabora.com>
Cc: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Matthias Brugger <matthias.bgg@gmail.com>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
linux-mediatek@lists.infradead.org
Subject: Re: [PATCH 1/4] arm64: dts: mediatek: mt7622: add 'serial' cell to efuse
Date: Wed, 17 Sep 2025 11:08:24 +0100 [thread overview]
Message-ID: <aMqImGmz0uf_aTUR@pidgin.makrotopia.org> (raw)
In-Reply-To: <87179c9f-cc7f-446f-9e8d-c84bddb48660@collabora.com>
On Wed, Sep 17, 2025 at 11:06:13AM +0200, AngeloGioacchino Del Regno wrote:
> Il 17/09/25 01:05, Daniel Golle ha scritto:
> > The efuse of the MediaTek MT7622 contains an 8-byte unique identifier.
> > Add a 'serial' cell covering those 8 bytes to the nvmem defininition of
> > the efuse to allow easy access from userspace, eg. to generate a
> > persistent random MAC address on boards like the BananaPi R64 which
> > doesn't have any factory-assigned addresses.
>
> Sorry, but I don't get why this is named "serial" and not "soc-uuid".
>
> Care to explain?
I don't have documentation covering the efuse content but only got this
information on an informal way:
https://forum.banana-pi.org/t/bpi-r3-serial-number/14556/10?u=dangowrt
Either name is fine with me, I thought of it as "serial number", but
obviously "soc-uuid" works fine, too.
I can change it to that and send v2 tonight.
next prev parent reply other threads:[~2025-09-17 10:08 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-16 23:05 [PATCH 1/4] arm64: dts: mediatek: mt7622: add 'serial' cell to efuse Daniel Golle
2025-09-16 23:05 ` [PATCH 2/4] arm64: dts: mediatek: mt7986a: " Daniel Golle
2025-09-16 23:05 ` [PATCH 3/4] arm64: dts: mediatek: mt7981b: " Daniel Golle
2025-09-16 23:05 ` [PATCH 4/4] arm64: dts: mediatek: mt7988a: " Daniel Golle
2025-09-17 9:06 ` [PATCH 1/4] arm64: dts: mediatek: mt7622: " AngeloGioacchino Del Regno
2025-09-17 10:08 ` Daniel Golle [this message]
2025-09-17 11:53 ` AngeloGioacchino Del Regno
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=aMqImGmz0uf_aTUR@pidgin.makrotopia.org \
--to=daniel@makrotopia.org \
--cc=angelogioacchino.delregno@collabora.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mediatek@lists.infradead.org \
--cc=matthias.bgg@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