From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Dan Williams <dan.j.williams@intel.com>
Cc: Linus Walleij <linus.ml.walleij@gmail.com>,
Linus WALLEIJ <linus.walleij@stericsson.com>,
"akpm@linux-foundation.org" <akpm@linux-foundation.org>,
Grant Likely <grant.likely@secretlab.ca>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
STEricsson_nomadik_linux <STEricsson_nomadik_linux@list.st.com>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 00/11] ARM: PrimeCell DMA Interface v5
Date: Sat, 1 May 2010 23:44:29 +0100 [thread overview]
Message-ID: <20100501224429.GA17693@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <g2qe9c3a7c21005011500l11511d43i12d971775b139c3b@mail.gmail.com>
On Sat, May 01, 2010 at 03:00:09PM -0700, Dan Williams wrote:
> Just to clarify are you nak'ing these patches for upstream inclusion
> until this testing occurs? Or do we just need a !ARCH_VERSATILE
> somewhere to allow any incompatibilities to be worked out later
> in-tree?
What I don't want to do is to get into the situation where we throw
this patchset into the kernel and then find that we have to invent a
whole new implementation in the various primecell drivers to support
the Versatile hardware.
Versatile has some MUXing on three of the DMA signals, so (eg) we
really don't want UARTs claiming DMAs just because they're in existence
and not in use - that would prevent DMAs from being used for (eg) AACI
or MMC.
The alternative is that we could just take the attitude that Versatile/
Realview will never have DMA support implemented, but that seems rather
silly, as they've tended to be the first platforms I get new CPU
architectures for. (This is why DMA coherency stuff on new architectures
tends to be left for others to do...)
next prev parent reply other threads:[~2010-05-01 22:45 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-04-07 23:12 [PATCH 00/11] ARM: PrimeCell DMA Interface v5 Linus Walleij
2010-04-07 23:45 ` Dan Williams
2010-04-08 6:35 ` Linus WALLEIJ
2010-04-11 14:13 ` Linus Walleij
2010-04-12 19:23 ` Russell King - ARM Linux
2010-04-15 1:15 ` Dan Williams
2010-04-17 4:58 ` Linus Walleij
2010-04-22 11:00 ` Russell King - ARM Linux
2010-04-30 18:30 ` Linus Walleij
2010-05-01 22:00 ` Dan Williams
2010-05-01 22:27 ` Linus Walleij
2010-05-01 22:44 ` Russell King - ARM Linux [this message]
2010-05-01 23:04 ` Linus Walleij
2010-05-01 23:28 ` Russell King - ARM Linux
2010-05-02 0:21 ` Linus Walleij
2010-05-02 8:18 ` Russell King - ARM Linux
2010-05-04 13:05 ` Linus WALLEIJ
2010-05-01 23:28 ` Dan Williams
2010-05-01 23:48 ` Linus Walleij
2010-05-01 23:25 ` Dan Williams
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=20100501224429.GA17693@n2100.arm.linux.org.uk \
--to=linux@arm.linux.org.uk \
--cc=STEricsson_nomadik_linux@list.st.com \
--cc=akpm@linux-foundation.org \
--cc=dan.j.williams@intel.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.ml.walleij@gmail.com \
--cc=linus.walleij@stericsson.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-mmc@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 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).