From: "Kumar, Udit" <u-kumar1@ti.com>
To: Apurva Nandan <a-nandan@ti.com>, Nishanth Menon <nm@ti.com>,
Vignesh Raghavendra <vigneshr@ti.com>,
Tero Kristo <kristo@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
<linux-arm-kernel@lists.infradead.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>,
Hari Nagalla <hnagalla@ti.com>
Subject: Re: [PATCH v4 8/9] arm64: dts : ti: k3-am69-sk: Add DDR carveout memory nodes for R5F
Date: Wed, 27 Sep 2023 20:52:42 +0530 [thread overview]
Message-ID: <d96b0ac6-b216-3025-23f7-28c93b84b98f@ti.com> (raw)
In-Reply-To: <20230906112422.2846151-9-a-nandan@ti.com>
On 9/6/2023 4:54 PM, Apurva Nandan wrote:
> Two carveout reserved memory nodes each have been added for each of the
> R5F remote processor device within both the MCU and MAIN domains for the
> TI K3 AM69 SK boards. These nodes are assigned to the respective rproc
> device nodes as well. The first region will be used as the DMA pool for
> the rproc device, and the second region will furnish the static carveout
> regions for the firmware memory.
>
> The current carveout addresses and sizes are defined statically for each
> device. The R5F processors do not have an MMU, and as such require the
> exact memory used by the firmwares to be set-aside. The firmware images
> do not require any RSC_CARVEOUT entries in their resource tables either
> to allocate the memory for firmware memory segments.
>
> Note that the R5F1 carveouts are needed only if the R5F cluster is
> running in Split (non-LockStep) mode. The reserved memory nodes can be
> disabled later on if there is no use-case defined to use the corresponding
> remote processor.
>
> Signed-off-by: Sinthu Raja <sinthu.raja@ti.com>
> Signed-off-by: Apurva Nandan <a-nandan@ti.com>
> ---
> arch/arm64/boot/dts/ti/k3-am69-sk.dts | 200 ++++++++++++++++++++++++++
> 1 file changed, 200 insertions(+)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-am69-sk.dts b/arch/arm64/boot/dts/ti/k3-am69-sk.dts
> index d282c2c633c1..d5a39caf15af 100644
> --- a/arch/arm64/boot/dts/ti/k3-am69-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-am69-sk.dts
> @@ -47,6 +47,102 @@ secure_ddr: optee@9e800000 {
> reg = <0x00 0x9e800000 0x00 0x01800000>;
> no-map;
> };
Reviewed by: Udit Kumar<u-kumar1@ti.com>
> [...]
next prev parent reply other threads:[~2023-09-27 15:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-06 11:24 [PATCH v4 0/9] Add R5F and C7x DSP node for K3 J721S2, AM68 and AM69 SoCs Apurva Nandan
2023-09-06 11:24 ` [PATCH v4 1/9] arm64: dts: ti: k3-j721s2-mcu: Add MCU R5F cluster nodes Apurva Nandan
2023-09-06 11:24 ` [PATCH v4 2/9] arm64: dts: ti: k3-j721s2-main: Add MAIN R5F remote processsor nodes Apurva Nandan
2023-09-06 11:24 ` [PATCH v4 3/9] arm64: dts: ti: k3-j721s2-main: Add C7x " Apurva Nandan
2023-09-06 11:24 ` [PATCH v4 4/9] arm64: dts : ti: k3-j721s2-som-p0: Add DDR carveout memory nodes for R5F Apurva Nandan
2023-09-06 11:24 ` [PATCH v4 5/9] arm64: dts : ti: k3-j721s2-som-p0: Add DDR carveout memory nodes for C71x DSPs Apurva Nandan
2023-09-06 11:24 ` [PATCH v4 6/9] arm64: dts : ti: k3-am68-sk-som: Add DDR carveout memory nodes for R5F Apurva Nandan
2023-09-27 15:21 ` Kumar, Udit
2023-09-06 11:24 ` [PATCH v4 7/9] arm64: dts : ti: k3-am68-sk-som: Add DDR carveout memory nodes for C71x DSP Apurva Nandan
2023-09-27 15:22 ` Kumar, Udit
2023-09-06 11:24 ` [PATCH v4 8/9] arm64: dts : ti: k3-am69-sk: Add DDR carveout memory nodes for R5F Apurva Nandan
2023-09-27 15:22 ` Kumar, Udit [this message]
2023-09-06 11:24 ` [PATCH v4 9/9] arm64: dts : ti: k3-am69-sk: Add DDR carveout memory nodes for C71x DSP Apurva Nandan
2023-09-27 15:23 ` Kumar, Udit
2023-09-27 8:54 ` [PATCH v4 0/9] Add R5F and C7x DSP node for K3 J721S2, AM68 and AM69 SoCs Kumar, Udit
2023-09-27 12:28 ` Nishanth Menon
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=d96b0ac6-b216-3025-23f7-28c93b84b98f@ti.com \
--to=u-kumar1@ti.com \
--cc=a-nandan@ti.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=kristo@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).