From: Beleswar Padhi <b-padhi@ti.com>
To: <andersson@kernel.org>, <mathieu.poirier@linaro.org>,
<robh@kernel.org>, <krzk+dt@kernel.org>, <conor+dt@kernel.org>,
<nm@ti.com>, <vigneshr@ti.com>, <kristo@kernel.org>
Cc: <afd@ti.com>, <u-kumar1@ti.com>, <hnagalla@ti.com>,
<b-padhi@ti.com>, <linux-remoteproc@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: [PATCH 0/3] Add TI K3 HSM M4F nodes in device-tree
Date: Wed, 31 Dec 2025 22:20:59 +0530 [thread overview]
Message-ID: <20251231165102.950644-1-b-padhi@ti.com> (raw)
Some of the TI K3 family of SoCs (like J721S2, J784S4, J722S) have a
HSM (High Security Module) M4F core in the Wakeup Voltage Domain which
could be used to run secure services like Authentication. Add the device
tree bindings and device-tree node definitions for this HSM M4F core.
The HSM M4 core is typically booted early from the bootloader and the
driver for the same will be posted shortly.
Beleswar Padhi (3):
dt-bindings: remoteproc: Add bindings for HSM core on TI K3 SoCs
arm64: dts: ti: k3-{j784s4-j742s2/j721s2}-mcu-wakeup: Add HSM M4F node
arm64: dts: ti: k3-am62p-j722s-common-main: Add HSM M4F node
.../bindings/remoteproc/ti,k3-hsm-rproc.yaml | 79 +++++++++++++++++++
.../dts/ti/k3-am62p-j722s-common-main.dtsi | 15 ++++
arch/arm64/boot/dts/ti/k3-am62p.dtsi | 1 +
.../boot/dts/ti/k3-j721s2-mcu-wakeup.dtsi | 15 ++++
arch/arm64/boot/dts/ti/k3-j722s.dtsi | 1 +
.../k3-j784s4-j742s2-mcu-wakeup-common.dtsi | 15 ++++
6 files changed, 126 insertions(+)
create mode 100644 Documentation/devicetree/bindings/remoteproc/ti,k3-hsm-rproc.yaml
--
2.34.1
next reply other threads:[~2025-12-31 16:51 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-31 16:50 Beleswar Padhi [this message]
2025-12-31 16:51 ` [PATCH 1/3] dt-bindings: remoteproc: Add bindings for HSM core on TI K3 SoCs Beleswar Padhi
2026-01-02 12:30 ` Krzysztof Kozlowski
2026-01-05 5:56 ` Padhi, Beleswar
2026-01-05 7:10 ` Krzysztof Kozlowski
2026-01-05 7:28 ` Padhi, Beleswar
2025-12-31 16:51 ` [PATCH 2/3] arm64: dts: ti: k3-{j784s4-j742s2/j721s2}-mcu-wakeup: Add HSM M4F node Beleswar Padhi
2025-12-31 16:51 ` [PATCH 3/3] arm64: dts: ti: k3-am62p-j722s-common-main: " Beleswar Padhi
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=20251231165102.950644-1-b-padhi@ti.com \
--to=b-padhi@ti.com \
--cc=afd@ti.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-remoteproc@vger.kernel.org \
--cc=mathieu.poirier@linaro.org \
--cc=nm@ti.com \
--cc=robh@kernel.org \
--cc=u-kumar1@ti.com \
--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
all inboxes | Powered by JetHome®