linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 3/5] dmaengine: pxa: add pxa dmaengine driver
Date: Thu, 02 Apr 2015 11:06:32 +0200	[thread overview]
Message-ID: <87k2xuucfb.fsf@free.fr> (raw)
In-Reply-To: <1426977868-5414-4-git-send-email-robert.jarzmik@free.fr> (Robert Jarzmik's message of "Sat, 21 Mar 2015 23:44:26 +0100")

Robert Jarzmik <robert.jarzmik@free.fr> writes:

> This is a new driver for pxa SoCs, which is also compatible with the former
> mmp_pdma.

All right, I have a v2 for this patch, with a minor change for muxed interrupt
probe case (1 interrupt for all channels).

I'll release it this week. Did you have the time to have a look at the patch
serie Vinod ?

Cheers.

--
Robert

  reply	other threads:[~2015-04-02  9:06 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-03-21 22:44 [PATCH 0/5] Driver for pxa architectures Robert Jarzmik
2015-03-21 22:44 ` [PATCH 1/5] Documentation: dmaengine: pxa-dma design Robert Jarzmik
2015-03-21 22:44 ` [PATCH 2/5] MAINTAINERS: add pxa dma driver to pxa architecture Robert Jarzmik
2015-03-21 22:44 ` [PATCH 3/5] dmaengine: pxa: add pxa dmaengine driver Robert Jarzmik
2015-04-02  9:06   ` Robert Jarzmik [this message]
2015-04-02 10:46     ` Vinod Koul
2015-03-21 22:44 ` [PATCH 4/5] dmaengine: pxa_dma: add debug information Robert Jarzmik
2015-03-21 22:44 ` [PATCH 5/5] dmaengine: pxa_dma: add support for legacy transition Robert Jarzmik
2015-03-22  2:20 ` [PATCH 0/5] Driver for pxa architectures Arnd Bergmann
2015-03-23  9:21   ` Robert Jarzmik
2015-03-23 15:04     ` Arnd Bergmann
2015-03-23 20:33       ` Robert Jarzmik
2015-03-24  5:17         ` Arnd Bergmann

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=87k2xuucfb.fsf@free.fr \
    --to=robert.jarzmik@free.fr \
    --cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).