From: Dan Williams <dan.j.williams@intel.com>
To: Linus Torvalds <torvalds@linux-foundation.org>,
Andrew Morton <akpm@linux-foundation.org>
Cc: Zhang Wei <wei.zhang@freescale.com>,
Saeed Bishara <saeed@marvell.com>,
Maciej Sosnowski <maciej.sosnowski@intel.com>,
Haavard Skinnemoen <hskinnemoen@atmel.com>,
linux-kernel <linux-kernel@vger.kernel.org>
Subject: [git pull] async-tx/dmaengine update for 2.6.27
Date: Thu, 17 Jul 2008 16:21:01 -0700 [thread overview]
Message-ID: <1216336861.18579.32.camel@dwillia2-linux.ch.intel.com> (raw)
Linus, please pull from:
git://git.kernel.org/pub/scm/linux/kernel/git/djbw/async_tx.git next
to receive:
Dan Williams (4):
async_tx: fix async_memset compile error
dmaengine: remove arch dependency from DMADEVICES
dmaengine: track the number of clients using a channel
dmaengine: add DMA_COMPL_SKIP_{SRC,DEST}_UNMAP flags to control dma unmap
Haavard Skinnemoen (5):
dmaengine: Couple DMA channels to their physical DMA device
dmatest: Simple DMA memcpy test client
dmaengine: Add dma_client parameter to device_alloc_chan_resources
dmaengine: Add slave DMA interface
dmaengine: Driver for the Synopsys DesignWare DMA controller
Kay Sievers (1):
iop-adma: fix platform driver hotplug/coldplug
Li Yang (1):
fsldma: fix incorrect exit path for initialization
Saeed Bishara (1):
dmaengine: DMA engine driver for Marvell XOR engine
arch/avr32/mach-at32ap/at32ap700x.c | 27 +-
crypto/async_tx/async_memset.c | 2 +-
drivers/dma/Kconfig | 37 +-
drivers/dma/Makefile | 3 +
drivers/dma/dmaengine.c | 35 +-
drivers/dma/dmatest.c | 444 +++++++++
drivers/dma/dw_dmac.c | 1122 +++++++++++++++++++++++
drivers/dma/dw_dmac_regs.h | 225 +++++
drivers/dma/fsldma.c | 38 +-
drivers/dma/ioat_dma.c | 53 +-
drivers/dma/iop-adma.c | 38 +-
drivers/dma/mv_xor.c | 1375 ++++++++++++++++++++++++++++
drivers/dma/mv_xor.h | 183 ++++
include/asm-arm/plat-orion/mv_xor.h | 28 +
include/asm-avr32/arch-at32ap/at32ap700x.h | 16 +
include/linux/dmaengine.h | 61 ++-
include/linux/dw_dmac.h | 62 ++
17 files changed, 3662 insertions(+), 87 deletions(-)
create mode 100644 drivers/dma/dmatest.c
create mode 100644 drivers/dma/dw_dmac.c
create mode 100644 drivers/dma/dw_dmac_regs.h
create mode 100644 drivers/dma/mv_xor.c
create mode 100644 drivers/dma/mv_xor.h
create mode 100644 include/asm-arm/plat-orion/mv_xor.h
create mode 100644 include/linux/dw_dmac.h
This update brings two new drivers, an expansion of the dmaengine
infrastructure to enable device-to-memory dma, as well as a mechanism
for exclusive client-channel associations. Also notable for developers
is the addition of the dmatest client for dmaengine driver validation.
One api extension was made to allow intelligent clients more control
over dma-unmapping. There is a follow on patch brewing to use this
capability to fix a case where xor buffers are unmapped too early. It
is not an urgent concern since the only xor offload engine drivers in
mainline are for configurations where dma-unmap is a nop.
Regards,
Dan
reply other threads:[~2008-07-17 23:21 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=1216336861.18579.32.camel@dwillia2-linux.ch.intel.com \
--to=dan.j.williams@intel.com \
--cc=akpm@linux-foundation.org \
--cc=hskinnemoen@atmel.com \
--cc=linux-kernel@vger.kernel.org \
--cc=maciej.sosnowski@intel.com \
--cc=saeed@marvell.com \
--cc=torvalds@linux-foundation.org \
--cc=wei.zhang@freescale.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
Powered by JetHome