From: Thierry Reding <thierry.reding@gmail.com>
To: Rajesh Gumasta <rgumasta@nvidia.com>
Cc: ldewangan@nvidia.com, jonathanh@nvidia.com, vkoul@kernel.org,
dan.j.williams@intel.com, p.zabel@pengutronix.de,
dmaengine@vger.kernel.org, linux-tegra@vger.kernel.org,
linux-kernel@vger.kernel.org, kyarlagadda@nvidia.com
Subject: Re: [Patch v1 0/4] Add Nvidia Tegra GPC-DMA driver
Date: Mon, 20 Jul 2020 11:25:56 +0200 [thread overview]
Message-ID: <20200720092556.GA2141917@ulmo> (raw)
In-Reply-To: <1595226856-19241-1-git-send-email-rgumasta@nvidia.com>
[-- Attachment #1: Type: text/plain, Size: 1662 bytes --]
On Mon, Jul 20, 2020 at 12:04:12PM +0530, Rajesh Gumasta wrote:
> Add support for Nvida Tegra general purpose DMA driver for
> Tegra186 and Tegra194 platform.
>
> Patch 1: Add dt-binding document for Tegra GPCDMA driver
> Patch 2: Add Tegra GPCDMA driver
> Patch 3: Enable Tegra GPCDMA as module
> Patch 4: Add GPCDMA DT node for Tegra186 and Tegra194
>
> Rajesh Gumasta (4):
> dt-bindings: dma: Add DT binding document
> dma: tegra: Adding Tegra GPC DMA controller driver
> arm64: configs: enable tegra gpc dma
> arm64: tegra: Add GPCDMA node in dt
>
> .../bindings/dma/nvidia,tegra-gpc-dma.yaml | 99 ++
> arch/arm64/boot/dts/nvidia/tegra186-p3310.dtsi | 4 +
> arch/arm64/boot/dts/nvidia/tegra186.dtsi | 46 +
> arch/arm64/boot/dts/nvidia/tegra194.dtsi | 44 +
> arch/arm64/configs/defconfig | 1 +
> drivers/dma/Kconfig | 12 +
> drivers/dma/Makefile | 1 +
> drivers/dma/tegra-gpc-dma.c | 1512 ++++++++++++++++++++
> 8 files changed, 1719 insertions(+)
> create mode 100644 Documentation/devicetree/bindings/dma/nvidia,tegra-gpc-dma.yaml
> create mode 100644 drivers/dma/tegra-gpc-dma.c
Hi Rajesh,
can you provide instructions on how to test that this driver does what
it's supposed to? I could probably figure out how to run this with the
kernel's built-in dmatest module, but if you could provide a set of
parameters that you've used or other instructions on how to validate
this it would greatly help.
Thanks,
Thierry
>
> --
> 2.7.4
>
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 833 bytes --]
next prev parent reply other threads:[~2020-07-20 9:25 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-07-20 6:34 [Patch v1 0/4] Add Nvidia Tegra GPC-DMA driver Rajesh Gumasta
2020-07-20 6:34 ` [Patch v1 1/4] dt-bindings: dma: Add DT binding document Rajesh Gumasta
2020-07-20 6:34 ` [Patch v1 2/4] dma: tegra: Adding Tegra GPC DMA controller driver Rajesh Gumasta
[not found] ` <1595226856-19241-3-git-send-email-rgumasta-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-07-20 9:37 ` Philipp Zabel
2020-07-20 11:58 ` kernel test robot
2020-07-20 15:12 ` Dmitry Osipenko
2020-07-20 15:42 ` Randy Dunlap
2020-07-27 9:07 ` Vinod Koul
[not found] ` <1595226856-19241-1-git-send-email-rgumasta-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2020-07-20 6:34 ` [Patch v1 3/4] arm64: configs: enable tegra gpc dma Rajesh Gumasta
2020-07-20 6:34 ` [Patch v1 4/4] arm64: tegra: Add GPCDMA node in dt Rajesh Gumasta
2020-07-20 9:25 ` Thierry Reding [this message]
2020-07-20 10:00 ` [Patch v1 0/4] Add Nvidia Tegra GPC-DMA driver Rajesh Gumasta
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=20200720092556.GA2141917@ulmo \
--to=thierry.reding@gmail.com \
--cc=dan.j.williams@intel.com \
--cc=dmaengine@vger.kernel.org \
--cc=jonathanh@nvidia.com \
--cc=kyarlagadda@nvidia.com \
--cc=ldewangan@nvidia.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-tegra@vger.kernel.org \
--cc=p.zabel@pengutronix.de \
--cc=rgumasta@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).