From: Frank Li <Frank.li@oss.nxp.com>
To: Sheetal <sheetal@nvidia.com>
Cc: Vinod Koul <vkoul@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Frank Li <Frank.Li@kernel.org>,
Laxman Dewangan <ldewangan@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
Thierry Reding <thierry.reding@kernel.org>,
Mohan Kumar <mkumard@nvidia.com>,
Sameer Pujar <spujar@nvidia.com>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
Anupama Kunkulagunta <akunkulagunt@nvidia.com>
Subject: Re: [PATCH 1/3] dt-bindings: dma: nvidia,tegra210-adma: Add Tegra268 support
Date: Thu, 12 Nov 2026 15:05:56 -0600 [thread overview]
Message-ID: <avYqNEiy2ZiNItlK@SMW015318> (raw)
In-Reply-To: <20261104110932.1097294-2-sheetal@nvidia.com>
On Wed, Nov 04, 2026 at 11:09:30AM +0000, Sheetal wrote:
>
> From: Anupama Kunkulagunta <akunkulagunt@nvidia.com>
>
> Add the Tegra268 ADMA compatible. Tegra268 has 10 ADMA channels,
> so set the interrupt limit accordingly.
>
> Signed-off-by: Anupama Kunkulagunta <akunkulagunt@nvidia.com>
> Signed-off-by: Sheetal <sheetal@nvidia.com>
> ---
Reviewed-by: Frank Li <Frank.Li@nxp.com>
> .../bindings/dma/nvidia,tegra210-adma.yaml | 13 +++++++++++++
> 1 file changed, 13 insertions(+)
>
> diff --git a/Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml b/Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml
> index 269a1f7ebdbb..6aa9b83b90d9 100644
> --- a/Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml
> +++ b/Documentation/devicetree/bindings/dma/nvidia,tegra210-adma.yaml
> @@ -20,6 +20,7 @@ properties:
> - nvidia,tegra210-adma
> - nvidia,tegra186-adma
> - nvidia,tegra264-adma
> + - nvidia,tegra268-adma
> - items:
> - enum:
> - nvidia,tegra234-adma
> @@ -100,6 +101,17 @@ allOf:
> interrupts:
> maxItems: 32
>
> + - if:
> + properties:
> + compatible:
> + contains:
> + enum:
> + - nvidia,tegra268-adma
> + then:
> + properties:
> + interrupts:
> + maxItems: 10
> +
> - if:
> properties:
> compatible:
> @@ -107,6 +119,7 @@ allOf:
> enum:
> - nvidia,tegra186-adma
> - nvidia,tegra264-adma
> + - nvidia,tegra268-adma
> then:
> anyOf:
> - properties:
> --
> 2.43.0
>
next prev parent reply other threads:[~2026-11-12 21:06 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-11-04 11:09 [PATCH 0/3] dmaengine: tegra210-adma: Add Tegra268 support Sheetal
2026-11-04 11:09 ` [PATCH 1/3] dt-bindings: dma: nvidia,tegra210-adma: " Sheetal
2026-11-12 21:05 ` Frank Li [this message]
2026-11-04 11:09 ` [PATCH 2/3] dmaengine: tegra210-adma: Make Tegra264 FIFO size explicit Sheetal
2026-11-12 21:10 ` Frank Li
2026-11-04 11:09 ` [PATCH 3/3] dmaengine: tegra210-adma: Add Tegra268 support Sheetal
2026-11-12 21:13 ` Frank Li
2026-11-11 14:12 ` [PATCH 0/3] " 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=avYqNEiy2ZiNItlK@SMW015318 \
--to=frank.li@oss.nxp.com \
--cc=Frank.Li@kernel.org \
--cc=akunkulagunt@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=mkumard@nvidia.com \
--cc=robh@kernel.org \
--cc=sheetal@nvidia.com \
--cc=spujar@nvidia.com \
--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