public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Akhil R <akhilrajeev@nvidia.com>
To: <frank.li@nxp.com>
Cc: <Frank.Li@kernel.org>, <akhilrajeev@nvidia.com>,
	<conor+dt@kernel.org>, <devicetree@vger.kernel.org>,
	<dmaengine@vger.kernel.org>, <jonathanh@nvidia.com>,
	<krzk+dt@kernel.org>, <linux-kernel@vger.kernel.org>,
	<linux-tegra@vger.kernel.org>, <p.zabel@pengutronix.de>,
	<robh@kernel.org>, <thierry.reding@gmail.com>, <vkoul@kernel.org>
Subject: Re: [PATCH 8/8] arm64: tegra: Add iommu-map and enable GPCDMA in Tegra264
Date: Tue, 24 Feb 2026 12:25:30 +0530	[thread overview]
Message-ID: <20260224065530.50701-1-akhilrajeev@nvidia.com> (raw)
In-Reply-To: <aZStTjL8EoZC4TtE@lizhi-Precision-Tower-5810>

On Tue, 17 Feb 2026 13:02:54 -0500, Frank Li wrote:
> On Tue, Feb 17, 2026 at 11:04:57PM +0530, Akhil R wrote:
>> Add iommu-map and remove iommus in the GPCDMA controller node so
>> that each channel uses separate stream ID and gets its own IOMMU
>> domain for memory. Also enable GPCDMA for Tegra264.
>>
>> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
>> ---
>>  .../arm64/boot/dts/nvidia/tegra264-p3834.dtsi |  4 +++
>>  arch/arm64/boot/dts/nvidia/tegra264.dtsi      | 33 ++++++++++++++++++-
>>  2 files changed, 36 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";
>> +		};
>>  	};
>>
>>  	bus@8100000000 {
>> diff --git a/arch/arm64/boot/dts/nvidia/tegra264.dtsi b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
>> index 7644a41d5f72..0317418c95d3 100644
>> --- a/arch/arm64/boot/dts/nvidia/tegra264.dtsi
>> +++ b/arch/arm64/boot/dts/nvidia/tegra264.dtsi
>> @@ -3243,7 +3243,38 @@ gpcdma: dma-controller@8400000 {
>> 				     <GIC_SPI 614 IRQ_TYPE_LEVEL_HIGH>,
>> 				     <GIC_SPI 615 IRQ_TYPE_LEVEL_HIGH>;
>> 			#dma-cells = <1>;
>> -			iommus = <&smmu1 0x00000800>;
>> +			iommu-map =
>> +				<1  &smmu1 0x801 1>,
>> +				<2  &smmu1 0x802 1>,
>> +				<3  &smmu1 0x803 1>,
>> +				<4  &smmu1 0x804 1>,
>> +				<5  &smmu1 0x805 1>,
>> +				<6  &smmu1 0x806 1>,
>> +				<7  &smmu1 0x807 1>,
>> +				<8  &smmu1 0x808 1>,
>> +				<9  &smmu1 0x809 1>,
>> +				<10 &smmu1 0x80a 1>,
>> +				<11 &smmu1 0x80b 1>,
>> +				<12 &smmu1 0x80c 1>,
>> +				<13 &smmu1 0x80d 1>,
>> +				<14 &smmu1 0x80e 1>,
>> +				<15 &smmu1 0x80f 1>,
>> +				<16 &smmu1 0x810 1>,
>> +				<17 &smmu1 0x811 1>,
>> +				<18 &smmu1 0x812 1>,
>> +				<19 &smmu1 0x813 1>,
>> +				<20 &smmu1 0x814 1>,
>> +				<21 &smmu1 0x815 1>,
>> +				<22 &smmu1 0x816 1>,
>> +				<23 &smmu1 0x817 1>,
>> +				<24 &smmu1 0x818 1>,
>> +				<25 &smmu1 0x819 1>,
>> +				<26 &smmu1 0x81a 1>,
>> +				<27 &smmu1 0x81b 1>,
>> +				<28 &smmu1 0x81c 1>,
>> +				<29 &smmu1 0x81d 1>,
>> +				<30 &smmu1 0x81e 1>,
>> +				<31 &smmu1 0x81f 1>;
> 
> It is linear increase
> <1 &smmu1 0x801 31>;

Ack. I will update.

> 
> Frank
> 
>>  			dma-coherent;
>>  			dma-channel-mask = <0xfffffffe>;
>>  			status = "disabled";
>> --

Regards,
Akhil

      reply	other threads:[~2026-02-24  6:55 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-17 17:34 [PATCH 0/8] Add GPCDMA support in Tegra264 Akhil R
2026-02-17 17:34 ` [PATCH 1/8] dt-bindings: dma: nvidia,tegra186-gpc-dma: Add iommu-map property Akhil R
2026-02-17 18:38   ` Rob Herring (Arm)
2026-02-17 19:53   ` Krzysztof Kozlowski
2026-02-18  9:59     ` Jon Hunter
2026-02-18 15:49       ` Rob Herring
2026-02-24  6:41         ` Akhil R
2026-02-17 17:34 ` [PATCH 2/8] dt-bindings: dma: nvidia,tegra186-gpc-dma: Make reset optional Akhil R
2026-02-17 18:38   ` Rob Herring (Arm)
2026-02-17 17:34 ` [PATCH 3/8] dmaengine: tegra: Make reset control optional Akhil R
2026-02-17 18:04   ` Frank Li
2026-02-24  5:39     ` Akhil R
2026-02-24 17:02       ` Jon Hunter
2026-02-25 10:01         ` Akhil R
2026-02-17 17:34 ` [PATCH 4/8] dmaengine: tegra: Use struct for register offsets Akhil R
2026-02-17 18:09   ` Frank Li
2026-02-17 17:34 ` [PATCH 5/8] dmaengine: tegra: Support address width > 40 bits Akhil R
2026-02-17 19:44   ` Frank Li
2026-02-24  6:03     ` Akhil R
2026-02-17 17:34 ` [PATCH 6/8] dmaengine: tegra: Use iommu-map for stream ID Akhil R
2026-02-17 19:52   ` Frank Li
2026-02-24  6:25     ` Akhil R
2026-02-24 21:59       ` Frank Li
2026-02-25 10:27         ` Akhil R
2026-02-25 11:23           ` Jon Hunter
2026-02-26  4:25             ` Akhil R
2026-02-19  8:28   ` Dan Carpenter
2026-02-17 17:34 ` [PATCH 7/8] dmaengine: tegra: Add Tegra264 support Akhil R
2026-02-17 19:53   ` Frank Li
2026-02-17 17:34 ` [PATCH 8/8] arm64: tegra: Add iommu-map and enable GPCDMA in Tegra264 Akhil R
2026-02-17 18:02   ` Frank Li
2026-02-24  6:55     ` Akhil R [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=20260224065530.50701-1-akhilrajeev@nvidia.com \
    --to=akhilrajeev@nvidia.com \
    --cc=Frank.Li@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=dmaengine@vger.kernel.org \
    --cc=frank.li@nxp.com \
    --cc=jonathanh@nvidia.com \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=p.zabel@pengutronix.de \
    --cc=robh@kernel.org \
    --cc=thierry.reding@gmail.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