mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Padhi, Beleswar" <b-padhi@ti.com>
To: Krzysztof Kozlowski <krzk@kernel.org>
Cc: <nm@ti.com>, <kristo@kernel.org>, <ssantosh@kernel.org>,
	<linux-arm-kernel@lists.infradead.org>,
	<linux-kernel@vger.kernel.org>, <afd@ti.com>, <u-kumar1@ti.com>,
	<vigneshr@ti.com>, Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH 2/6] dt-bindings: arm: keystone: ti,sci: Add ti,tda54-sci-pdm compatible
Date: Fri, 2 Oct 2026 16:00:46 +0530	[thread overview]
Message-ID: <33bea116-676c-423f-a225-80762d45c719@ti.com> (raw)
In-Reply-To: <7a66abc8-3b9a-4a9d-a094-e47e3588091a@kernel.org>


On 10/2/2026 3:09 PM, Krzysztof Kozlowski wrote:
> On 02/10/2026 11:30, Padhi, Beleswar wrote:
>> On 10/2/2026 12:01 PM, Krzysztof Kozlowski wrote:
>>> On Thu, Oct 01, 2026 at 01:11:27AM +0530, Beleswar Padhi wrote:
>>>> 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 Deadlock 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.
>>> I don't get at all how above description helps to understand this patch
>>> and this new compatible, except that this is not compatible with old
>>> variants.
>>
>> You just answered your own question.
>>
>>>    So 30 lines of text instead of 3?
>>
>> The existing system controllers have been compatible in all TI SoCs
>> for over 10+ years since Keystone generations. Using 30 lines of
>> text to explain "why" the new system controller is not compatible
>> with old variants is worth it.
> If you decide to spam us with a lot of description, including marketing
> crap ("To realize this enhanced isolation in hardware", "this improved
> isolation")


I am a Open Source Developer at TI. Marketing about TI Product/Hardware
is of no interest to me, neither is my intent. I was just describing why
& how the hardware has changed. If it gives the impression of
marketing, then sure, I will drop the "crap" to not waste your time.

Thanks,
Beleswar

>   instead of writing concise and precise messages, accept the
> outcome of maintainers choosing to allocate their time in "improved way".
>
> Best regards,
> Krzysztof

  reply	other threads:[~2026-10-02 10:31 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-09-30 19:41 [PATCH 0/6] Enhance TI-SCI FFI with ABI5.0 support Beleswar Padhi
2026-09-30 19:41 ` [PATCH 1/6] dt-bindings: arm: keystone: ti,sci: Update nodename pattern Beleswar Padhi
2026-10-02  6:27   ` Krzysztof Kozlowski
2026-10-02  9:56     ` Padhi, Beleswar
2026-10-02 10:00       ` Krzysztof Kozlowski
2026-09-30 19:41 ` [PATCH 2/6] dt-bindings: arm: keystone: ti,sci: Add ti,tda54-sci-pdm compatible Beleswar Padhi
2026-10-02  6:31   ` Krzysztof Kozlowski
2026-10-02  9:30     ` Padhi, Beleswar
2026-10-02  9:39       ` Krzysztof Kozlowski
2026-10-02 10:30         ` Padhi, Beleswar [this message]
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=33bea116-676c-423f-a225-80762d45c719@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=krzk@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®