From: hch@infradead.org (Christoph Hellwig)
To: linux-arm-kernel@lists.infradead.org
Subject: Support for configurable PCIe endpoint
Date: Wed, 3 Aug 2016 02:47:47 -0700 [thread overview]
Message-ID: <20160803094747.GA10170@infradead.org> (raw)
In-Reply-To: <57A18927.9070003@ti.com>
On Wed, Aug 03, 2016 at 11:33:19AM +0530, Kishon Vijay Abraham I wrote:
> Hi,
>
> The PCIe controller present in TI's DRA7 SoC is capable of operating either in
> Root Complex mode or Endpoint mode. (It uses Synopsys Designware Core).I'd
> assume most of the PCIe controllers on other platforms that use Designware core
> should also be capable to operate in endpoint mode. But linux kernel right now
> supports only RC mode.
>
> PCIe endpoint support discussion came up briefly before [1] but it was felt the
> practical use case will find firmware more suitable and endpoint support in
> kernel can be used only for validation or demo.
I disagree. It's highly useful for rapid prototyping of hardware
interfaces, and I've been looking into PCIe EP drivers for exactly
that reason recently. Going a little offtopic: any good DRA7 eval
boards you'd recommend to try for this purpose?
We already have a EP driver in the tree:
drivers/misc/spear13xx_pcie_gadget.c
but as far as I can tell it doesn't really work at the moment.
> Validation or demo is itself a valid use case in my opinion (consider something
> similar to gadget zero for USB). There can be other use cases as well. The RC
> can use the SoC with EP mode support as an accelerator to accomplish specific
> task. Here RC gives data to the EP. The EP processes the data. The processing
> can be done either in ARM itself or it can use other hardware accelerators
> (like DSP, IVA-HD etc..) present in the EP system. If HW accelerator is used,
> the linux kernel running in ARM can be used to accomplish other tasks. Once EP
> mode support is added, I think more use cases will be added.
That sounds useful as well.
> >From the high level this should look _similar_ to the gadget framework of USB.
> One difference from USB would be this should allow HW components (like DSP, PRU
> etc.. and maybe even some peripheral) in the EP system to be used by RC system.
Indeed.
> So these are the high-level steps that I thought would be needed to add EP
> support in linux.
> *) move pcie-designware.c out of drivers/pci/host (maybe create a
> drivers/pci/designware/ folder?). All users of pcie-designware.c should be
> moved here.
> This is in preparation for adding EP mode support to designware.
I'd use a new drivers/pci/controller. Or maybe just skip the rename
for now and see how this evolves.
The rest of the plan sounds fine to me.
next prev parent reply other threads:[~2016-08-03 9:47 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-08-03 6:03 Support for configurable PCIe endpoint Kishon Vijay Abraham I
2016-08-03 7:42 ` Arnd Bergmann
2016-08-04 8:19 ` Kishon Vijay Abraham I
2016-08-03 9:47 ` Christoph Hellwig [this message]
2016-08-03 16:03 ` Arnd Bergmann
2016-08-03 17:27 ` Christoph Hellwig
2016-08-03 19:38 ` Arnd Bergmann
2016-08-04 8:49 ` Kishon Vijay Abraham I
2016-08-03 13:39 ` Joao Pinto
2016-08-04 10:02 ` Kishon Vijay Abraham I
2016-08-04 11:13 ` Arnd Bergmann
2016-08-18 13:14 ` Kishon Vijay Abraham I
2016-08-25 12:59 ` Arnd Bergmann
2016-08-29 11:47 ` Kishon Vijay Abraham I
2016-08-17 9:49 ` Mingkai Hu
2016-08-18 12:24 ` Kishon Vijay Abraham I
2016-08-29 15:25 ` Roy Zang
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=20160803094747.GA10170@infradead.org \
--to=hch@infradead.org \
--cc=linux-arm-kernel@lists.infradead.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