linux-spi.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Linus WALLEIJ <linus.walleij@stericsson.com>
Cc: Russell King <linux@arm.linux.org.uk>,
	"spi-devel-general@lists.sourceforge.net"
	<spi-devel-general@lists.sourceforge.net>,
	"linux-mmc@vger.kernel.org" <linux-mmc@vger.kernel.org>,
	STEricsson_nomadik_linux <STEricsson_nomadik_linux@list.st.com>,
	Dan Williams <dan.j.williams@intel.com>,
	"linux-arm-kernel@lists.infradead.org"
	<linux-arm-kernel@lists.infradead.org>
Subject: Re: [PATCH 0/5] ARM: PrimeCell DMA patches v4
Date: Thu, 8 Apr 2010 00:12:57 -0600	[thread overview]
Message-ID: <n2ifa686aa41004072312ob606cc7fofbfa698da16cdba@mail.gmail.com> (raw)
In-Reply-To: <CEE6BB42CAD6E947908279175AF8470A039B48CC@EXDCVYMBSTM006.EQ1STM.local>

On Tue, Mar 30, 2010 at 3:57 AM, Linus WALLEIJ
<linus.walleij@stericsson.com> wrote:
> [Self]
>
>> This is a fourth iteration of the PrimeCell DMA API on top of the
>> generic DMA devices (sibling to the DMA engine). It's based on
>> the suggestion from Russell to try and define a specific extension
>> subset for DMA devices.
>
> Russell & Grant can you give some hint on the direction you
> see for this patch set?
>
> The problem we're facing is that next I will start adding DMA
> support for the U8500 and the MMCI derivate found in that platform
> doesn't *have* a PIO IRQ, which means the system cannot even
> boot without some solid DMA framework in place. (It is currently
> unbootable from the released kernels.)
>
> So unless there is some outstanding issue with this approach
> we pretty much need this now to keep working on mainlining
> the U8500.
>
> I would very much like to have the DMA patches for PrimeCell
> support pushed through Dan's tree, but that requires your ACKs
> of course, and it will inevitably collide with other PrimeCell
> patches for the next merge window (many submitted by myself
> admittedly).
>
> I can feed all the PrimeCell stuff to Dan if all agree that this
> is a good approach. Another approach is to apply the latest
> patches from Dan's tree to ARM and SPI alike and then feed
> the PrimeCell stuff through the ARM tree.

I have no objections to the SPI driver getting merged via Dan's tree.

g.

      reply	other threads:[~2010-04-08  6:12 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-03-29 23:35 [PATCH 0/5] ARM: PrimeCell DMA patches v4 Linus Walleij
2010-03-30  9:57 ` Linus WALLEIJ
2010-04-08  6:12   ` Grant Likely [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=n2ifa686aa41004072312ob606cc7fofbfa698da16cdba@mail.gmail.com \
    --to=grant.likely@secretlab.ca \
    --cc=STEricsson_nomadik_linux@list.st.com \
    --cc=dan.j.williams@intel.com \
    --cc=linus.walleij@stericsson.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    --cc=spi-devel-general@lists.sourceforge.net \
    /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).