From: Jon Hunter <jonathanh@nvidia.com>
To: Akhil R <akhilrajeev@nvidia.com>, Vinod Koul <vkoul@kernel.org>,
Frank Li <Frank.Li@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Philipp Zabel <p.zabel@pengutronix.de>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 9/9] arm64: tegra: Enable GPCDMA and add iommu-map in Tegra264
Date: Tue, 24 Mar 2026 10:46:33 +0000 [thread overview]
Message-ID: <9d203e60-6aed-476b-b0f2-36adf7f8dc7c@nvidia.com> (raw)
In-Reply-To: <20260316171823.61800-10-akhilrajeev@nvidia.com>
On 16/03/2026 17:18, Akhil R wrote:
> Remove the fallback compatible string "nvidia,tegra186-gpcdma" and
> enable GPCDMA in Tegra264. Tegra186 compatible cannot work on
> Tegra264 because of the register offset changes and absence of
> the reset property.
>
> Also add the iommu-map property so that each channel uses a separate
> stream ID and gets its own IOMMU domain for memory.
>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> ---
> arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi | 4 ++++
> arch/arm64/boot/dts/nvidia/tegra264.dtsi | 3 ++-
> 2 files changed, 6 insertions(+), 1 deletion(-)
>
> diff --git a/arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi b/arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi
> index 7e2c3e66c2ab..c8beb616964a 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra264-p3834.dtsi
> @@ -16,6 +16,10 @@ serial@c4e0000 {
> serial@c5a0000 {
> status = "okay";
> };
> +
> + dma-controller@8400000 {
> + status = "okay";
> + };
> };
We need to fix the ordering here, because we order these according to
the address. Thierry may be able to fix this when applying.
>
> bus@8100000000 {
> diff --git a/arch/arm64/boot/dts/nvidia/tegra264.dtsi b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
> index 24cc2c51a272..b2f20d4b567a 100644
> --- a/arch/arm64/boot/dts/nvidia/tegra264.dtsi
> +++ b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
> @@ -3208,7 +3208,7 @@ agic_page5: interrupt-controller@99b0000 {
> };
>
> gpcdma: dma-controller@8400000 {
> - compatible = "nvidia,tegra264-gpcdma", "nvidia,tegra186-gpcdma";
> + compatible = "nvidia,tegra264-gpcdma";
Ideally this would be a separate patch with the appropriate fixes tag,
however, there is a dependency on patch 2/9. Really patch 2/9 should be
the first patch in the series as this is a fix and preparing for
enabling Tegra264 support. And this part should probably be patch 2/9.
Then this patch that enables this, the final one in the series.
> reg = <0x0 0x08400000 0x0 0x210000>;
> interrupts = <GIC_SPI 584 IRQ_TYPE_LEVEL_HIGH>,
> <GIC_SPI 585 IRQ_TYPE_LEVEL_HIGH>,
> @@ -3244,6 +3244,7 @@ gpcdma: dma-controller@8400000 {
> <GIC_SPI 615 IRQ_TYPE_LEVEL_HIGH>;
> #dma-cells = <1>;
> iommus = <&smmu1 0x00000800>;
> + iommu-map = <1 &smmu1 0x801 31>;
> dma-coherent;
> dma-channel-mask = <0xfffffffe>;
> status = "disabled";
--
nvpublic
prev parent reply other threads:[~2026-03-24 10:46 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-16 17:18 [PATCH v3 0/9] Add GPCDMA support in Tegra264 Akhil R
2026-03-16 17:18 ` [PATCH v3 1/9] dt-bindings: dma: nvidia,tegra186-gpc-dma: Add iommu-map property Akhil R
2026-03-25 16:35 ` Rob Herring (Arm)
2026-03-16 17:18 ` [PATCH v3 2/9] dt-bindings: dma: nvidia,tegra186-gpc-dma: Make reset optional Akhil R
2026-03-24 10:47 ` Jon Hunter
2026-03-25 16:37 ` Rob Herring (Arm)
2026-03-16 17:18 ` [PATCH v3 3/9] dmaengine: tegra: Make reset control optional Akhil R
2026-03-16 17:18 ` [PATCH v3 4/9] dmaengine: tegra: Use struct for register offsets Akhil R
2026-03-16 17:18 ` [PATCH v3 5/9] dmaengine: tegra: Support address width > 39 bits Akhil R
2026-03-16 17:18 ` [PATCH v3 6/9] dmaengine: tegra: Use managed DMA controller registration Akhil R
2026-03-16 17:18 ` [PATCH v3 7/9] dmaengine: tegra: Use iommu-map for stream ID Akhil R
2026-03-16 17:18 ` [PATCH v3 8/9] dmaengine: tegra: Add Tegra264 support Akhil R
2026-03-16 17:18 ` [PATCH v3 9/9] arm64: tegra: Enable GPCDMA and add iommu-map in Tegra264 Akhil R
2026-03-24 10:46 ` Jon Hunter [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=9d203e60-6aed-476b-b0f2-36adf7f8dc7c@nvidia.com \
--to=jonathanh@nvidia.com \
--cc=Frank.Li@kernel.org \
--cc=akhilrajeev@nvidia.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@kernel.org \
--cc=thierry.reding@kernel.org \
--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