From: Sascha Hauer <s.hauer@pengutronix.de>
To: BAREBOX <barebox@lists.infradead.org>
Subject: [PATCH 0/9] Unify SoC UID and machine hashable data
Date: Thu, 13 Nov 2025 10:34:24 +0100 [thread overview]
Message-ID: <20251113-soc-uid-v1-0-29a256e07144@pengutronix.de> (raw)
SoC UID and machine hashable data are both based on the same data but
are both registered at different places with different functions.
This series aims to unify this by adding a function which uses the
passed SoC UID to provide it to the environment and also to register
machine hashable data.
The SoC ID code on i.MX is quite a mess and this series cleans this
up a bit. We have drivers/nvmem/ocotp.c which reads the SoC ID and
provides machine hashable data and we have drivers/soc/imx/soc-imx8m.c
which implements a SoC driver and exposes soc0.serial_number, but
the SoC driver only works on i.MX8M which is a subset of the SoCs
supported by the ocotp driver.
Furthermore I realized that on i.MX8MP the SoC ID is 128bit whereas
we currently only use 64bit which additionally read from the wrong
registers. This series fixes this, but doing so will change the
machine_id passed to Linux which may break userspace, so this change
might need some discussion. Maybe we need a way to keep the previous
machine_id for already rolled out devices.
Signed-off-by: Sascha Hauer <s.hauer@pengutronix.de>
---
Sascha Hauer (9):
introduce SoC UID
soc: imx8mp: Soc ID is 128bit
ARM: i.MX6: print leading zero for SoC ID
nvmem: bsec: call barebox_set_soc_uid()
nvmem: imx-ocotp-ele: call barebox_set_soc_uid()
nvmem: ocotp: Fix SoC ID reading for i.MX8MP
nvmem: imx-ocotp: call barebox_set_soc_uid()
soc: imx8m: register SoC UID
Documentation: migration: add i.MX8MP SoC UID change note
.../migration-guides/migration-master.rst | 8 +++
arch/arm/mach-imx/imx6.c | 2 +-
common/misc.c | 58 ++++++++++++++++++++++
drivers/nvmem/bsec.c | 8 +--
drivers/nvmem/imx-ocotp-ele.c | 12 +++--
drivers/nvmem/ocotp.c | 40 ++++++++++++---
drivers/soc/imx/soc-imx8m.c | 37 ++++++++++----
include/barebox-info.h | 4 ++
8 files changed, 144 insertions(+), 25 deletions(-)
---
base-commit: 45b4b47cc650b0552d4920d0a353a860f6d2468c
change-id: 20251113-soc-uid-21daee8feac6
Best regards,
--
Sascha Hauer <s.hauer@pengutronix.de>
next reply other threads:[~2025-11-13 9:35 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-11-13 9:34 Sascha Hauer [this message]
2025-11-13 9:34 ` [PATCH 1/9] introduce SoC UID Sascha Hauer
2025-11-13 9:34 ` [PATCH 2/9] soc: imx8mp: Soc ID is 128bit Sascha Hauer
2025-11-14 16:22 ` Marco Felsch
2025-11-14 20:08 ` Sascha Hauer
2025-11-13 9:34 ` [PATCH 3/9] ARM: i.MX6: print leading zero for SoC ID Sascha Hauer
2025-11-13 9:34 ` [PATCH 4/9] nvmem: bsec: call barebox_set_soc_uid() Sascha Hauer
2025-11-13 9:34 ` [PATCH 5/9] nvmem: imx-ocotp-ele: " Sascha Hauer
2025-11-13 9:34 ` [PATCH 6/9] nvmem: ocotp: Fix SoC ID reading for i.MX8MP Sascha Hauer
2025-11-13 9:34 ` [PATCH 7/9] nvmem: imx-ocotp: call barebox_set_soc_uid() Sascha Hauer
2025-11-13 9:34 ` [PATCH 8/9] soc: imx8m: register SoC UID Sascha Hauer
2025-11-13 9:34 ` [PATCH 9/9] Documentation: migration: add i.MX8MP SoC UID change note Sascha Hauer
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=20251113-soc-uid-v1-0-29a256e07144@pengutronix.de \
--to=s.hauer@pengutronix.de \
--cc=barebox@lists.infradead.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