From: Gene Anderson <gwa@cox.net>
To: linux-kernel@vger.kernel.org
Subject: Re: [PATCHv5] dmaengine: Add support for BCM2835
Date: Tue, 24 Dec 2013 14:31:31 +0000 (UTC) [thread overview]
Message-ID: <loom.20131224T151818-230@post.gmane.org> (raw)
In-Reply-To: 20131115175155.GQ16735@n2100.arm.linux.org.uk
Group:
This is a request to augment with comments the
DREQ explanation in the Broadcom BCM2835
pdf on page 61 regarding DMA peripheral
mapping. Specifically, how to identify a pin on the 26
pin
header to use for DMA reads. More specifically,
if a clock signal,
like GPCLK0 is output to the peripheral device
(like an A/D converter) how we specify PERMAP in the
DMA TI register. Your users would be infinitely grateful.
thank you,
prev parent reply other threads:[~2013-12-24 14:35 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-11-15 16:28 [PATCHv5] dmaengine: Add support for BCM2835 Florian Meier
2013-11-15 16:28 ` Florian Meier
2013-11-15 16:28 ` Florian Meier
[not found] ` <52864BBC.7000506-oZ8rN/sblLk@public.gmane.org>
2013-11-15 17:03 ` Joe Perches
2013-11-15 17:03 ` Joe Perches
2013-11-15 17:03 ` Joe Perches
2013-11-15 17:43 ` Russell King - ARM Linux
2013-11-15 17:43 ` Russell King - ARM Linux
2013-11-15 17:43 ` Russell King - ARM Linux
2013-11-15 18:20 ` Joe Perches
2013-11-15 18:20 ` Joe Perches
2013-11-15 18:20 ` Joe Perches
2013-11-15 17:43 ` Shevchenko, Andriy
2013-11-15 17:43 ` Shevchenko, Andriy
2013-11-15 17:51 ` Russell King - ARM Linux
2013-11-15 17:51 ` Russell King - ARM Linux
[not found] ` <CAHp75Vf3CJNgSiSjoZ6dYjRRHWN4bTpMxRTLG37+wwtEsQbq4g@mail.gmail.com>
2013-11-16 9:39 ` Andy Shevchenko
2013-11-16 9:39 ` Andy Shevchenko
2013-11-16 11:27 ` Mark Brown
2013-11-16 11:27 ` Mark Brown
2013-11-16 11:41 ` Russell King - ARM Linux
2013-11-16 11:41 ` Russell King - ARM Linux
2013-11-16 12:22 ` Mark Brown
2013-11-16 12:22 ` Mark Brown
2013-12-24 14:31 ` Gene Anderson [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=loom.20131224T151818-230@post.gmane.org \
--to=gwa@cox.net \
--cc=linux-kernel@vger.kernel.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.