From: Moteen Shah <m-shah@ti.com>
To: <conor+dt@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<nm@ti.com>, <ssantosh@kernel.org>
Cc: <u-kumar1@ti.com>, <gehariprasath@ti.com>, <m-shah@ti.com>,
<vigneshr@ti.com>, <afd@ti.com>, <a-limaye@ti.com>,
<y-abhilashchandra@ti.com>, <johan@kernel.org>, <kees@kernel.org>,
<jm@ti.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH v2 0/3] soc: ti: Add TDA54 SCM configuration syscon support
Date: Tue, 27 Oct 2026 14:06:57 +0530 [thread overview]
Message-ID: <20261027083700.1964371-1-m-shah@ti.com> (raw)
This series adds support for the TDA54 SCM configuration region in the MCU
domain. The region is shared by several peripherals, so it is exposed as a
syscon regmap for other drivers to look up by phandle.
Patch 1 adds the device tree binding for ti,tda54-mcu-scm-conf.
Patch 2 splits the SoC decode and registration logic out of
k3_chipinfo_probe() into k3_socinfo_register() and exports it. The helper
lets other drivers register SoC information after reading the JTAG ID through
their own access path, and uses devm cleanup for registered SoC devices and
their attributes.
Patch 3 adds the TDA54 SCM configuration driver. It provides proxy-aware
register access with SCM unlock and claim handling, publishes the regmap
through syscon, and registers TDA54 SoC information through the helper from
patch 2. The option defaults to m on ARCH_K3.
Changelog:
Link to V1: https://lore.kernel.org/all/20261019080736.944127-1-m-shah@ti.com/
Changes in v2:
- No changes to the device tree binding patch.
- Use devm-managed allocation for the SoC attributes and revision string in
k3-socinfo, and simplify the cleanup of the registered SoC device.
- Enable fast_io for the TDA54 SCM configuration regmap.
Moteen Shah (3):
dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf binding
soc: ti: k3-socinfo: Export SoC registration helper
soc: ti: Add TDA54 SCM configuration syscon support
.../soc/ti/ti,tda54-mcu-scm-conf.yaml | 78 +++++++
drivers/soc/ti/Kconfig | 16 ++
drivers/soc/ti/Makefile | 1 +
drivers/soc/ti/k3-socinfo.c | 121 ++++++----
drivers/soc/ti/tda54-mcu-sysconf.c | 217 ++++++++++++++++++
include/linux/soc/ti/k3-socinfo.h | 11 +
6 files changed, 402 insertions(+), 42 deletions(-)
create mode 100644 Documentation/devicetree/bindings/soc/ti/ti,tda54-mcu-scm-conf.yaml
create mode 100644 drivers/soc/ti/tda54-mcu-sysconf.c
create mode 100644 include/linux/soc/ti/k3-socinfo.h
--
2.34.1
next reply other threads:[~2026-10-27 8:38 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-27 8:36 Moteen Shah [this message]
2026-10-27 8:36 ` [PATCH v2 1/3] dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf binding Moteen Shah
2026-10-28 12:24 ` Krzysztof Kozlowski
2026-10-27 8:36 ` [PATCH v2 2/3] soc: ti: k3-socinfo: Export SoC registration helper Moteen Shah
2026-10-27 8:37 ` [PATCH v2 3/3] soc: ti: Add TDA54 SCM configuration syscon support Moteen Shah
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=20261027083700.1964371-1-m-shah@ti.com \
--to=m-shah@ti.com \
--cc=a-limaye@ti.com \
--cc=afd@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=gehariprasath@ti.com \
--cc=jm@ti.com \
--cc=johan@kernel.org \
--cc=kees@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=u-kumar1@ti.com \
--cc=vigneshr@ti.com \
--cc=y-abhilashchandra@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