From: Judith Mendez <jm@ti.com>
To: Judith Mendez <jm@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Santosh Shilimkar <ssantosh@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Andrew Davis <afd@ti.com>
Subject: [PATCH v2 0/2] Add AM62P silicon revision detection via NVMEM
Date: Fri, 6 Feb 2026 13:19:12 -0600 [thread overview]
Message-ID: <20260206191914.52878-1-jm@ti.com> (raw)
This series adds support for detecting AM62P silicon revisions using
the NVMEM framework to read the GP_SW1 register.
Background:
===========
On AM62P SoCs, the standard JTAGID register does not provide information
on silicon revision, instead the GP_SW1 register contains the information
needed for proper device identification.
Proper silicon revision detection is required to apply proper workarounds
and quirks for different silicon revisions, particularly for MMCSD [0].
Implementation history:
=======================
An initial implementation [0] added a second register range directly to
the chipid node to access GP_SW registers. Following upstream review
feedback to split the patches appropriately, an alternative RFC approach
[1] was explored that introduced a new NVMEM eFuse binding specifically
for TI K3 SoCs.
This final implementation takes a simpler approach by leveraging the
existing NVMEM framework with optional nvmem-cells support. The k3-socinfo
driver can now optionally consume silicon revision data from the NVMEM
provider, making it more flexible and avoiding the need for either direct
register access or new bindings.
Implementation details:
=======================
- NVMEM support is fully optional - the driver continues to work without
it and falls back to SR1.0 for AM62P devices
- When NVMEM cells are present, the driver reads GP_SW1 to accurately
detect SR1.1 and SR1.2 variants
Changelog:
==========
since v1:
- Drop valid bit check, and determine all silicon revisions from ADR
register bits
- In k3_chipinfo_get_gpsw_variant, merge detection of final return value
and return action
- k3_chipinfo_get_gpsw_variant parameter: switch pdev to dev
Revisions:
==========
v1: https://lore.kernel.org/all/20260204213746.2589028-1-jm@ti.com/
[0] https://lore.kernel.org/linux-mmc/20250805234950.3781367-1-jm@ti.com/
[1] https://lore.kernel.org/all/20250924210735.1732423-1-jm@ti.com/
Judith Mendez (2):
dt-bindings: hwinfo: ti,k3-socinfo: Add nvmem-cells support
soc: ti: k3-socinfo: Add support for AM62P variants via NVMEM
.../bindings/hwinfo/ti,k3-socinfo.yaml | 12 ++++++
drivers/soc/ti/k3-socinfo.c | 41 +++++++++++++++++--
2 files changed, 50 insertions(+), 3 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-06 19:19 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-06 19:19 Judith Mendez [this message]
2026-02-06 19:19 ` [PATCH v2 1/2] dt-bindings: hwinfo: ti,k3-socinfo: Add nvmem-cells support Judith Mendez
2026-02-07 10:44 ` Krzysztof Kozlowski
2026-02-06 19:19 ` [PATCH v2 2/2] soc: ti: k3-socinfo: Add support for AM62P variants via NVMEM Judith Mendez
2026-02-06 20:22 ` Andrew Davis
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=20260206191914.52878-1-jm@ti.com \
--to=jm@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=ssantosh@kernel.org \
--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