From: "Rob Herring (Arm)" <robh@kernel.org>
To: Akhil R <akhilrajeev@nvidia.com>
Cc: Vinod Koul <vkoul@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Thierry Reding <thierry.reding@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Frank Li <Frank.Li@kernel.org>,
Jonathan Hunter <jonathanh@nvidia.com>,
dmaengine@vger.kernel.org,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-tegra@vger.kernel.org
Subject: Re: [PATCH v3 2/9] dt-bindings: dma: nvidia,tegra186-gpc-dma: Make reset optional
Date: Wed, 25 Mar 2026 11:37:28 -0500 [thread overview]
Message-ID: <177445664819.3770754.8129051164742800541.robh@kernel.org> (raw)
In-Reply-To: <20260316171823.61800-3-akhilrajeev@nvidia.com>
On Mon, 16 Mar 2026 22:48:16 +0530, Akhil R wrote:
> On Tegra264, GPCDMA reset control is not exposed to Linux and is handled
> by the boot firmware.
>
> Although the reset was not exposed in Tegra234 as well, the firmware
> supported a dummy reset which just returns success on reset without doing
> an actual reset. This is also not supported in Tegra264. Therefore mark
> 'reset' and 'reset-names' properties as required only for devices prior
> to Tegra264.
>
> This also necessitates that the Tegra264 compatible be standalone and
> cannot have the fallback compatible of Tegra186. Since there is no
> functional impact, we keep reset as required for Tegra234 to avoid
> breaking the ABI.
>
> Signed-off-by: Akhil R <akhilrajeev@nvidia.com>
> ---
> .../bindings/dma/nvidia,tegra186-gpc-dma.yaml | 25 +++++++++++++------
> 1 file changed, 18 insertions(+), 7 deletions(-)
>
Acked-by: Rob Herring (Arm) <robh@kernel.org>
next prev parent reply other threads:[~2026-03-25 16:37 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) [this message]
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
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=177445664819.3770754.8129051164742800541.robh@kernel.org \
--to=robh@kernel.org \
--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=jonathanh@nvidia.com \
--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=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