From: Vinod Koul <vkoul@kernel.org>
To: Kishon Vijay Abraham I <kishon@ti.com>
Cc: "lorenzo.pieralisi@arm.com" <lorenzo.pieralisi@arm.com>,
"arnd@arndb.de" <arnd@arndb.de>,
"gregkh@linuxfoundation.org" <gregkh@linuxfoundation.org>,
Gustavo Pimentel <Gustavo.Pimentel@synopsys.com>,
"palmer@sifive.com" <palmer@sifive.com>,
"kjlu@umn.edu" <kjlu@umn.edu>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"bhelgaas@google.com" <bhelgaas@google.com>,
Alan Mikhak <alan.mikhak@sifive.com>,
"paul.walmsley@sifive.com" <paul.walmsley@sifive.com>,
"linux-pci@vger.kernel.org" <linux-pci@vger.kernel.org>,
"jingoohan1@gmail.com" <jingoohan1@gmail.com>,
"linux-riscv@lists.infradead.org"
<linux-riscv@lists.infradead.org>,
"wen.yang99@zte.com.cn" <wen.yang99@zte.com.cn>
Subject: Re: [PATCH] PCI: endpoint: Add DMA to Linux PCI EP Framework
Date: Mon, 3 Jun 2019 10:12:51 +0530 [thread overview]
Message-ID: <20190603044251.GS15118@vkoul-mobl> (raw)
In-Reply-To: <400a7c28-39b1-f242-7810-a1d38aa51446@ti.com>
Hi Kishon,
On 03-06-19, 09:54, Kishon Vijay Abraham I wrote:
> right. For the endpoint case, drivers/pci/controller should register with the
> dmaengine i.e if the controller has aN embedded DMA (I think it should be okay
> to keep that in drivers/pci/controller itself instead of drivers/dma) and
> drivers/pci/endpoint/functions/ should use dmaengine API's (Depending on the
> platform, this will either use system DMA or DMA within the PCI controller).
Typically I would prefer the driver to be part of drivers/dma.
Would this be a standalone driver or part of the endpoint driver. In
former case we can move to dmaengine for latter i guess it makes sense
to stay in PCI
Thanks
--
~Vinod
_______________________________________________
linux-riscv mailing list
linux-riscv@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-riscv
prev parent reply other threads:[~2019-06-03 4:43 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-05-23 22:24 [PATCH] PCI: endpoint: Add DMA to Linux PCI EP Framework Alan Mikhak
2019-05-24 8:59 ` Gustavo Pimentel
2019-05-24 19:42 ` Alan Mikhak
2019-05-27 9:09 ` Gustavo Pimentel
2019-05-29 22:37 ` Alan Mikhak
2019-05-30 5:46 ` Kishon Vijay Abraham I
2019-05-30 17:56 ` Alan Mikhak
2019-05-31 5:06 ` Kishon Vijay Abraham I
2019-05-31 18:16 ` Alan Mikhak
2019-06-03 4:41 ` Kishon Vijay Abraham I
2019-06-03 17:42 ` Alan Mikhak
2019-09-13 12:11 ` Kishon Vijay Abraham I
2019-09-13 17:39 ` Alan Mikhak
2019-05-31 5:07 ` Vinod Koul
2019-05-31 5:20 ` Kishon Vijay Abraham I
2019-05-31 6:32 ` Vinod Koul
2019-05-31 7:49 ` Arnd Bergmann
2019-06-03 4:29 ` Kishon Vijay Abraham I
2019-06-03 4:24 ` Kishon Vijay Abraham I
2019-06-03 4: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=20190603044251.GS15118@vkoul-mobl \
--to=vkoul@kernel.org \
--cc=Gustavo.Pimentel@synopsys.com \
--cc=alan.mikhak@sifive.com \
--cc=arnd@arndb.de \
--cc=bhelgaas@google.com \
--cc=gregkh@linuxfoundation.org \
--cc=jingoohan1@gmail.com \
--cc=kishon@ti.com \
--cc=kjlu@umn.edu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pci@vger.kernel.org \
--cc=linux-riscv@lists.infradead.org \
--cc=lorenzo.pieralisi@arm.com \
--cc=palmer@sifive.com \
--cc=paul.walmsley@sifive.com \
--cc=wen.yang99@zte.com.cn \
/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).