devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Péter Ujfalusi" <peter.ujfalusi@gmail.com>
To: Vignesh Raghavendra <vigneshr@ti.com>,
	Vinod Koul <vkoul@kernel.org>, Rob Herring <robh+dt@kernel.org>,
	Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/3] dt-bindings: dma: ti: k3* : Update optional reg regions
Date: Sun, 27 Aug 2023 10:18:56 +0300	[thread overview]
Message-ID: <00bf501f-6829-4be3-bf1d-40ae8495d970@gmail.com> (raw)
In-Reply-To: <1d2ab22e-9bbc-f876-f059-980f543551d4@ti.com>

Hi Vignesh,

On 11/08/2023 19:04, Vignesh Raghavendra wrote:
> 
> There is been a relook at the arch post this driver was upstreamed. 
> System firmware (SYSFW) is now two separate components:  TI Foundational 
> Security (TIFS) running in a secure island and Device Management (DM) 
> firmware (runs on boot R5 core) [0] shows boot flow diagram for AM62x.

I see, I cannot argue with that.
Is this change affecting the entire K3 family or only the new members?
If the later then I would seek for conditionality for the new regions as
non relooked SoCs these regions are off-limit for the SW.

> Security critical items such as PSIL pairing, channel firewalls and 
> credential configurations are under TIFS and is handled via TI SCI calls 
> at all times.
> 
> But, things related to resource configuration (to ensure different cores 
> dont step on each other) is under DM. Linux still needs to talk to DM 
> for configuring these regions. But, when primary bootloader (R5 SPL) is 
> running, there isn't a DM firmware (as it runs on the same core after R5 
> SPL), it would need to configure DMA resources on its own. 
> 
> This update is mainly to aid R5 SPL to reuse kernel DT as is. 
> Hope that helps

Right, so Linux will need to use these soon ;)

> 
> 
> [0] https://u-boot.readthedocs.io/en/latest/board/ti/am62x_sk.html?highlight=am62#boot-flow
> (Similar boot flow for rest of K3 devices barring am65 and am64)

OK, if the R5 needs to use DMA before DM then surely there is a need to
configure the channel(s).
I expect that R5 or DM will reset things back before booting the main CPU.

> 
>>
>>>
>>> Vignesh Raghavendra (3):
>>>    dt-bindings: dma: ti: k3-bcdma: Describe cfg register regions
>>>    dt-bindings: dma: ti: k3-pktdma: Describe cfg register regions
>>>    dt-bindings: dma: ti: k3-udma: Describe cfg register regions
>>>
>>>   .../devicetree/bindings/dma/ti/k3-bcdma.yaml  | 25 +++++++++++++------
>>>   .../devicetree/bindings/dma/ti/k3-pktdma.yaml | 18 ++++++++++---
>>>   .../devicetree/bindings/dma/ti/k3-udma.yaml   | 14 ++++++++---
>>>   3 files changed, 43 insertions(+), 14 deletions(-)
>>>
>>
> 

-- 
Péter

      reply	other threads:[~2023-08-27  7:20 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-08-10 17:43 [PATCH 0/3] dt-bindings: dma: ti: k3* : Update optional reg regions Vignesh Raghavendra
2023-08-10 17:43 ` [PATCH 1/3] dt-bindings: dma: ti: k3-bcdma: Describe cfg register regions Vignesh Raghavendra
2023-08-10 18:35   ` Conor Dooley
2023-08-11  4:38     ` Vignesh Raghavendra
2023-08-27  7:06   ` Péter Ujfalusi
2023-08-10 17:43 ` [PATCH 2/3] dt-bindings: dma: ti: k3-pktdma: " Vignesh Raghavendra
2023-08-27  7:10   ` Péter Ujfalusi
2023-08-10 17:43 ` [PATCH 3/3] dt-bindings: dma: ti: k3-udma: " Vignesh Raghavendra
2023-08-11 15:16 ` [PATCH 0/3] dt-bindings: dma: ti: k3* : Update optional reg regions Péter Ujfalusi
2023-08-11 16:04   ` Vignesh Raghavendra
2023-08-27  7:18     ` Péter Ujfalusi [this message]

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=00bf501f-6829-4be3-bf1d-40ae8495d970@gmail.com \
    --to=peter.ujfalusi@gmail.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=krzysztof.kozlowski+dt@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh+dt@kernel.org \
    --cc=vigneshr@ti.com \
    --cc=vkoul@kernel.org \
    /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;
as well as URLs for NNTP newsgroup(s).