From: Rajesh Gumasta <rgumasta@nvidia.com>
To: Thierry Reding <thierry.reding@gmail.com>
Cc: Laxman Dewangan <ldewangan@nvidia.com>,
Jonathan Hunter <jonathanh@nvidia.com>,
"vkoul@kernel.org" <vkoul@kernel.org>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"p.zabel@pengutronix.de" <p.zabel@pengutronix.de>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"linux-tegra@vger.kernel.org" <linux-tegra@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Krishna Yarlagadda" <kyarlagadda@nvidia.com>
Subject: RE: [Patch v1 0/4] Add Nvidia Tegra GPC-DMA driver
Date: Mon, 20 Jul 2020 10:00:27 +0000 [thread overview]
Message-ID: <MN2PR12MB4143A3B01549E8243280CF30A27B0@MN2PR12MB4143.namprd12.prod.outlook.com> (raw)
In-Reply-To: <20200720092556.GA2141917@ulmo>
> -----Original Message-----
> From: Thierry Reding <thierry.reding@gmail.com>
> Sent: Monday, July 20, 2020 2:56 PM
> To: Rajesh Gumasta <rgumasta@nvidia.com>
> Cc: Laxman Dewangan <ldewangan@nvidia.com>; Jonathan Hunter
> <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; Krishna Yarlagadda
> <kyarlagadda@nvidia.com>
> Subject: Re: [Patch v1 0/4] Add Nvidia Tegra GPC-DMA driver
>
> 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.
>
I have used below parameter setting with kernel's built-in dmatest module to test mem to mem copy
cd /sys/module/dmatest/parameters
echo 50000 > iterations
echo dma0chan20 > channel
echo 1 > run
> Thanks,
> Thierry
>
> >
> > --
> > 2.7.4
> >
Thanks
Rajesh Gumasta
prev parent reply other threads:[~2020-07-20 10:00 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
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
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 ` [Patch v1 0/4] Add Nvidia Tegra GPC-DMA driver Thierry Reding
2020-07-20 10:00 ` Rajesh Gumasta [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=MN2PR12MB4143A3B01549E8243280CF30A27B0@MN2PR12MB4143.namprd12.prod.outlook.com \
--to=rgumasta@nvidia.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=thierry.reding@gmail.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).