linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: linux@arm.linux.org.uk (Russell King - ARM Linux)
To: linux-arm-kernel@lists.infradead.org
Subject: [RFC 00/12] OMAP DMA engine conversion
Date: Tue, 15 May 2012 08:41:41 +0100	[thread overview]
Message-ID: <20120515074141.GA16276@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <1337055564.16185.5356.camel@vkoul-udesk3>

On Tue, May 15, 2012 at 09:49:24AM +0530, Vinod Koul wrote:
> On Mon, 2012-04-23 at 17:04 +0100, Russell King - ARM Linux wrote:
> > For the full text, please see 
> > 
> > http://lists.arm.linux.org.uk/lurker/message/20120418.100954.7fa7acf8.en.html
> > 
> > This version contains updates for some of the comments received from the
> > previous round, and adds the OMAP1/2 MMC and SPI drivers to the conversion.
> > 
> > I've also added a note to feature-removal noting that the existing APIs
> > will be removed around 2013 - I'm planning January for that at the
> > moment.  Having drivers around which are unconverted blocks further work
> > on the DMA engine conversion, so it's actually important that we get
> > as many drivers converted as soon as possible.
> > 
> > Anything which isn't converted will probably have its DMA code removed,
> > or if that results in the driver not being usable, the driver itself
> > will be removed.
> > 
> > This series is still in RFC mode...
> Hi Russell,
> 
> What is the state of this series, would be good to have this merged in
> upcoming merge window.

It's not ready for merging.  While it allows some of the OMAP drivers
to be converted, there's others which need changes to omap-dma.c.

So, I'm _not_ planning to see this in for the upcoming merge window.

  reply	other threads:[~2012-05-15  7:41 UTC|newest]

Thread overview: 37+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-04-23 16:04 [RFC 00/12] OMAP DMA engine conversion Russell King - ARM Linux
2012-04-23 16:04 ` [PATCH 01/12] ARM: OMAP: fix DMA vs memory ordering Russell King
2012-04-23 16:04 ` [PATCH 02/12] dmaengine: split out virtual channel DMA support from sa11x0 driver Russell King
2012-04-27 18:57   ` Linus Walleij
2012-04-23 16:05 ` [PATCH 03/12] dmaengine: add OMAP DMA engine driver Russell King
2012-04-23 16:05 ` [PATCH 04/12] mmc: omap_hsmmc: release correct resource Russell King
2012-04-23 16:05 ` [PATCH 05/12] mmc: omap_hsmmc: add DMA engine support Russell King
2012-04-24  0:16   ` Tony Lindgren
2012-04-27 19:00   ` Linus Walleij
2012-04-27 19:03     ` Russell King - ARM Linux
2012-04-27 20:34       ` Linus Walleij
2012-04-23 16:06 ` [PATCH 06/12] mmc: omap_hsmmc: remove private DMA API implementation Russell King
2012-04-24  0:17   ` Tony Lindgren
2012-04-24 21:51   ` Grazvydas Ignotas
2012-04-24 22:05     ` Russell King - ARM Linux
2012-04-23 16:06 ` [PATCH 07/12] mmc: omap: add DMA engine support Russell King
2012-04-24  0:13   ` Tony Lindgren
2012-04-28 16:37     ` Russell King - ARM Linux
2012-04-30 15:59       ` Tony Lindgren
2012-04-23 16:06 ` [PATCH 08/12] mmc: omap: remove private DMA API implementation Russell King
2012-04-23 16:07 ` [PATCH 09/12] ARM: omap: remove mmc platform data dma_mask and initialization Russell King
2012-04-23 16:07 ` [PATCH 10/12] spi: omap2-mcspi: add DMA engine support Russell King
2012-04-27 17:20   ` Grant Likely
2012-04-23 16:07 ` [PATCH 11/12] spi: omap2-mcspi: remove private DMA API implementation Russell King
2012-04-23 16:08 ` [PATCH 12/12] Add removal of old OMAP private DMA implementation to feature removal Russell King
2012-04-24  0:17   ` Tony Lindgren
2012-04-27 20:19   ` Linus Walleij
2012-04-24 10:38 ` [RFC 00/12] OMAP DMA engine conversion Russell King - ARM Linux
2012-04-24 16:51   ` Tony Lindgren
2012-04-24 22:47     ` Grazvydas Ignotas
2012-04-24 23:29       ` Russell King - ARM Linux
2012-04-24 23:59         ` Grazvydas Ignotas
2012-05-09 12:25 ` T Krishnamoorthy, Balaji
2012-05-15  4:19 ` Vinod Koul
2012-05-15  7:41   ` Russell King - ARM Linux [this message]
2012-05-15  8:59     ` Vinod Koul
2012-05-15  9:32       ` Russell King - ARM Linux

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=20120515074141.GA16276@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).