From: Maxime Ripard <maxime.ripard@free-electrons.com>
To: Vinod Koul <vinod.koul@intel.com>
Cc: dmaengine@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Alexandre Belloni <alexandre.belloni@free-electrons.com>,
Ludovic Desroches <ludovic.desroches@atmel.com>,
Thomas Petazzoni <thomas@free-electrons.com>,
linux-kernel@vger.kernel.org,
linux-arm-kernel@lists.infradead.org,
Maxime Ripard <maxime.ripard@free-electrons.com>
Subject: [PATCH 0/2] dmaengine: hdmac: Implement interleaved transfers support
Date: Wed, 27 May 2015 16:01:51 +0200 [thread overview]
Message-ID: <1432735313-481-1-git-send-email-maxime.ripard@free-electrons.com> (raw)
Hi everyone,
This patchset implements the interleaved transfer capability found on
some AT91 SoCs.
The hardware actually support a somewhat similar mode called
picture-in-picture, that allows to transfer a squared portion of a
framebuffer.
That actually means that the interleaved transfer that this hardware
support will need to have the same size and ICGs across all its
chunks.
It has been tested on the SAMA5D36.
Let me know what you think!
Maxime
Maxime Ripard (2):
dmaengine: Move icg helpers to global header
dmaengine: hdmac: Implement interleaved transfers
drivers/dma/at_hdmac.c | 106 ++++++++++++++++++++++++++++++++++++++++++++
drivers/dma/at_hdmac_regs.h | 5 +++
drivers/dma/at_xdmac.c | 46 ++-----------------
include/linux/dmaengine.h | 27 +++++++++++
4 files changed, 142 insertions(+), 42 deletions(-)
--
2.4.1
next reply other threads:[~2015-05-27 14:05 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 14:01 Maxime Ripard [this message]
2015-05-27 14:01 ` [PATCH 1/2] dmaengine: Move icg helpers to global header Maxime Ripard
2015-06-01 8:14 ` Ludovic Desroches
2015-05-27 14:01 ` [PATCH 2/2] dmaengine: hdmac: Implement interleaved transfers Maxime Ripard
2015-06-01 8:32 ` Ludovic Desroches
2015-06-02 9:19 ` Maxime Ripard
2015-06-12 12:44 ` [PATCH 0/2] dmaengine: hdmac: Implement interleaved transfers support Vinod Koul
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=1432735313-481-1-git-send-email-maxime.ripard@free-electrons.com \
--to=maxime.ripard@free-electrons.com \
--cc=alexandre.belloni@free-electrons.com \
--cc=dmaengine@vger.kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ludovic.desroches@atmel.com \
--cc=nicolas.ferre@atmel.com \
--cc=thomas@free-electrons.com \
--cc=vinod.koul@intel.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
all inboxes | Powered by JetHome®