[PATCH 0/3] arm: meson: extend sm calls to support Amlogic chip_id v1, v2
neil.armstrong at linaro.org
neil.armstrong at linaro.org
Mon Feb 24 20:54:06 CET 2025
From: Neil Armstrong <neil.armstrong at linaro.org>
Hi,
On Mon, 10 Feb 2025 20:50:13 +0300, Evgeny Bachinin wrote:
> The Amlogic Meson SoC secure monitor (TF-A) handles a call (0x82000044)
> to retrieve a chip_id from eFuse OTP data [1].
>
> Previously, this sm call (0x82000044) was used to retrieve just unique
> SoC number [2] (a.k.a. SoC "serial" [3]), identifying particular die.
> This SoC serial, stored in the eFuse, is always 12 bytes long.
>
> [...]
Thanks, Applied to https://source.denx.de/u-boot/custodians/u-boot-amlogic (u-boot-amlogic-next)
[1/3] arm: meson: unify type being used for socinfo
https://source.denx.de/u-boot/custodians/u-boot-amlogic/-/commit/bcacf50d9defd49f12335866570fb41753bc9dc7
[2/3] arm: meson: sm: get rid of SM_CHIP_ID_SIZE
https://source.denx.de/u-boot/custodians/u-boot-amlogic/-/commit/a64a4149e39b574bb8d550da1356209caa75274e
[3/3] arch: arm: meson: support Amlogic chip_id v1 and v2
https://source.denx.de/u-boot/custodians/u-boot-amlogic/-/commit/f6b4f91117984a3ecba486f728b9619e75f06d52
--
Neil
More information about the U-Boot
mailing list