From: Bryan Brattlof <bb@ti.com>
To: Tom Rini <trini@konsulko.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Hari Nagalla <hnagalla@ti.com>
Cc: Lukasz Majewski <lukma@denx.de>,
Sean Anderson <seanga2@gmail.com>,
Jaehoon Chung <jh80.chung@samsung.com>,
Simon Glass <sjg@chromium.org>,
Sumit Garg <sumit.garg@linaro.org>, Nishanth Menon <nm@ti.com>,
Andrew Davis <afd@ti.com>, Neha Malcom Francis <n-francis@ti.com>,
UBoot Mailing List <u-boot@lists.denx.de>,
Bryan Brattlof <bb@ti.com>
Subject: [PATCH v2 01/13] soc: add info to identify the am62p SoC family
Date: Wed, 31 Jan 2024 21:06:37 -0600 [thread overview]
Message-ID: <20240201030634.1120963-18-bb@ti.com> (raw)
In-Reply-To: <20240201030634.1120963-16-bb@ti.com>
Include the part number for TI's am62px family of SoCs so we can
properly identify it during boot
Signed-off-by: Bryan Brattlof <bb@ti.com>
---
arch/arm/mach-k3/include/mach/hardware.h | 2 ++
drivers/soc/soc_ti_k3.c | 3 +++
2 files changed, 5 insertions(+)
diff --git a/arch/arm/mach-k3/include/mach/hardware.h b/arch/arm/mach-k3/include/mach/hardware.h
index a1a9dfbde66c8..040288150b12f 100644
--- a/arch/arm/mach-k3/include/mach/hardware.h
+++ b/arch/arm/mach-k3/include/mach/hardware.h
@@ -46,6 +46,7 @@
#define JTAG_ID_PARTNO_J721S2 0xbb75
#define JTAG_ID_PARTNO_AM62X 0xbb7e
#define JTAG_ID_PARTNO_AM62AX 0xbb8d
+#define JTAG_ID_PARTNO_AM62PX 0xbb9d
#define K3_SOC_ID(id, ID) \
static inline bool soc_is_##id(void) \
@@ -61,6 +62,7 @@ K3_SOC_ID(am64x, AM64X)
K3_SOC_ID(j721s2, J721S2)
K3_SOC_ID(am62x, AM62X)
K3_SOC_ID(am62ax, AM62AX)
+K3_SOC_ID(am62px, AM62PX)
#define K3_SEC_MGR_SYS_STATUS 0x44234100
#define SYS_STATUS_DEV_TYPE_SHIFT 0
diff --git a/drivers/soc/soc_ti_k3.c b/drivers/soc/soc_ti_k3.c
index 355a5368dd45a..d7d0152b115fa 100644
--- a/drivers/soc/soc_ti_k3.c
+++ b/drivers/soc/soc_ti_k3.c
@@ -45,6 +45,9 @@ static const char *get_family_string(u32 idreg)
case JTAG_ID_PARTNO_AM62AX:
family = "AM62AX";
break;
+ case JTAG_ID_PARTNO_AM62PX:
+ family = "AM62PX";
+ break;
default:
family = "Unknown Silicon";
};
--
2.43.0
next prev parent reply other threads:[~2024-02-01 3:07 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-02-01 3:06 [PATCH] arm: dts: k3-am62p5: enable the wkup i2c bus Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 00/13] Introduce basic support for TI's AM62Px SoC family Bryan Brattlof
2024-02-02 8:03 ` Sumit Garg
2024-02-02 16:36 ` Bryan Brattlof
2024-02-01 3:06 ` Bryan Brattlof [this message]
2024-02-01 14:41 ` [PATCH v2 01/13] soc: add info to identify the am62p " Igor Opaniuk
2024-02-01 3:06 ` [PATCH v2 02/13] power: domain: ti: use IS_ENABLED macro Bryan Brattlof
2024-02-01 14:46 ` Igor Opaniuk
2024-02-01 3:06 ` [PATCH v2 03/13] arm: mach-k3: am62px: introduce clock and device files for wkup spl Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 04/13] ram: k3-ddrss: enable the am62ax's DDR controller for am62px Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 05/13] arm: mach-k3: invert logic for split DM firmware config Bryan Brattlof
2024-02-02 16:44 ` Andrew Davis
2024-02-02 17:12 ` Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 06/13] arch: mach-k3: introduce basic files to support the am62px SoC family Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 07/13] board: ti: introduce basic board files for the am62px family Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 08/13] firmware: ti_sci_static_data: add static DMA channel data Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 09/13] dma: ti: k3-udma: Add DMA PSIL mappings for AM62P and J722S Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 10/13] arm: dts: introduce am62p5 uboot dts files Bryan Brattlof
2024-02-02 15:53 ` Andrew Davis
2024-02-02 16:28 ` Bryan Brattlof
2024-02-02 16:36 ` Andrew Davis
2024-02-02 17:06 ` Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 11/13] Makefile: remove hardcoded device tree source directory Bryan Brattlof
2024-02-02 7:57 ` Sumit Garg
2024-02-01 3:06 ` [PATCH v2 12/13] configs: introduce configs needed for the am62px Bryan Brattlof
2024-02-01 3:06 ` [PATCH v2 13/13] doc: board: ti: introduce am62px documentation Bryan Brattlof
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=20240201030634.1120963-18-bb@ti.com \
--to=bb@ti.com \
--cc=afd@ti.com \
--cc=hnagalla@ti.com \
--cc=jh80.chung@samsung.com \
--cc=lukma@denx.de \
--cc=n-francis@ti.com \
--cc=nm@ti.com \
--cc=seanga2@gmail.com \
--cc=sjg@chromium.org \
--cc=sumit.garg@linaro.org \
--cc=trini@konsulko.com \
--cc=u-boot@lists.denx.de \
--cc=vigneshr@ti.com \
/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