From: Guennadi Liakhovetski <g.liakhovetski@gmx.de>
To: linux-kernel@vger.kernel.org
Cc: linux-sh@vger.kernel.org, Magnus Damm <magnus.damm@gmail.com>,
Simon Horman <horms@verge.net.au>,
Vinod Koul <vinod.koul@intel.com>,
Laurent Pinchart <laurent.pinchart@ideasonboard.com>,
Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
Subject: [PATCH 0/8] ARM: shmobile: move DMAC configuration data in the driver
Date: Fri, 12 Jul 2013 13:43:50 +0000 [thread overview]
Message-ID: <1373636638-18496-1-git-send-email-g.liakhovetski@gmx.de> (raw)
Currently DMACs on sh-, r-mobile and r-car SoCs use platform data for
their configuration. This doesn't work well with DT. Adding the complete
DMAC configuration to DT wouldn't make sense either, because it would
produce duplication, it would be difficult to define future-safe bindings,
that wouldn't have to change with any future DMAC versions, and it is
unneeded, because all that configuration is SoC-specific, not board-
specific.
The best option is to move that configuration data to the driver, to be
used, depending on the device ID. Then this data can be re-used in DT-
and non-DT configurations.
This patch set extends the driver, adds example configuration data sets
for 2 SoCs. One of those SoCs already had DMAC support, so, it is switched
over. The other SoC didn't include support for DMAC yet, it is added in
this series too. Patches 1-3 are common for DT- and non-DT cases, patches
4 and 5 handle the "traditional" non-DT case, and patches 6-8 deal with DT.
The DMA part applies on top of my earlier shdma patch "DMA: shdma: support
the new CHCLR register layout" and other patches, already in -next. The
ARM part applies on top of today's renesas.git devel branch.
Cc: Guennadi Liakhovetski <g.liakhovetski+renesas@gmail.com>
Guennadi Liakhovetski (8):
DMA: shdma: add support for DMAC configuration data, supplied via
device ID
DMA: shdma: add r8a7740 DMAC data to the device ID table
DMA: shdma: add r8a73a4 DMAC data to the device ID table
ARM: shmobile: r8a73a4: add a DMAC platform device and clock for it
ARM: shmobile: r8a7740: switch DMAC controllers to using device ID
data
DMA: shdma: pass SoC-specific configuration to the driver via OF
matching
DMA: shdma: make multiplexer platform data optional
ARM: shmobile: r8a7740: add DT nodes and clock aliases for three DMAC
instances
Documentation/devicetree/bindings/dma/shdma.txt | 7 +-
arch/arm/boot/dts/r8a7740.dtsi | 61 +++++++++++++
arch/arm/mach-shmobile/clock-r8a73a4.c | 4 +-
arch/arm/mach-shmobile/clock-r8a7740.c | 9 ++-
arch/arm/mach-shmobile/include/mach/r8a73a4.h | 9 ++
arch/arm/mach-shmobile/setup-r8a73a4.c | 16 ++++
arch/arm/mach-shmobile/setup-r8a7740.c | 106 +----------------------
drivers/dma/sh/Kconfig | 8 ++
drivers/dma/sh/Makefile | 4 +
drivers/dma/sh/shdma-of.c | 3 -
drivers/dma/sh/shdma-r8a73a4.c | 75 ++++++++++++++++
drivers/dma/sh/shdma-r8a7740.c | 95 ++++++++++++++++++++
drivers/dma/sh/shdma.h | 14 +++
drivers/dma/sh/{shdma.c => shdmac.c} | 28 +++++-
14 files changed, 322 insertions(+), 117 deletions(-)
create mode 100644 drivers/dma/sh/shdma-r8a73a4.c
create mode 100644 drivers/dma/sh/shdma-r8a7740.c
rename drivers/dma/sh/{shdma.c => shdmac.c} (97%)
--
1.7.2.5
Thanks
Guennadi
---
Guennadi Liakhovetski, Ph.D.
Freelance Open-Source Software Developer
http://www.open-technology.de/
next reply other threads:[~2013-07-12 13:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-07-12 13:43 Guennadi Liakhovetski [this message]
2013-07-12 13:43 ` [PATCH 1/8] DMA: shdma: add support for DMAC configuration data, supplied via device ID Guennadi Liakhovetski
2013-07-12 13:43 ` [PATCH 2/8] DMA: shdma: add r8a7740 DMAC data to the device ID table Guennadi Liakhovetski
2013-07-12 13:43 ` [PATCH 3/8] DMA: shdma: add r8a73a4 " Guennadi Liakhovetski
2013-07-12 13:43 ` [PATCH 4/8] ARM: shmobile: r8a73a4: add a DMAC platform device and clock for it Guennadi Liakhovetski
2013-07-12 13:43 ` [PATCH 5/8] ARM: shmobile: r8a7740: switch DMAC controllers to using device ID data Guennadi Liakhovetski
2013-07-12 13:43 ` [PATCH 6/8] DMA: shdma: pass SoC-specific configuration to the driver via OF matching Guennadi Liakhovetski
2013-07-12 19:49 ` Sergei Shtylyov
2013-07-12 13:43 ` [PATCH 7/8] DMA: shdma: make multiplexer platform data optional Guennadi Liakhovetski
2013-07-12 13:43 ` [PATCH 8/8] ARM: shmobile: r8a7740: add DT nodes and clock aliases for three DMAC instances Guennadi Liakhovetski
2013-07-12 14:56 ` Sergei Shtylyov
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=1373636638-18496-1-git-send-email-g.liakhovetski@gmx.de \
--to=g.liakhovetski@gmx.de \
--cc=g.liakhovetski+renesas@gmail.com \
--cc=horms@verge.net.au \
--cc=laurent.pinchart@ideasonboard.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.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).