mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: "Rob Herring (Arm)" <robh@kernel.org>
To: Sheetal <sheetal@nvidia.com>
Cc: Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Sameer Pujar <spujar@nvidia.com>,
	linux-tegra@vger.kernel.org,
	Thierry Reding <thierry.reding@kernel.org>,
	Anupama Kunkulagunta <akunkulagunt@nvidia.com>,
	dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
	Frank Li <Frank.Li@kernel.org>,
	linux-kernel@vger.kernel.org, Vinod Koul <vkoul@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Jonathan Hunter <jonathanh@nvidia.com>,
	Mohan Kumar <mkumard@nvidia.com>,
	Laxman Dewangan <ldewangan@nvidia.com>
Subject: Re: [PATCH 1/3] dt-bindings: dma: nvidia,tegra210-adma: Add Tegra268 support
Date: Thu, 19 Nov 2026 15:49:02 -0600	[thread overview]
Message-ID: <179512494227.783763.1329720459172434228.robh@kernel.org> (raw)
In-Reply-To: <20261104110932.1097294-2-sheetal@nvidia.com>


On Wed, 04 Nov 2026 11:09:30 +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>
> ---
>  .../bindings/dma/nvidia,tegra210-adma.yaml          | 13 +++++++++++++
>  1 file changed, 13 insertions(+)
> 

Reviewed-by: Rob Herring (Arm) <robh@kernel.org>


  parent reply	other threads:[~2026-11-19 21:49 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 11:09 [PATCH 0/3] dmaengine: tegra210-adma: " Sheetal
2026-11-04 11:09 ` [PATCH 1/3] dt-bindings: dma: nvidia,tegra210-adma: " Sheetal
2026-11-12 21:05   ` Frank Li
2026-11-19 21:49   ` Rob Herring (Arm) [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=179512494227.783763.1329720459172434228.robh@kernel.org \
    --to=robh@kernel.org \
    --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=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

all inboxes | Powered by JetHome®