From: Beleswar Padhi <b-padhi@ti.com>
To: <nm@ti.com>, <kristo@kernel.org>, <ssantosh@kernel.org>
Cc: <linux-arm-kernel@lists.infradead.org>,
<linux-kernel@vger.kernel.org>, <afd@ti.com>, <u-kumar1@ti.com>,
<vigneshr@ti.com>, <b-padhi@ti.com>,
"Rob Herring" <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
"Conor Dooley" <conor+dt@kernel.org>,
<devicetree@vger.kernel.org>
Subject: [PATCH 0/6] Enhance TI-SCI FFI with ABI5.0 support
Date: Thu, 1 Oct 2026 01:11:25 +0530 [thread overview]
Message-ID: <20260930194131.117129-1-b-padhi@ti.com> (raw)
The previous TI K2G and K3 architectures were tightly coupled systems in
terms of Safety and Security. All the TI-SCI messages from HLOS (Linux)
were sent to a single sec proxy thread terminating at the core running
Safety service (DM). In K2G systems, DM handled both Safety & Security
requests by itself. Whereas in K3 systems, DM serviced the Safety
requests itself, and forwarded the Security requests to core running
Security service (TIFS) on the HLOS's behalf. This posed various
limitations:
a. Increased latency: An extra forwarding hop through DM adds latency
in requests and responses.
b. Freedom From Interference (FFI) concerns: Having Safety service
proxy Security's requests (& vice versa) undermines the isolation
and FFI of the system.
c. Potential Dealock Scenario: Forwarding messages between Safety and
Security cores can result in a deadlock if there are circular
dependencies.
To eliminate all the above limitations, the TI TDA54 class of SoCs
introduce an architectural change: Isolation of Security and Safety
services. To realize this enhanced isolation in hardware, two
independent sec proxy threads are now provided for HLOS to communicate
separately with the Security and Safety cores respectively. And the
TI-SCI message forwarding has been eliminated in Software. The System
Firmware ABI5.0 version necessitates this improved isolation and FFI
change.
This series adds the support for TI TDA54 PDM System Controller across
Devicetree bindings and TI-SCI Driver to support the ABI 5.0 change.
Note:
a. The first half of the series i.e, patches
[PATCH 01/06] - [PATCH 02/06] are independent and can be applied
directly.
b. The second half of the series i.e, patches
[PATCH 03/06] - [PATCH 06/06] is dependent on the following 2 series
1. https://lore.kernel.org/all/20260930172948.2901336-1-b-padhi@ti.com/
2. https://lore.kernel.org/all/20260930160607.2674980-1-b-padhi@ti.com/
Testing done:
- Build and Boot tested on all Keystone and K3 platforms.
- Verified ABI5.0 core and device operations on TI TDA54 platform.
(after applying an out-of-tree patch to add DTS support)
- Verified that none of the patches in the series generate any warnings
or errors.
Logs:
https://gist.github.com/3V3RYONE/d821cea46f5dc1e70a759c97878fa487
Cc: Nishanth Menon <nm@ti.com>
Cc: Tero Kristo <kristo@kernel.org>
Cc: Santosh Shilimkar <ssantosh@kernel.org>
Cc: Rob Herring <robh@kernel.org>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>
Cc: Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org
Cc: devicetree@vger.kernel.org
Cc: linux-kernel@vger.kernel.org
Beleswar Padhi (6):
dt-bindings: arm: keystone: ti,sci: Update nodename pattern
dt-bindings: arm: keystone: ti,sci: Add ti,tda54-sci-pdm compatible
firmware: ti: ti_sci_core: Add ABI5.0 Enhancements and TDA54 PDM SCI
support
firmware: ti: ti_sci_device: Add ABI5.0 compliant Device and Reset
APIs
firmware: ti: ti_sci_clock: Add ABI5.0 compliant Clock APIs
firmware: ti: ti_sci_rm: Add ABI5.0 compliant basic RM APIs
.../bindings/arm/keystone/ti,sci.yaml | 48 ++-
drivers/firmware/ti/ti_sci.h | 233 +++++++++++
drivers/firmware/ti/ti_sci_clock.c | 380 ++++++++++++++++++
drivers/firmware/ti/ti_sci_core.c | 204 ++++++++--
drivers/firmware/ti/ti_sci_device.c | 62 +++
drivers/firmware/ti/ti_sci_rm.c | 148 +++++++
6 files changed, 1039 insertions(+), 36 deletions(-)
--
2.34.1
next reply other threads:[~2026-09-30 19:42 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-09-30 19:41 Beleswar Padhi [this message]
2026-09-30 19:41 ` [PATCH 1/6] dt-bindings: arm: keystone: ti,sci: Update nodename pattern Beleswar Padhi
2026-09-30 19:41 ` [PATCH 2/6] dt-bindings: arm: keystone: ti,sci: Add ti,tda54-sci-pdm compatible Beleswar Padhi
2026-09-30 19:41 ` [PATCH 3/6] firmware: ti: ti_sci_core: Add ABI5.0 Enhancements and TDA54 PDM SCI support Beleswar Padhi
2026-09-30 19:41 ` [PATCH 4/6] firmware: ti: ti_sci_device: Add ABI5.0 compliant Device and Reset APIs Beleswar Padhi
2026-09-30 19:41 ` [PATCH 5/6] firmware: ti: ti_sci_clock: Add ABI5.0 compliant Clock APIs Beleswar Padhi
2026-09-30 19:41 ` [PATCH 6/6] firmware: ti: ti_sci_rm: Add ABI5.0 compliant basic RM APIs 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=20260930194131.117129-1-b-padhi@ti.com \
--to=b-padhi@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=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®