From: Andrew Bresticker <abrestic@chromium.org>
To: Vinod Koul <vinod.koul@intel.com>,
Dan Williams <dan.j.williams@intel.com>
Cc: Andrew Bresticker <abrestic@chromium.org>,
Rob Herring <robh+dt@kernel.org>, Pawel Moll <pawel.moll@arm.com>,
Mark Rutland <mark.rutland@arm.com>,
Ian Campbell <ijc+devicetree@hellion.org.uk>,
Kumar Gala <galak@codeaurora.org>,
Grant Likely <grant.likely@linaro.org>,
James Hartley <james.hartley@imgtec.com>,
James Hogan <james.hogan@imgtec.com>,
Ezequiel Garcia <ezequiel.garcia@imgtec.com>,
Damien Horsley <Damien.Horsley@imgtec.com>,
Arnd Bergmann <arnd@arndb.de>,
dmaengine@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH V3 0/2] dmaengine: Support for IMG MDC
Date: Thu, 11 Dec 2014 14:59:15 -0800 [thread overview]
Message-ID: <1418338757-10022-1-git-send-email-abrestic@chromium.org> (raw)
This series adds support for the IMG Multi-threaded DMA Controller (MDC)
which is found on IMG SoCs. Currently this driver only supports the
variant found on the MIPS-based Pistachio SoC.
The MDC supports slave and memory-to-memory transfers on up to 32 channels.
Requests from channels are handled by MDC threads. Thread assignments are
per-channel and are specified in the device-tree.
Tested on a platform based on the Pistachio SoC with additional patches.
Support for Pistachio will be submitted later. Slave DMA was tested
with the recently submitted IMG SPFI driver [1] and memory-to-memory
DMA was tested with the dmatest module.
Based on Vinod's slave-dma/topic/slave_caps_device_control_fix.
Changes from v2:
- addressed Vinod's review comments
Changes from v1:
- addressed Arnd's review comments
- rebased on Maxime's dmaengine cleanups
[1] https://lkml.org/lkml/2014/11/12/763
Andrew Bresticker (2):
dmaengine: Add binding document for IMG MDC
dmaengine: Add driver for IMG MDC
.../devicetree/bindings/dma/img-mdc-dma.txt | 57 ++
drivers/dma/Kconfig | 9 +
drivers/dma/Makefile | 1 +
drivers/dma/img-mdc-dma.c | 1011 ++++++++++++++++++++
4 files changed, 1078 insertions(+)
create mode 100644 Documentation/devicetree/bindings/dma/img-mdc-dma.txt
create mode 100644 drivers/dma/img-mdc-dma.c
--
2.2.0.rc0.207.ga3a616c
next reply other threads:[~2014-12-11 22:59 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-11 22:59 Andrew Bresticker [this message]
2014-12-11 22:59 ` [PATCH V3 1/2] dmaengine: Add binding document for IMG MDC Andrew Bresticker
[not found] ` <1418338757-10022-1-git-send-email-abrestic-F7+t8E8rja9g9hUCZPvPmw@public.gmane.org>
2014-12-11 22:59 ` [PATCH V3 2/2] dmaengine: Add driver " Andrew Bresticker
2014-12-24 5:22 ` Vinod Koul
2014-12-24 17:21 ` Andrew Bresticker
2014-12-24 20:06 ` James Hartley
2015-01-27 10:00 ` [PATCH V3 0/2] dmaengine: Support " Andrew Bresticker
2015-02-05 2:13 ` Vinod Koul
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=1418338757-10022-1-git-send-email-abrestic@chromium.org \
--to=abrestic@chromium.org \
--cc=Damien.Horsley@imgtec.com \
--cc=arnd@arndb.de \
--cc=dan.j.williams@intel.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=ezequiel.garcia@imgtec.com \
--cc=galak@codeaurora.org \
--cc=grant.likely@linaro.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=james.hartley@imgtec.com \
--cc=james.hogan@imgtec.com \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).