mail archive of the barebox mailing list
 help / color / mirror / Atom feed
From: Jonas Rebmann <jre@pengutronix.de>
To: Fabian Pflug <f.pflug@pengutronix.de>,
	Sascha Hauer <s.hauer@pengutronix.de>,
	BAREBOX <barebox@lists.infradead.org>
Subject: Re: [PATCH 2/2] i.MX: HAB: update text for HABV4_CSF_UNLOCK_UID
Date: Mon, 13 Apr 2026 10:21:52 +0200	[thread overview]
Message-ID: <0b4961bd-7195-4d73-8692-e6d5828ba02a@pengutronix.de> (raw)
In-Reply-To: <20260330-v2026-03-0-topic-soc_bin_id-v1-2-11292f75b196@pengutronix.de>

On 2026-03-30 14:24, Fabian Pflug wrote:
> With the establishment of global.soc_uid_bin, there is no need to look
> for the serial number and reverse it.

I don't believe reverting the byte order manually is something we were
supposed to be doing before.

> 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..bfcb6ae402 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
> -
> -	  So this value have to be set:
> +	  is stored in $global.soc_uid_bin, but must be split into bytes.

"The UNIQUE_ID is is stored"?

> +	  The soc_uid_bin 0011223344556677 becomes:
>   	    - 0x00, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77

I never used this feature but is there any good reason why this should
consume a different format from what $global.soc_uid_bin returns?

>   	  Afterwards, the `hab -p -r` command can be used to burn the fuse.
> 

-- 
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    |



  reply	other threads:[~2026-04-13  8:22 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-30 12:24 [PATCH 0/2] Add additional globalvar for soc_uid Fabian Pflug
2026-03-30 12:24 ` [PATCH 1/2] common: misc: add soc_uid_bin to globalvar Fabian Pflug
2026-04-13  8:21   ` Jonas Rebmann
2026-04-13  8:24   ` Ahmad Fatoum
2026-03-30 12:24 ` [PATCH 2/2] i.MX: HAB: update text for HABV4_CSF_UNLOCK_UID Fabian Pflug
2026-04-13  8:21   ` Jonas Rebmann [this message]
2026-04-14 11:04     ` Fabian Pflug
2026-04-13  8:21 ` [PATCH 0/2] Add additional globalvar for soc_uid Jonas Rebmann
2026-04-14 11:10   ` Fabian Pflug

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=0b4961bd-7195-4d73-8692-e6d5828ba02a@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