From: maxime.ripard@free-electrons.com (Maxime Ripard)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 2/2] dmaengine: hdmac: Implement interleaved transfers
Date: Tue, 2 Jun 2015 11:19:51 +0200 [thread overview]
Message-ID: <20150602091951.GV23777@lukather> (raw)
In-Reply-To: <20150601083216.GH25118@odux.rfo.atmel.com>
Hi,
On Mon, Jun 01, 2015 at 10:32:16AM +0200, Ludovic Desroches wrote:
> > channel_writel(atchan, CTRLA, 0);
> > channel_writel(atchan, CTRLB, 0);
> > channel_writel(atchan, DSCR, first->txd.phys);
> > + channel_writel(atchan, SPIP, ATC_SPIP_HOLE(first->src_hole) |
> > + ATC_SPIP_BOUNDARY(first->boundary));
> > + channel_writel(atchan, DPIP, ATC_DPIP_HOLE(first->dst_hole) |
> > + ATC_DPIP_BOUNDARY(first->boundary));
>
> Can't we get a trivial condition to perform these two writes only if
> needed?
Is that really needed?
My understanding is that the hardware will only take this into account
if we set the ATC_SRC_PIP and ATC_DST_PIP bits anyway, so the check is
already there.
Maxime
--
Maxime Ripard, Free Electrons
Embedded Linux, Kernel and Android engineering
http://free-electrons.com
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 819 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20150602/1f1e61c4/attachment.sig>
next prev parent reply other threads:[~2015-06-02 9:19 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-27 14:01 [PATCH 0/2] dmaengine: hdmac: Implement interleaved transfers support Maxime Ripard
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 [this message]
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=20150602091951.GV23777@lukather \
--to=maxime.ripard@free-electrons.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).