linux-kernel - [PATCH 0/8] ARM: shmobile: move DMAC configuration data in the driver

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 12 Jul 2013 15:43:50 +0200
From:	Guennadi Liakhovetski <g.liakhovetski@....de>
To:	linux-kernel@...r.kernel.org
Cc:	linux-sh@...r.kernel.org, Magnus Damm <magnus.damm@...il.com>,
	Simon Horman <horms@...ge.net.au>,
	Vinod Koul <vinod.koul@...el.com>,
	Laurent Pinchart <laurent.pinchart@...asonboard.com>,
	Guennadi Liakhovetski <g.liakhovetski+renesas@...il.com>
Subject: [PATCH 0/8] ARM: shmobile: move DMAC configuration data in the driver

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@...il.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/
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/