From: Stefan Kerkmann <s.kerkmann@pengutronix.de>
To: Sascha Hauer <s.hauer@pengutronix.de>,
BAREBOX <barebox@lists.infradead.org>
Cc: Stefan Kerkmann <s.kerkmann@pengutronix.de>
Subject: [PATCH v3 09/10] i.mx8: ocotp: add GPx_LOCK defines
Date: Thu, 23 Jan 2025 15:56:14 +0100 [thread overview]
Message-ID: <20250123-v2024-05-0-topic-hab-v3-9-e90d0e43c2de@pengutronix.de> (raw)
In-Reply-To: <20250123-v2024-05-0-topic-hab-v3-0-e90d0e43c2de@pengutronix.de>
The GPx_LOCK registers changed position in the fuse map from the i.MX6
series and derivates to the i.MX8 series with i.MX8MP being different
again.
The defines have been derived from:
IMX8MNRM Rev. 2 (i.MX8MN)
IMX8MPRM Rev. 3 (i.MX8MP)
IMX8MMRM Rev. 3 (i.MX8MM)
Signed-off-by: Stefan Kerkmann <s.kerkmann@pengutronix.de>
---
include/mach/imx/ocotp-fusemap.h | 16 ++++++++++++++++
1 file changed, 16 insertions(+)
diff --git a/include/mach/imx/ocotp-fusemap.h b/include/mach/imx/ocotp-fusemap.h
index 37f1ee8298c2ae47406c6ae58b73f1eba9effed8..3c961998b0fc4bd374331342baaa2051163309ae 100644
--- a/include/mach/imx/ocotp-fusemap.h
+++ b/include/mach/imx/ocotp-fusemap.h
@@ -12,6 +12,22 @@
#define OCOTP_MAC_ADDR_LOCK (OCOTP_WORD(0x400) | OCOTP_BIT(8) | OCOTP_WIDTH(2))
#define OCOTP_GP1_LOCK (OCOTP_WORD(0x400) | OCOTP_BIT(10) | OCOTP_WIDTH(2))
#define OCOTP_GP2_LOCK (OCOTP_WORD(0x400) | OCOTP_BIT(12) | OCOTP_WIDTH(2))
+
+/* available on i.MX8 */
+#define MX8M_OCOTP_GP1_LOCK (OCOTP_WORD(0x400) | OCOTP_BIT(20) | OCOTP_WIDTH(2))
+#define MX8M_OCOTP_GP2_LOCK (OCOTP_WORD(0x400) | OCOTP_BIT(22) | OCOTP_WIDTH(2))
+#define MX8M_OCOTP_GP5_LOCK (OCOTP_WORD(0x400) | OCOTP_BIT(24) | OCOTP_WIDTH(2))
+
+/* available on i.MX8MP */
+#define MX8MP_OCOTP_GP1_LOCK MX8M_OCOTP_GP1_LOCK
+#define MX8MP_OCOTP_GP2_LOCK MX8M_OCOTP_GP2_LOCK
+#define MX8MP_OCOTP_GP4_LOCK (OCOTP_WORD(0x410) | OCOTP_BIT(4) | OCOTP_WIDTH(2))
+#define MX8MP_OCOTP_GP5_LOCK (OCOTP_WORD(0x410) | OCOTP_BIT(8) | OCOTP_WIDTH(2))
+#define MX8MP_OCOTP_GP6_LOCK (OCOTP_WORD(0x410) | OCOTP_BIT(10) | OCOTP_WIDTH(2))
+#define MX8MP_OCOTP_GP7_LOCK (OCOTP_WORD(0x410) | OCOTP_BIT(12) | OCOTP_WIDTH(2))
+#define MX8MP_OCOTP_GP8_LOCK (OCOTP_WORD(0x410) | OCOTP_BIT(14) | OCOTP_WIDTH(2))
+#define MX8MP_OCOTP_GP9_LOCK (OCOTP_WORD(0x410) | OCOTP_BIT(16) | OCOTP_WIDTH(2))
+
#define OCOTP_SRK_LOCK (OCOTP_WORD(0x400) | OCOTP_BIT(14) | OCOTP_WIDTH(1))
#define OCOTP_ANALOG_LOCK (OCOTP_WORD(0x400) | OCOTP_BIT(18) | OCOTP_WIDTH(2))
#define OCOTP_MISC_CONF_LOCK (OCOTP_WORD(0x400) | OCOTP_BIT(22) | OCOTP_WIDTH(1))
--
2.39.5
next prev parent reply other threads:[~2025-01-23 15:01 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-23 14:56 [PATCH v3 00/10] i.MX8M HAB and OCOTP additions and fixes Stefan Kerkmann
2025-01-23 14:56 ` [PATCH v3 01/10] nvmem: ocotp: add support to get/set srk_revoke sticky bit Stefan Kerkmann
2025-01-23 14:56 ` [PATCH v3 02/10] nvmem: ocotp: add support to query the field-return " Stefan Kerkmann
2025-01-23 14:56 ` [PATCH v3 03/10] hab: convert flags to use BIT() macro Stefan Kerkmann
2025-01-23 14:56 ` [PATCH v3 04/10] i.MX: HAB: add imx_hab_revoke_key support Stefan Kerkmann
2025-01-23 14:56 ` [PATCH v3 05/10] i.MX: HABv4: add more i.MX8M fuse defines Stefan Kerkmann
2025-01-23 14:56 ` [PATCH v3 06/10] i.MX8M: HABv4: add an option to allow key revocation Stefan Kerkmann
2025-01-23 14:56 ` [PATCH v3 07/10] i.MX8M: HABv4: add option to allow burning the field-return fuse Stefan Kerkmann
2025-01-23 14:56 ` [PATCH v3 08/10] i.MX: HAB: add imx_hab_field_return support Stefan Kerkmann
2025-01-23 14:56 ` Stefan Kerkmann [this message]
2025-01-23 14:56 ` [PATCH v3 10/10] hab: lock GP5 on i.MX8MP socs Stefan Kerkmann
2025-01-28 10:00 ` [PATCH v3 00/10] i.MX8M HAB and OCOTP additions and fixes 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=20250123-v2024-05-0-topic-hab-v3-9-e90d0e43c2de@pengutronix.de \
--to=s.kerkmann@pengutronix.de \
--cc=barebox@lists.infradead.org \
--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