From: Arnd Bergmann <arnd@arndb.de>
To: Mayuresh Chitale <mchitale@apm.com>
Cc: "devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"vinod.koul@intel.com" <vinod.koul@intel.com>,
"jcm@redhat.com" <jcm@redhat.com>,
"patches@apm.com" <patches@apm.com>,
"ddutile@redhat.com" <ddutile@redhat.com>,
"dmaengine@vger.kernel.org" <dmaengine@vger.kernel.org>,
"dan.j.williams@intel.com" <dan.j.williams@intel.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 4/4] dma: X-Gene PCIE DMA Driver
Date: Wed, 07 Jan 2015 17:22:14 +0100 [thread overview]
Message-ID: <1765004.TVkcxIlmTg@wuerfel> (raw)
In-Reply-To: <CAL-zptNW81KwWXnMcsh_S5KQFMNGysm=ATmixMge6RXj_U-_zQ@mail.gmail.com>
On Wednesday 07 January 2015 21:35:22 Mayuresh Chitale wrote:
> >
> > I think I'm missing something important here. What exactly is the
> > interaction with PCI here? Is it possible to use the dmaengine
> > driver at all when the PCI host controller is not in endpoint mode?
> Yes. Dmaengine driver can be used when port is configured as RC or EP.
> >
> > Does the dmaengine show up as a PCI device when the PCI controller is
> > in host mode?
> No. It sits between AXI and PCI interfaces but it needs to be
> programmed via the config bar.
Ok, I see. So in RC mode, it sounds like this is a regular DMA engine
that could be used with arbitrary slaves, but in EP mode it would
actually be controlled by the remote host, right?
When we are in RC mode, who sets up that BAR? If this is set up by
the firmware, we can just have the register appear in the DT as well,
as it's known, and when we are in EP mode, it sounds like we would
not even use the dmaengine because it's owned by the other host.
Or is there a way that in EP mode, both sides would access the
dma engine simultaneously?
Arnd
next prev parent reply other threads:[~2015-01-07 16:22 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-01-07 5:28 [PATCH 0/4] APM X-Gene PCIe DMA driver Mayuresh Chitale
2015-01-07 5:28 ` [PATCH 1/4] MAINTAINERS: Add entry for X-Gene PCIE " Mayuresh Chitale
2015-01-07 5:28 ` [PATCH 2/4] Documentation: dt-bindings: Add the binding info for APM X-Gene PCIe " Mayuresh Chitale
2015-01-07 8:30 ` Arnd Bergmann
2015-01-07 10:42 ` Mayuresh Chitale
2015-01-07 5:28 ` [PATCH 3/4] arm64: dts: Add APM X-Gene PCIe DMA device tree nodes Mayuresh Chitale
[not found] ` <1420608537-12296-4-git-send-email-mchitale-qTEPVZfXA3Y@public.gmane.org>
2015-01-07 8:37 ` Arnd Bergmann
2015-01-07 10:45 ` Mayuresh Chitale
[not found] ` <CAL-zptPDU2qoot-aZMDwRmPQ_4QoCsqtQZ=kc-fN-Ts68qrVDQ-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2015-01-07 11:28 ` Arnd Bergmann
2015-01-07 5:28 ` [PATCH 4/4] dma: X-Gene PCIE DMA Driver Mayuresh Chitale
2015-01-07 8:35 ` Arnd Bergmann
2015-01-07 11:25 ` Mayuresh Chitale
2015-01-07 12:46 ` Arnd Bergmann
2015-01-07 16:05 ` Mayuresh Chitale
2015-01-07 16:22 ` Arnd Bergmann [this message]
2015-01-08 6:30 ` Mayuresh Chitale
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=1765004.TVkcxIlmTg@wuerfel \
--to=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=ddutile@redhat.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=jcm@redhat.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=mchitale@apm.com \
--cc=patches@apm.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