From: Peter Ujfalusi <peter.ujfalusi@ti.com>
To: vinod.koul@intel.com, tony@atomide.com, linux@arm.linux.org.uk
Cc: grant.likely@linaro.org, dmaengine@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org,
linux-omap@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
robh+dt@kernel.org, nm@ti.com
Subject: [PATCH v3 0/7] dmaengine/dra7x: DMA router (crossbar support)
Date: Fri, 27 Mar 2015 14:26:46 +0200 [thread overview]
Message-ID: <1427459213-14611-1-git-send-email-peter.ujfalusi@ti.com> (raw)
Hi,
Vinod: is it OK if I send the Documnetation/dmanegine/ update a bit later when
we agree on what form it should be?
Changes since v2:
- not using regmap for the TI crossbar driver.
Changes since v1:
- Comments from Russell King and Paul Bolle addressed:
- Use the added defined in the omap-dma changes
- MODULE_* removed from the ti-dma-crossbar driver.
- DMA router documentation: do not limit the #dma-cells to be the same as the
dma controller's #dma-cells. It might be possible to have a router which needs
more information than the DMA controller (direct request pairing for example)
- Use defines in the ti-dma-crossbar driver
- Binding document for the ti-dma-crossbar driver
Intro mail from v1:
The series adds support for DMA router type of devices. They are used in SoCs
which has more peripherals with DMA request lines than the DMA controller can
handle.
The router itself is not part of the DMA controller and it's operation should be
transparent (as it is in the HW) for the SW stack.
This series takes into accound the comments Sricharan received for his version
of the crossbar driver:
https://lkml.org/lkml/2014/3/7/199
This implementation is not tied to any DMA driver so it is possible to use the
framework by other vendors, also ACPI version of binding can be easy enough to
be added.
Regards,
Peter
---
Peter Ujfalusi (7):
dmaengine: of_dma: Support for DMA routers
Documentation: devicetree: dma: Binding documentation for TI DMA
crossbar
dmaengine: Add driver for TI DMA crossbar on DRA7x
dmaengine: omap-dma: Use defines for dma channels and request count
dmaengine: omap-dma: Take DMA request number from DT if it is
available
dmaengine: omap-dma: Remove mapping between virtual channels and
requests
ARM: DTS: dra7x: Integrate sDMA crossbar
Documentation/devicetree/bindings/dma/dma.txt | 28 ++++
.../devicetree/bindings/dma/ti-dma-crossbar.txt | 52 ++++++
arch/arm/boot/dts/dra7.dtsi | 57 ++++---
drivers/dma/Kconfig | 4 +
drivers/dma/Makefile | 1 +
drivers/dma/dmaengine.c | 7 +
drivers/dma/of-dma.c | 92 +++++++++++
drivers/dma/omap-dma.c | 25 ++-
drivers/dma/ti-dma-crossbar.c | 179 +++++++++++++++++++++
include/linux/dmaengine.h | 17 ++
include/linux/of_dma.h | 21 +++
11 files changed, 455 insertions(+), 28 deletions(-)
create mode 100644 Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt
create mode 100644 drivers/dma/ti-dma-crossbar.c
--
2.3.3
next reply other threads:[~2015-03-27 12:26 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-03-27 12:26 Peter Ujfalusi [this message]
2015-03-27 12:26 ` [PATCH v3 1/7] dmaengine: of_dma: Support for DMA routers Peter Ujfalusi
2015-03-28 1:44 ` Arnd Bergmann
2015-03-31 16:48 ` Peter Ujfalusi
2015-03-27 12:26 ` [PATCH v3 2/7] Documentation: devicetree: dma: Binding documentation for TI DMA crossbar Peter Ujfalusi
2015-03-27 12:26 ` [PATCH v3 3/7] dmaengine: Add driver for TI DMA crossbar on DRA7x Peter Ujfalusi
2015-03-27 12:26 ` [PATCH v3 4/7] dmaengine: omap-dma: Use defines for dma channels and request count Peter Ujfalusi
2015-03-27 12:26 ` [PATCH v3 5/7] dmaengine: omap-dma: Take DMA request number from DT if it is available Peter Ujfalusi
2015-03-27 20:24 ` Russell King - ARM Linux
2015-03-31 14:47 ` Peter Ujfalusi
2015-03-27 12:26 ` [PATCH v3 6/7] dmaengine: omap-dma: Remove mapping between virtual channels and requests Peter Ujfalusi
2015-03-27 20:22 ` Russell King - ARM Linux
2015-03-31 15:44 ` Peter Ujfalusi
2015-03-27 12:26 ` [PATCH v3 7/7] ARM: DTS: dra7x: Integrate sDMA crossbar Peter Ujfalusi
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=1427459213-14611-1-git-send-email-peter.ujfalusi@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=devicetree@vger.kernel.org \
--cc=dmaengine@vger.kernel.org \
--cc=grant.likely@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=nm@ti.com \
--cc=robh+dt@kernel.org \
--cc=tony@atomide.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;
as well as URLs for NNTP newsgroup(s).