From: Jon Hunter <jonathanh@nvidia.com>
To: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Thierry Reding <thierry.reding@gmail.com>,
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,
Akhil R <akhilrajeev@nvidia.com>, Frank Li <Frank.Li@kernel.org>
Subject: Re: [PATCH v6 00/10] Add GPCDMA support in Tegra264
Date: Fri, 10 Apr 2026 09:09:38 +0100 [thread overview]
Message-ID: <d548278c-8bbd-4871-8fb6-e22db1688546@nvidia.com> (raw)
In-Reply-To: <586052f6-d415-4603-accb-be15bad80db8@nvidia.com>
Hi Vinod,
On 31/03/2026 19:06, Jon Hunter wrote:
>
> On 31/03/2026 11:22, Akhil R wrote:
>> This series adds support for GPCDMA in Tegra264 with additional
>> support for separate stream ID for each channel. Tegra264 GPCDMA
>> controller has changes in the register offsets and uses 41-bit
>> addressing for memory. Add changes in the tegra186-gpc-dma driver
>> to support these.
>>
>> v5->v6:
>> - Replace dev_err() with dev_err_probe() in the probe function for fixed
>> return values also.
>> v4->v5:
>> - Use dev_err_probe() when returning error from the probe function.
>> - Remove tegra194 and tegra234 compatible from the reset 'if' condition
>> in the bindings as suggested in v2 (which I missed).
>> v3->v4:
>> - Split device tree changes to two patches.
>> - Reordered patches to have fixes first.
>> - Added fixes tag to dt-bindings and device tree changes.
>> v2->v3:
>> - Add description for iommu-map property and update commit descriptions.
>> - Use enum for compatible string instead of const.
>> - Remove unused registers from struct tegra_dma_channel_regs.
>> - Use devm_of_dma_controller_register() to register the DMA controller.
>> - Remove return value check for mask setting in the driver as the bitmask
>> value is always greater than 32.
>> v1->v2:
>> - Fix dt_bindings_check warnings
>> - Drop fallback compatible "nvidia,tegra186-gpcdma" from Tegra264 DT
>> - Use dma_addr_t for sg_req src/dst fields and drop separate high_add
>> variable and check for the addr_bits only when programming the
>> registers.
>> - Update address width to 39 bits for Tegra234 and before since the SMMU
>> supports only up to 39 bits till Tegra234.
>> - Add a patch to do managed DMA controller registration.
>> - Describe the second iteration in the probe.
>> - Update commit descriptions.
>>
>> Akhil R (10):
>> dt-bindings: dma: nvidia,tegra186-gpc-dma: Make reset optional
>> arm64: tegra: Remove fallback compatible for GPCDMA
>> dt-bindings: dma: nvidia,tegra186-gpc-dma: Add iommu-map property
>> dmaengine: tegra: Make reset control optional
>> dmaengine: tegra: Use struct for register offsets
>> dmaengine: tegra: Support address width > 39 bits
>> dmaengine: tegra: Use managed DMA controller registration
>> dmaengine: tegra: Use iommu-map for stream ID
>> dmaengine: tegra: Add Tegra264 support
>> arm64: tegra: Enable GPCDMA in Tegra264 and add iommu-map
>>
>> .../bindings/dma/nvidia,tegra186-gpc-dma.yaml | 32 +-
>> .../arm64/boot/dts/nvidia/tegra264-p3834.dtsi | 4 +
>> arch/arm64/boot/dts/nvidia/tegra264.dtsi | 3 +-
>> drivers/dma/tegra186-gpc-dma.c | 429 +++++++++++-------
>> 4 files changed, 284 insertions(+), 184 deletions(-)
>>
>
> For the series ...
>
> Reviewed-by: Jon Hunter <jonathanh@nvidia.com>
I am not sure if it is too late to pick this up for v7.1, but we would
like to get this into -next if you are happy with it.
Thanks
Jon
--
nvpublic
prev parent reply other threads:[~2026-04-10 8:09 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-03-31 10:22 [PATCH v6 00/10] Add GPCDMA support in Tegra264 Akhil R
2026-03-31 10:22 ` [PATCH v6 01/10] dt-bindings: dma: nvidia,tegra186-gpc-dma: Make reset optional Akhil R
2026-03-31 10:22 ` [PATCH v6 02/10] arm64: tegra: Remove fallback compatible for GPCDMA Akhil R
2026-03-31 10:22 ` [PATCH v6 03/10] dt-bindings: dma: nvidia,tegra186-gpc-dma: Add iommu-map property Akhil R
2026-03-31 10:22 ` [PATCH v6 04/10] dmaengine: tegra: Make reset control optional Akhil R
2026-03-31 10:22 ` [PATCH v6 05/10] dmaengine: tegra: Use struct for register offsets Akhil R
2026-03-31 10:22 ` [PATCH v6 06/10] dmaengine: tegra: Support address width > 39 bits Akhil R
2026-03-31 10:23 ` [PATCH v6 07/10] dmaengine: tegra: Use managed DMA controller registration Akhil R
2026-03-31 10:23 ` [PATCH v6 08/10] dmaengine: tegra: Use iommu-map for stream ID Akhil R
2026-03-31 14:12 ` Frank Li
2026-03-31 10:23 ` [PATCH v6 09/10] dmaengine: tegra: Add Tegra264 support Akhil R
2026-03-31 10:23 ` [PATCH v6 10/10] arm64: tegra: Enable GPCDMA in Tegra264 and add iommu-map Akhil R
2026-03-31 18:06 ` [PATCH v6 00/10] Add GPCDMA support in Tegra264 Jon Hunter
2026-04-10 8:09 ` 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=d548278c-8bbd-4871-8fb6-e22db1688546@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@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