From: Sinan Kaya <okaya@codeaurora.org>
To: Vinod Koul <vinod.koul@intel.com>,
Bharat Kumar Gogada <bharat.kumar.gogada@xilinx.com>
Cc: "linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
Bjorn Helgaas <bhelgaas@google.com>,
nofooter <nofooter@xilinx.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>
Subject: Re: PCIe EndPoint DMA driver with DMA Framework
Date: Mon, 13 Jun 2016 10:07:05 -0400 [thread overview]
Message-ID: <575EBE09.9090603@codeaurora.org> (raw)
In-Reply-To: <20160613052531.GZ16910@localhost>
On 6/13/2016 1:25 AM, Vinod Koul wrote:
>> We are planning to write a PCIe EndPoint DMA driver with DMA Framework
>> > targeting x86 machine. (
>> > "https://www.kernel.org/doc/Documentation/dmaengine/provider.txt") Our DMA
>> > controller is part of PCIe End Point. We are targeting to measure PCIe
>> > performance with this Framework driver.
>> >
>> > But when I see DMA Framework drivers is kernel source "drivers/dma" most
>> > of the drivers are platform drivers.
> wrong, there are bunch of PCI X86 driver. Look closely dw, ioat etc
I usually see endpoint specific DMA code to reside in the endpoint device
driver not in the dmaengine directory.
I think the main question is who the consumer of this DMA controller is like
Vinod asked.
If it is a general purpose DMA controller then dmaengine would be the right
place.
If it is specific to your endpoint, then it should be set up and used in your
endpoint device driver.
--
Sinan Kaya
Qualcomm Technologies, Inc. on behalf of Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum, a Linux Foundation Collaborative Project
next prev parent reply other threads:[~2016-06-13 14:07 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-10 15:39 PCIe EndPoint DMA driver with DMA Framework Bharat Kumar Gogada
2016-06-13 5:25 ` Vinod Koul
2016-06-13 14:07 ` Sinan Kaya [this message]
2016-06-14 11:40 ` Bharat Kumar Gogada
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=575EBE09.9090603@codeaurora.org \
--to=okaya@codeaurora.org \
--cc=bharat.kumar.gogada@xilinx.com \
--cc=bhelgaas@google.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=nofooter@xilinx.com \
--cc=vinod.koul@intel.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