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] i.mx8: ocotp: add GPx defines
Date: Tue, 25 Feb 2025 11:56:40 +0100 [thread overview]
Message-ID: <20250225-imx8-ocotp-gp-defines-v1-1-344b291675a7@pengutronix.de> (raw)
The general purpose GPx registers changed position in the fuse map from
the i.MX6 series and derivates to the i.MX8 series. The i.MX8MP has 4
additional 128-bit wide fuse banks which have been added as well.
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 | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
diff --git a/include/mach/imx/ocotp-fusemap.h b/include/mach/imx/ocotp-fusemap.h
index 3c961998b0fc4bd374331342baaa2051163309ae..74f3a55d182d50046d7d544603110fefd590e368 100644
--- a/include/mach/imx/ocotp-fusemap.h
+++ b/include/mach/imx/ocotp-fusemap.h
@@ -17,6 +17,10 @@
#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))
+#define MX8M_OCOTP_GP1_0 (OCOTP_WORD(0x780) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8M_OCOTP_GP1_1 (OCOTP_WORD(0x790) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8M_OCOTP_GP2_0 (OCOTP_WORD(0x7A0) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8M_OCOTP_GP2_1 (OCOTP_WORD(0x7B0) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
/* available on i.MX8MP */
#define MX8MP_OCOTP_GP1_LOCK MX8M_OCOTP_GP1_LOCK
@@ -27,6 +31,22 @@
#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 MX8MP_OCOTP_GP6_0 (OCOTP_WORD(0xE40) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP6_1 (OCOTP_WORD(0xE50) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP6_2 (OCOTP_WORD(0xE60) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP6_3 (OCOTP_WORD(0xE70) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP7_0 (OCOTP_WORD(0xE80) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP7_1 (OCOTP_WORD(0xE90) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP7_2 (OCOTP_WORD(0xEA0) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP7_3 (OCOTP_WORD(0xEB0) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP8_0 (OCOTP_WORD(0xEC0) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP8_1 (OCOTP_WORD(0xED0) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP8_2 (OCOTP_WORD(0xEE0) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP8_3 (OCOTP_WORD(0xEF0) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP9_0 (OCOTP_WORD(0xF00) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP9_1 (OCOTP_WORD(0xF30) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP9_2 (OCOTP_WORD(0xF40) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
+#define MX8MP_OCOTP_GP9_3 (OCOTP_WORD(0xF50) | OCOTP_BIT(0) | OCOTP_WIDTH(32))
#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))
---
base-commit: a2e7a50e3417b93effd9cce56ea94fec8b40f814
change-id: 20250225-imx8-ocotp-gp-defines-2990fa080367
Best regards,
--
Stefan Kerkmann <s.kerkmann@pengutronix.de>
reply other threads:[~2025-02-25 12:03 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=20250225-imx8-ocotp-gp-defines-v1-1-344b291675a7@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