Linux Tegra architecture development
 help / color / mirror / Atom feed
From: Vinod Koul <vkoul@kernel.org>
To: robh@kernel.org, krzk+dt@kernel.org, conor+dt@kernel.org,
	 Mohan Kumar D <mkumard@nvidia.com>
Cc: dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
	 linux-tegra@vger.kernel.org, linux-kernel@vger.kernel.org,
	 treding@nvidia.com, jonathanh@nvidia.com, spujar@nvidia.com
Subject: Re: [PATCH v2 RESEND 0/2] Add Tegra ADMA channel page support
Date: Tue, 24 Dec 2024 16:12:10 +0530	[thread overview]
Message-ID: <173503693084.903491.14497745388505993099.b4-ty@kernel.org> (raw)
In-Reply-To: <20241217074358.340180-1-mkumard@nvidia.com>


On Tue, 17 Dec 2024 13:13:56 +0530, Mohan Kumar D wrote:
> Multiple ADMA Channel page hardware support has been added from
> TEGRA186 and onwards. Add channel page handling support in the tegra
> adma driver
> 
> Changelog
> =========
> 
> [...]

Applied, thanks!

[1/2] dt-bindings: dma: Support channel page to nvidia,tegra210-adma
      commit: 762b37fc6ae2af0c7ddf36556fe7427575e9c759
[2/2] dmaengine: tegra210-adma: Support channel page
      commit: 68811c928f88828f188656dd3c9c184eeec2ce86

Best regards,
-- 
~Vinod



      parent reply	other threads:[~2024-12-24 10:42 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2024-12-17  7:43 [PATCH v2 RESEND 0/2] Add Tegra ADMA channel page support Mohan Kumar D
2024-12-17  7:43 ` [PATCH v2 RESEND 1/2] dt-bindings: dma: Support channel page to nvidia,tegra210-adma Mohan Kumar D
2024-12-17 18:22   ` Conor Dooley
2024-12-17  7:43 ` [PATCH v2 RESEND 2/2] dmaengine: tegra210-adma: Support channel page Mohan Kumar D
2025-01-18 16:33   ` Guenter Roeck
2025-01-20  3:46     ` Mohan Kumar D
2024-12-24 10:42 ` Vinod Koul [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=173503693084.903491.14497745388505993099.b4-ty@kernel.org \
    --to=vkoul@kernel.org \
    --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=linux-kernel@vger.kernel.org \
    --cc=linux-tegra@vger.kernel.org \
    --cc=mkumard@nvidia.com \
    --cc=robh@kernel.org \
    --cc=spujar@nvidia.com \
    --cc=treding@nvidia.com \
    /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