mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Jon Hunter <jonathanh@nvidia.com>
To: Sheetal <sheetal@nvidia.com>, Vinod Koul <vkoul@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>
Cc: Frank Li <Frank.Li@kernel.org>,
	Laxman Dewangan <ldewangan@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
Subject: Re: [PATCH 0/3] dmaengine: tegra210-adma: Add Tegra268 support
Date: Wed, 11 Nov 2026 14:12:05 +0000	[thread overview]
Message-ID: <5882de47-d50c-4e64-94b7-dc41b0e647cd@nvidia.com> (raw)
In-Reply-To: <20261104110932.1097294-1-sheetal@nvidia.com>


On 04/11/2026 11:09, Sheetal wrote:
> Tegra268 reuses the Tegra264 ADMA register layout but has ten DMA
> channels, five request IDs, six pages and a different uniform FIFO size.
> Add its binding and SoC data, and derive the shared page configuration
> masks from these limits.
> 
> Make the Tegra264 FIFO size explicit first so Tegra268 can select its
> FIFO size without changing the existing devices' FIFO programming.
> 
> Anupama Kunkulagunta (2):
>   dt-bindings: dma: nvidia,tegra210-adma: Add Tegra268 support
>   dmaengine: tegra210-adma: Add Tegra268 support
> 
> Sheetal (1):
>   dmaengine: tegra210-adma: Make Tegra264 FIFO size explicit
> 
>  .../bindings/dma/nvidia,tegra210-adma.yaml    | 13 ++++
>  drivers/dma/tegra210-adma.c                   | 73 +++++++++++++++----
>  2 files changed, 73 insertions(+), 13 deletions(-)
> 


For the series ...

Reviewed-by: Jon Hunter <jonathanh@nvidia.com>

Thanks!
Jon

-- 
nvpublic


      parent reply	other threads:[~2026-11-11 14:12 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-11-04 11:09 Sheetal
2026-11-04 11:09 ` [PATCH 1/3] dt-bindings: dma: nvidia,tegra210-adma: " Sheetal
2026-11-04 11:09 ` [PATCH 2/3] dmaengine: tegra210-adma: Make Tegra264 FIFO size explicit Sheetal
2026-11-04 11:09 ` [PATCH 3/3] dmaengine: tegra210-adma: Add Tegra268 support Sheetal
2026-11-11 14:12 ` 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=5882de47-d50c-4e64-94b7-dc41b0e647cd@nvidia.com \
    --to=jonathanh@nvidia.com \
    --cc=Frank.Li@kernel.org \
    --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=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

all inboxes | Powered by JetHome®