From: Andrew Davis <afd@ti.com>
To: Beleswar Padhi <b-padhi@ti.com>, <nm@ti.com>, <vigneshr@ti.com>,
<kristo@kernel.org>, <robh@kernel.org>, <krzk+dt@kernel.org>,
<conor+dt@kernel.org>
Cc: <u-kumar1@ti.com>, <hnagalla@ti.com>, <jm@ti.com>,
<d-gole@ti.com>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH v4 21/34] Revert "arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations"
Date: Wed, 10 Sep 2025 09:07:31 -0500 [thread overview]
Message-ID: <4c9750c3-ba75-46ec-8398-0691d385d0d2@ti.com> (raw)
In-Reply-To: <20250908142826.1828676-22-b-padhi@ti.com>
On 9/8/25 9:28 AM, Beleswar Padhi wrote:
> This reverts commit 9f3814a7c06b7c7296cf8c1622078ad71820454b.
>
> The C6x carveouts are reversed intentionally. This is due to the
> requirement to keep the DMA memory region as non-cached, however the
> minimum granular cache region for C6x is 16MB. So, C66x_0 marks the
> entire C66x_1 16MB memory carveouts as non-cached, and uses the DMA
> memory region of C66x_1 as its own, and vice-versa.
>
> This was also called out in the original commit which introduced these
> reversed carveouts:
> "The minimum granularity on the Cache settings on C66x DSP cores
> is 16MB, so the DMA memory regions are chosen such that they are
> in separate 16MB regions for each DSP, while reserving a total
> of 16 MB for each DSP and not changing the overall DSP
> remoteproc carveouts."
>
> Fixes: 9f3814a7c06b ("arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations")
> Signed-off-by: Beleswar Padhi <b-padhi@ti.com>
> ---
Still feels like something we should have fixed on the firmware side,
but since the firmware is out there already we can live with it.
Acked-by: Andrew Davis <afd@ti.com>
> v4: Changelog:
> 1. Updated carveout node names to generic 'memory@addr'
>
> Link to v3:
> https://lore.kernel.org/all/20250905051846.1189612-21-b-padhi@ti.com/
>
> v3: Changelog:
> 1. None
>
> Link to v2:
> https://lore.kernel.org/all/20250823160901.2177841-21-b-padhi@ti.com/
>
> v2: Changelog:
> 1. Re-ordered patch from [PATCH 03/33] to [PATCH v2 20/33].
>
> Link to v1:
> https://lore.kernel.org/all/20250814223839.3256046-4-b-padhi@ti.com/
> arch/arm64/boot/dts/ti/k3-j721e-sk.dts | 6 ++++--
> 1 file changed, 4 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/ti/k3-j721e-sk.dts b/arch/arm64/boot/dts/ti/k3-j721e-sk.dts
> index 0f05e65f7bf7..37bc33f2cc26 100644
> --- a/arch/arm64/boot/dts/ti/k3-j721e-sk.dts
> +++ b/arch/arm64/boot/dts/ti/k3-j721e-sk.dts
> @@ -120,7 +120,8 @@ main_r5fss1_core1_memory_region: memory@a5100000 {
> no-map;
> };
>
> - c66_0_dma_memory_region: memory@a6000000 {
> + /* Carveout locations are flipped due to caching */
> + c66_1_dma_memory_region: memory@a6000000 {
> compatible = "shared-dma-pool";
> reg = <0x00 0xa6000000 0x00 0x100000>;
> no-map;
> @@ -132,7 +133,8 @@ c66_0_memory_region: memory@a6100000 {
> no-map;
> };
>
> - c66_1_dma_memory_region: memory@a7000000 {
> + /* Carveout locations are flipped due to caching */
> + c66_0_dma_memory_region: memory@a7000000 {
> compatible = "shared-dma-pool";
> reg = <0x00 0xa7000000 0x00 0x100000>;
> no-map;
next prev parent reply other threads:[~2025-09-10 14:07 UTC|newest]
Thread overview: 41+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-08 14:27 [PATCH v4 00/34] Refactor TI IPC DT configs into dtsi Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 01/34] arm64: dts: ti: k3-j7200: Enable R5F remote processors at board level Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 02/34] arm64: dts: ti: k3-j721e: Enable " Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 03/34] arm64: dts: ti: k3-j721s2: " Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 04/34] arm64: dts: ti: k3-j784s4-j742s2: " Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 05/34] arm64: dts: ti: k3-am62p-j722s: " Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 06/34] arm64: dts: ti: k3-am62: " Beleswar Padhi
2025-09-08 14:27 ` [PATCH v4 07/34] arm64: dts: ti: k3-am62a: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 08/34] arm64: dts: ti: k3-am64: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 09/34] arm64: dts: ti: k3-am65: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 10/34] arm64: dts: ti: k3-am62: Enable Mailbox nodes at the " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 11/34] arm64: dts: ti: k3-am62a: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 12/34] arm64: dts: ti: k3-am6*-boards: Add label to reserved-memory node Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 13/34] arm64: dts: ti: k3: Rename rproc reserved-mem nodes to 'memory@addr' Beleswar Padhi
2025-09-08 19:23 ` Francesco Dolcini
2025-09-08 14:28 ` [PATCH v4 14/34] arm64: dts: ti: k3-j721e-beagleboneai64: Add missing cfg for TI IPC FW Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 15/34] arm64: dts: ti: k3-am62p-verdin: Add missing cfg for TI IPC Firmware Beleswar Padhi
2025-09-08 19:20 ` Francesco Dolcini
2025-09-08 14:28 ` [PATCH v4 16/34] arm64: dts: ti: k3-am62-verdin: " Beleswar Padhi
2025-09-08 19:21 ` Francesco Dolcini
2025-09-08 14:28 ` [PATCH v4 17/34] arm64: dts: ti: k3-am62-pocketbeagle2: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 18/34] arm64: dts: ti: k3-am642-sr-som: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 19/34] arm64: dts: ti: k3-am64-phycore-som: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 20/34] arm64: dts: ti: k3-am642-tqma64xxl: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 21/34] Revert "arm64: dts: ti: k3-j721e-sk: Fix reversed C6x carveout locations" Beleswar Padhi
2025-09-10 14:07 ` Andrew Davis [this message]
2025-09-08 14:28 ` [PATCH v4 22/34] Revert "arm64: dts: ti: k3-j721e-beagleboneai64: " Beleswar Padhi
2025-09-10 14:07 ` Andrew Davis
2025-09-08 14:28 ` [PATCH v4 23/34] arm64: dts: ti: k3-j721e-beagleboneai64: Switch MAIN R5F clusters to Split-mode Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 24/34] arm64: dts: ti: k3-j7200-ti-ipc-firmware: Refactor IPC cfg into new dtsi Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 25/34] arm64: dts: ti: k3-j721e-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 26/34] arm64: dts: ti: k3-j721s2-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 27/34] arm64: dts: ti: k3-j784s4-j742s2-ti-ipc-firmware-common: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 28/34] arm64: dts: ti: k3-j784s4-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 29/34] arm64: dts: ti: k3-j722s-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 30/34] arm64: dts: ti: k3-am62p-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 31/34] arm64: dts: ti: k3-am62-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 32/34] arm64: dts: ti: k3-am62a-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 33/34] arm64: dts: ti: k3-am64-ti-ipc-firmware: " Beleswar Padhi
2025-09-08 14:28 ` [PATCH v4 34/34] arm64: dts: ti: k3-am65-ti-ipc-firmware: " Beleswar Padhi
2025-09-12 9:49 ` [PATCH v4 00/34] Refactor TI IPC DT configs into dtsi 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=4c9750c3-ba75-46ec-8398-0691d385d0d2@ti.com \
--to=afd@ti.com \
--cc=b-padhi@ti.com \
--cc=conor+dt@kernel.org \
--cc=d-gole@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=hnagalla@ti.com \
--cc=jm@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=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