linux-kernel - [PATCH RFC 0/2] Prepare smooth PXA transition to dmaengine

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:	Sat, 14 Feb 2015 23:47:31 +0100
From:	Robert Jarzmik <robert.jarzmik@...e.fr>
To:	Vinod Koul <vinod.koul@...el.com>, Arnd Bergmann <arnd@...db.de>,
	Olof Johansson <olof@...om.net>,
	Daniel Mack <zonque@...il.com>,
	Haojian Zhuang <haojian.zhuang@...il.com>
Cc:	linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
	dmaengine@...r.kernel.org, Robert Jarzmik <robert.jarzmik@...e.fr>
Subject: [PATCH RFC 0/2] Prepare smooth PXA transition to dmaengine

This is the best I could think of to smoothly transition the PXA drivers to
dmaengine, driver by driver. The goal is to :
 - be able to port several drivers, but not _all_ of them at the same time
 - have both dmaengine and legacy dma code working in the same kernel
 - have dma chanels correctly split between both APIs

This was only compiled for now, I'll make some test shortly.

If anybody thinks of something smarter, please let me know.

Cheers.

--
Robert

Robert Jarzmik (2):
  dma: mmp_dma: add support for legacy transition
  ARM: pxa: transition to dmaengine phase 1

 arch/arm/Kconfig                     |  2 ++
 arch/arm/plat-pxa/dma.c              |  4 +++-
 arch/arm/plat-pxa/include/plat/dma.h |  1 +
 drivers/dma/mmp_pdma.c               | 26 ++++++++++++++++++++++++++
 4 files changed, 32 insertions(+), 1 deletion(-)

-- 
2.1.0

--
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/