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>, <arnd@arndb.de>, <maxime.ripard@free-electrons.com>
Subject: Re: [PATCH v5 0/8] dmaengine/dra7x: DMA router (crossbar support)
Date: Wed, 22 Apr 2015 10:38:27 +0300 [thread overview]
Message-ID: <55374FF3.1030003@ti.com> (raw)
In-Reply-To: <1428572154-3548-1-git-send-email-peter.ujfalusi@ti.com>
On 04/09/2015 12:35 PM, Peter Ujfalusi wrote:
> Vinod: is it OK if I send the Documnetation/dmanegine/ update a bit later when
> I have finished it?
>
> Changes since v4:
> - Comments from Maxime Ripard addressed:
> - long line fixed in of-dma.c
> - node leaks has been fixed in ti-dma-crossbar
> - Using devm_ioremap_resource() in ti-dma-crossbar
> - u16 casting has been addressed
> - Router drivers are expected to return with ERR_PTR in case their
> of_dma_route_allocate() callback fails.
Are there more comments I need to address with this series?
Thanks,
Péter
> Changes since v3:
> - Comments from Russell:
> - Warnings removed in case of non DT boot when taking the DMA request number
> - Reduced the number of channels presented to DMAengine
> - removed the dma_sig parameter from omap_dma_chan_init()
> - Comments from Arnd:
> - dma-device property renamed to dma-masters
> - Allow list of phandes in dma-masters
>
> 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 (8):
> 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
> dmaengine: omap-dma: Reduce the number of virtual channels
> 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 | 89 ++++++++++
> drivers/dma/omap-dma.c | 29 +++-
> drivers/dma/ti-dma-crossbar.c | 188 +++++++++++++++++++++
> include/linux/dmaengine.h | 17 ++
> include/linux/of_dma.h | 21 +++
> 11 files changed, 463 insertions(+), 30 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/dma/ti-dma-crossbar.txt
> create mode 100644 drivers/dma/ti-dma-crossbar.c
>
next prev parent reply other threads:[~2015-04-22 7:39 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-04-09 9:35 [PATCH v5 0/8] dmaengine/dra7x: DMA router (crossbar support) Peter Ujfalusi
2015-04-09 9:35 ` [PATCH v5 1/8] dmaengine: of_dma: Support for DMA routers Peter Ujfalusi
2015-04-09 9:35 ` [PATCH v5 2/8] Documentation: devicetree: dma: Binding documentation for TI DMA crossbar Peter Ujfalusi
2015-04-09 9:35 ` [PATCH v5 3/8] dmaengine: Add driver for TI DMA crossbar on DRA7x Peter Ujfalusi
2015-05-04 5:38 ` Vinod Koul
2015-05-07 9:48 ` Peter Ujfalusi
2015-05-08 3:41 ` Vinod Koul
2015-05-08 7:05 ` Peter Ujfalusi
2015-05-08 9:03 ` Vinod Koul
2015-05-08 15:09 ` Tony Lindgren
2015-05-08 17:44 ` Peter Ujfalusi
2015-04-09 9:35 ` [PATCH v5 4/8] dmaengine: omap-dma: Use defines for dma channels and request count Peter Ujfalusi
2015-04-09 9:35 ` [PATCH v5 5/8] dmaengine: omap-dma: Take DMA request number from DT if it is available Peter Ujfalusi
2015-04-09 9:35 ` [PATCH v5 6/8] dmaengine: omap-dma: Remove mapping between virtual channels and requests Peter Ujfalusi
2015-04-09 9:35 ` [PATCH v5 7/8] dmaengine: omap-dma: Reduce the number of virtual channels Peter Ujfalusi
2015-04-09 9:35 ` [PATCH v5 8/8] ARM: DTS: dra7x: Integrate sDMA crossbar Peter Ujfalusi
2015-04-09 15:18 ` Tony Lindgren
2015-04-09 18:50 ` Peter Ujfalusi
2015-04-09 19:01 ` Tony Lindgren
2015-04-09 19:05 ` Peter Ujfalusi
2015-04-09 19:12 ` Tony Lindgren
2015-07-14 10:28 ` Tony Lindgren
2015-05-04 5:40 ` Vinod Koul
2015-04-22 7:38 ` Peter Ujfalusi [this message]
2015-05-09 11:44 ` [PATCH v5 0/8] dmaengine/dra7x: DMA router (crossbar support) Vinod Koul
2015-05-13 14:57 ` Peter Ujfalusi
2015-05-14 15:21 ` 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=55374FF3.1030003@ti.com \
--to=peter.ujfalusi@ti.com \
--cc=arnd@arndb.de \
--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=maxime.ripard@free-electrons.com \
--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).