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 v3 0/4] soc: ti: Add TDA54 SCM configuration syscon support
Date: Thu, 12 Nov 2026 13:40:43 +0530 [thread overview]
Message-ID: <20261112081047.1550471-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 converts the SoC attributes, revision string, and registered SoC device
in k3-socinfo to device-managed cleanup.
Patch 3 splits the SoC decode and registration logic out of
k3_chipinfo_probe() into k3_socinfo_register() and exports it, so drivers that
read the JTAG ID through another access path can reuse the common K3 SoC
identification logic.
Patch 4 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 3. The option defaults to m on ARCH_K3.
Changelog:
Link to v2: https://lore.kernel.org/all/20261027083700.1964371-1-m-shah@ti.com/
Changes in v3:
- Split the k3-socinfo device-managed cleanup changes from the exported SoC
registration helper into separate patches.
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 (4):
dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf
soc: ti: k3-socinfo: Use device managed allocations and unregistration
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 | 111 +++++----
drivers/soc/ti/tda54-mcu-sysconf.c | 217 ++++++++++++++++++
5 files changed, 380 insertions(+), 43 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
--
2.34.1
next reply other threads:[~2026-11-12 8:11 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-12 8:10 Moteen Shah [this message]
2026-11-12 8:10 ` [PATCH v3 1/4] dt-bindings: soc: ti: Document the ti,tda54-mcu-scm-conf Moteen Shah
2026-11-12 8:10 ` [PATCH v3 2/4] soc: ti: k3-socinfo: Use device managed allocations and unregistration Moteen Shah
2026-11-12 8:10 ` [PATCH v3 3/4] soc: ti: k3-socinfo: Export SoC registration helper Moteen Shah
2026-11-12 8:10 ` [PATCH v3 4/4] soc: ti: Add TDA54 SCM configuration syscon support Moteen Shah
2026-11-12 16:16 ` kernel test robot
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=20261112081047.1550471-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
all inboxes | Powered by JetHome®