From: Jamie Iles <jamie@jamieiles.com>
To: linux-kernel@vger.kernel.org
Cc: Jamie Iles <jamie@jamieiles.com>
Subject: [PATCH repost 0/4] dmaengine/dw_dmac: enhancements to allow use
Date: Fri, 21 Jan 2011 14:11:51 +0000 [thread overview]
Message-ID: <1295619115-18420-1-git-send-email-jamie@jamieiles.com> (raw)
This is a repost of the patch series previously posted back in November
last year to allow the DW_DMAC driver to be used on architectures other
than AV32 (there is still a dependency on AVR32 but I'll create a follow
up patch for this once we have a user in tree).
Jamie Iles (4):
dmaengine/dw_dmac: don't scan descriptors if no xfers in progress
dmaengine/dw_dmac: allow src/dst masters to be configured at runtime
dmaengine/dw_dmac: provide a mechanism to indicate private devices
avr32: at32ap700x: specify DMA src and dst masters
arch/avr32/mach-at32ap/at32ap700x.c | 6 +++++
drivers/dma/dw_dmac.c | 36 +++++++++++++++++++++-------------
include/linux/dw_dmac.h | 5 ++++
3 files changed, 33 insertions(+), 14 deletions(-)
--
1.7.3.4
next reply other threads:[~2011-01-21 14:12 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-01-21 14:11 Jamie Iles [this message]
2011-01-21 14:11 ` [PATCH repost 1/4] dmaengine/dw_dmac: don't scan descriptors if no xfers in progress Jamie Iles
2011-01-21 14:11 ` [PATCH repost 2/4] dmaengine/dw_dmac: allow src/dst masters to be configured at runtime Jamie Iles
2011-01-24 14:54 ` Hans-Christian Egtvedt
2011-01-21 14:11 ` [PATCH repost 3/4] dmaengine/dw_dmac: provide a mechanism to indicate private devices Jamie Iles
2011-01-21 14:11 ` [PATCH repost 4/4] avr32: at32ap700x: specify DMA src and dst masters Jamie Iles
2011-01-24 14:59 ` Hans-Christian Egtvedt
2011-01-30 6:33 ` Dan Williams
2011-02-04 11:06 ` Jamie Iles
2011-02-21 13:45 ` Hans-Christian Egtvedt
2011-02-21 14:45 ` Jamie Iles
2011-03-15 14:56 ` Jamie Iles
2011-03-16 2:08 ` Koul, Vinod
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=1295619115-18420-1-git-send-email-jamie@jamieiles.com \
--to=jamie@jamieiles.com \
--cc=linux-kernel@vger.kernel.org \
/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
all inboxes | Powered by JetHome®