From: Jonas Rebmann <jre@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
Fabian Pflug <f.pflug@pengutronix.de>
Cc: BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH v2 2/2] i.MX: HAB: update text for HABV4_CSF_UNLOCK_UID
Date: Wed, 22 Apr 2026 11:47:20 +0200 [thread overview]
Message-ID: <9349d9e9-efe5-48d4-95c0-56f322611b3c@pengutronix.de> (raw)
In-Reply-To: <aeh8E8taV-bxPoK_@pengutronix.de>
Hi,
On 2026-04-22 09:43, Sascha Hauer wrote:
> Hi Fabian,
>
> On Wed, Apr 15, 2026 at 01:10:22PM +0200, Fabian Pflug wrote:
>> With the establishment of global.soc_uid_hex, there is no need to look
>> for the serial number and reverse it.
>>
>> Also some SoC's will have 128-bit UID's, so the hint to 64-bit is not
>> correct and should be removed.
>>
>> Signed-off-by: Fabian Pflug <f.pflug@pengutronix.de>
>> ---
>> arch/arm/mach-imx/Kconfig | 11 +++--------
>> 1 file changed, 3 insertions(+), 8 deletions(-)
>>
>> diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig
>> index 2e4d1ac80a..cb77d0d5b6 100644
>> --- a/arch/arm/mach-imx/Kconfig
>> +++ b/arch/arm/mach-imx/Kconfig
>> @@ -918,17 +918,12 @@ config HABV4_CSF_UNLOCK_UID
>> depends on HABV4 && HABV4_CSF_UNLOCK_FIELD_RETURN
>> string "CSF Unlock UID"
>> help
>> - Device specific 64-bit UID required to unlock the field-return
>> + Device specific UID required to unlock the field-return
>> feature. This value must match the per device UNIQUE_ID fuses.
>>
>> The below example shows the expected format. The UNIQUE_ID is
>> - printed during boot by barebox:
>> - i.MX___ unique ID: 7766554433221100
>> - or it can be queried by Linux via:
>> - - cat /sys/devices/soc0/serial_number
>> - 7766554433221100
>
> I don't think we should remove this. For some people it might be more
> convenient to read the SoC UID from Linux or to parse it from the
> barebox console log.
If instructions of reversing /sys/devices/soc0/serial_number are kept, I
suggest to indicate that it's Linux' that prints them in reverse on
i.MX. `drivers/soc/imx/soc-imx8m.c` and `soc-imx.c` flat out present the
SoC UID in reverse order, at least consistently across i.MX SoCs.
There is an unambiguous order of the byteorder in the registers; and for
reasons beyond my comprehension (inattention?) it was chosen for the
kernel to print them uid[16],uid[15],uid[14],... Although the vendor
seems to do the obvious and expect uid[0],uid[1],uid[2],...
Regards,
Jonas
--
Pengutronix e.K. | Jonas Rebmann |
Steuerwalder Str. 21 | http://www.pengutronix.de/ |
31137 Hildesheim, Germany | Phone: +49-5121-206917-0 |
Amtsgericht Hildesheim, HRA 2686 | Fax: +49-5121-206917-9 |
prev parent reply other threads:[~2026-04-22 9:47 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-15 11:10 [PATCH v2 0/2] Add additional globalvar for soc_uid Fabian Pflug
2026-04-15 11:10 ` [PATCH v2 1/2] common: misc: add soc_uid_hex to globalvar Fabian Pflug
2026-04-15 11:14 ` Jonas Rebmann
2026-04-22 7:56 ` Sascha Hauer
2026-04-22 8:14 ` Fabian Pflug
2026-04-22 8:25 ` Sascha Hauer
2026-04-22 8:52 ` Fabian Pflug
2026-04-22 9:16 ` Sascha Hauer
2026-04-22 9:19 ` Fabian Pflug
2026-04-22 9:38 ` Sascha Hauer
2026-04-15 11:10 ` [PATCH v2 2/2] i.MX: HAB: update text for HABV4_CSF_UNLOCK_UID Fabian Pflug
2026-04-15 11:14 ` Jonas Rebmann
2026-04-22 7:43 ` Sascha Hauer
2026-04-22 7:49 ` Fabian Pflug
2026-04-22 9:47 ` Jonas Rebmann [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=9349d9e9-efe5-48d4-95c0-56f322611b3c@pengutronix.de \
--to=jre@pengutronix.de \
--cc=barebox@lists.infradead.org \
--cc=f.pflug@pengutronix.de \
--cc=s.hauer@pengutronix.de \
/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