[PATCH v3 2/2] i.MX: HAB: update text for HABV4_CSF_UNLOCK_UID

[Fabian Pflug]

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.

Reviewed-by: Jonas Rebmann <jre at pengutronix.de>
Signed-off-by: Fabian Pflug <f.pflug at pengutronix.de>
---
 arch/arm/mach-imx/Kconfig | 13 +++++++------
 1 file changed, 7 insertions(+), 6 deletions(-)

diff --git a/arch/arm/mach-imx/Kconfig b/arch/arm/mach-imx/Kconfig
index 2e4d1ac80a..75086d13e6 100644
--- a/arch/arm/mach-imx/Kconfig
+++ b/arch/arm/mach-imx/Kconfig
@@ -918,19 +918,20 @@ 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:
+	  stored in $global.soc_uid_hex, but must be split into bytes.
+	  The soc_uid_hex 0011223344556677 becomes:
+	    - 0x00, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77
+
+	  Alternatively, it is printed in reverse byte order during boot
 	    i.MX___ unique ID: 7766554433221100
-	  or it can be queried by Linux via:
+	  or it can be queried (in reverse byte order) by Linux via:
 	    - cat /sys/devices/soc0/serial_number
 	      7766554433221100
 
-	  So this value have to be set:
-	    - 0x00, 0x11, 0x22, 0x33, 0x44, 0x55, 0x66, 0x77
-
 	  Afterwards, the `hab -p -r` command can be used to burn the fuse.
 
 config HAB_CERTS_ENV

-- 
2.47.3