From: ludovic.desroches@atmel.com (Ludovic Desroches)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/4] dmaengine: at_xdmac: several improvements
Date: Mon, 19 Jan 2015 11:45:01 +0100 [thread overview]
Message-ID: <20150119104501.GD19014@odux.rfo.atmel.com> (raw)
In-Reply-To: <1418380615-12171-1-git-send-email-ludovic.desroches@atmel.com>
Hi Vinod,
Any issue with this patch series?
Regards
Ludovic
On Fri, Dec 12, 2014 at 11:36:51AM +0100, Ludovic Desroches wrote:
> Hi,
>
> This series is based on vkoul/slave-dma/topic/slave_caps_device_control_fix
> branch.
>
> Changes from v1:
> - put save_cc field addition in a single patch
> - update commit log of patch 3/4
> - remove AT_XDMAC_CUR_CFG since it is no more used
>
> Cyrille Pitchen (1):
> dmaengine: at_xdmac: wait for in-progress transaction to complete
> after pausing a channel
>
> Ludovic Desroches (3):
> dmaengine: at_xdmac: introduce save_cc field
> dmaengine: at_xdmac: simplify channel configuration stuff
> dmaengine: at_xdmac: allow muliple dwidths when doing slave transfers
>
> drivers/dma/at_xdmac.c | 60 ++++++++++++++++++++++++++------------------------
> 1 file changed, 31 insertions(+), 29 deletions(-)
>
> --
> 2.0.3
>
prev parent reply other threads:[~2015-01-19 10:45 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-12 10:36 [PATCH v2 0/4] dmaengine: at_xdmac: several improvements Ludovic Desroches
2014-12-12 10:36 ` [PATCH v2 1/4] dmaengine: at_xdmac: wait for in-progress transaction to complete after pausing a channel Ludovic Desroches
2014-12-12 10:36 ` [PATCH v2 2/4] dmaengine: at_xdmac: introduce save_cc field Ludovic Desroches
2014-12-12 10:36 ` [PATCH v2 3/4] dmaengine: at_xdmac: simplify channel configuration stuff Ludovic Desroches
2014-12-12 10:36 ` [PATCH v2 4/4] dmaengine: at_xdmac: allow muliple dwidths when doing slave transfers Ludovic Desroches
2015-01-19 10:45 ` Ludovic Desroches [this message]
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=20150119104501.GD19014@odux.rfo.atmel.com \
--to=ludovic.desroches@atmel.com \
--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).