From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [Patch v3 2/2] dmaengine: qcom_bam_dma: Add device tree binding
Date: Tue, 28 Jan 2014 13:01:54 +0000 [thread overview]
Message-ID: <20140128130153.GI15937@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <4916428.f0GtxdkWKj@wuerfel>
On Tue, Jan 28, 2014 at 01:05:10PM +0100, Arnd Bergmann wrote:
> Ok, thanks for clearing up my mistake. However, the argument remains:
> the direction doesn't need to be in the DT DMA descriptor since it
> gets set by software anyway.
Yes - for full-duplex, it's implied, since you have one DMA request
(and therefore virtual channel) for memory-to-device and another for
device-to-memory.
--
FTTC broadband for 0.8mile line: 5.8Mbps down 500kbps up. Estimation
in database were 13.1 to 19Mbit for a good line, about 7.5+ for a bad.
Estimate before purchase was "up to 13.2Mbit".
next prev parent reply other threads:[~2014-01-28 13:01 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-01-28 6:27 [Patch v3 0/2] Add Qualcomm BAM dmaengine driver Andy Gross
2014-01-28 6:27 ` [Patch v3 1/2] dmaengine: add Qualcomm BAM dma driver Andy Gross
2014-01-28 6:27 ` [Patch v3 2/2] dmaengine: qcom_bam_dma: Add device tree binding Andy Gross
2014-01-28 9:05 ` Lars-Peter Clausen
2014-01-28 9:16 ` Arnd Bergmann
2014-01-28 11:17 ` Russell King - ARM Linux
2014-01-28 11:32 ` Vinod Koul
2014-01-28 12:05 ` Arnd Bergmann
2014-01-28 12:08 ` Arnd Bergmann
2014-01-28 12:16 ` Russell King - ARM Linux
2014-01-29 15:05 ` Arnd Bergmann
2014-01-28 13:01 ` Russell King - ARM Linux [this message]
2014-01-28 19:50 ` Andy Gross
2014-01-30 6:23 ` Andy Gross
2014-01-28 19:47 ` Andy Gross
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=20140128130153.GI15937@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--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).