From: Sanjay R Mehta <sanmehta@amd.com>
To: Vinod Koul <vkoul@kernel.org>
Cc: "Hook, Gary" <Gary.Hook@amd.com>,
"S-k, Shyam-sundar" <Shyam-sundar.S-k@amd.com>,
"Shah, Nehal-bakulchandra" <Nehal-bakulchandra.Shah@amd.com>,
"Kumar, Rajesh" <Rajesh1.Kumar@amd.com>,
"mchehab+samsung@kernel.org" <mchehab+samsung@kernel.org>,
"davem@davemloft.net" <davem@davemloft.net>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
"robh@kernel.org" <robh@kernel.org>,
"linus.walleij@linaro.org" <linus.walleij@linaro.org>,
"nicolas.ferre@microchip.com" <nicolas.ferre@microchip.com>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: Re: [PATCH 0/4] *** AMD PTDMA driver ***
Date: Thu, 3 Oct 2019 17:27:14 +0000 [thread overview]
Message-ID: <8a83d483-d5e2-703c-61ed-adb88c1f9559@amd.com> (raw)
In-Reply-To: <20190924163744.GC3824@vkoul-mobl>
On 9/24/2019 10:07 PM, Vinod Koul wrote:
> [CAUTION: External Email]
>
> On 24-09-19, 07:31, Mehta, Sanju wrote:
>> From: Sanjay R Mehta <sanju.mehta@amd.com>
>>
>> *** This patch series adds support for AMD PTDMA engine ***
> What lots of stars!
>
> Can you describe the controller a bit more to help people set the
> context for the review!
>
> And also helps to make the email subject as "Add AMD PTDMA driver ...."
> or similar!
Okay sure Vinod. This will be resolved in next version of patch set.
>
>> Sanjay R Mehta (4):
>> dma: Add PTDMA Engine driver support
>> dma: Support for multiple PTDMA
>> dmaengine: Register as a DMA resource
>> dmaengine: Add debugfs entries for PTDMA information
> Can you be consistent with naming, and yes do use dmaengine!
>
>> MAINTAINERS | 6 +
>> drivers/dma/Kconfig | 2 +
>> drivers/dma/Makefile | 1 +
>> drivers/dma/ptdma/Kconfig | 8 +
>> drivers/dma/ptdma/Makefile | 12 +
>> drivers/dma/ptdma/ptdma-debugfs.c | 249 +++++++++++++
>> drivers/dma/ptdma/ptdma-dev.c | 445 +++++++++++++++++++++++
>> drivers/dma/ptdma/ptdma-dmaengine.c | 700 ++++++++++++++++++++++++++++++++++++
>> drivers/dma/ptdma/ptdma-ops.c | 464 ++++++++++++++++++++++++
>> drivers/dma/ptdma/ptdma-pci.c | 244 +++++++++++++
>> drivers/dma/ptdma/ptdma.h | 563 +++++++++++++++++++++++++++++
>> 11 files changed, 2694 insertions(+)
>> create mode 100644 drivers/dma/ptdma/Kconfig
>> create mode 100644 drivers/dma/ptdma/Makefile
>> create mode 100644 drivers/dma/ptdma/ptdma-debugfs.c
>> create mode 100644 drivers/dma/ptdma/ptdma-dev.c
>> create mode 100644 drivers/dma/ptdma/ptdma-dmaengine.c
>> create mode 100644 drivers/dma/ptdma/ptdma-ops.c
>> create mode 100644 drivers/dma/ptdma/ptdma-pci.c
>> create mode 100644 drivers/dma/ptdma/ptdma.h
>>
>> --
>> 2.7.4
> --
> ~Vinod
prev parent reply other threads:[~2019-10-03 17:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-24 7:31 [PATCH 0/4] *** AMD PTDMA driver *** Mehta, Sanju
2019-09-24 16:37 ` Vinod Koul
2019-10-03 17:27 ` Sanjay R Mehta [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=8a83d483-d5e2-703c-61ed-adb88c1f9559@amd.com \
--to=sanmehta@amd.com \
--cc=Gary.Hook@amd.com \
--cc=Nehal-bakulchandra.Shah@amd.com \
--cc=Rajesh1.Kumar@amd.com \
--cc=Shyam-sundar.S-k@amd.com \
--cc=dan.j.williams@intel.com \
--cc=davem@davemloft.net \
--cc=dmaengine@vger.kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mchehab+samsung@kernel.org \
--cc=nicolas.ferre@microchip.com \
--cc=robh@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;
as well as URLs for NNTP newsgroup(s).