public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: vinod.koul@intel.com (Koul, Vinod)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH v2 0/5] ep93xx DMA patches
Date: Mon, 06 Jun 2011 12:09:40 +0530	[thread overview]
Message-ID: <1307342380.10976.79.camel@vkoul-udesk3> (raw)
In-Reply-To: <20110605081904.GA16018@acer>

On Sun, 2011-06-05 at 11:19 +0300, Mika Westerberg wrote:
> Vinod,
> 
> As this series has acks for all the subsystem maintainers, would it be ok for
> you to take the entire series via your tree? Or do you have any idea how to
> get it merged?
Please don't top post :(

I have applied this series to next including the asoc and spi changes,
if anyone has any objections please let me know

> 
> On Sun, May 29, 2011 at 01:10:01PM +0300, Mika Westerberg wrote:
> > This is an updated version of the ep93xx DMA patches. Previous version can be
> > found here: https://lkml.org/lkml/2011/5/22/86.
> > 
> > Changes to v1:
> >  * removed unnecessary header
> >  * corrected SPI driver documentation
> >  * DMA driver platform code is only compiled when CONFIG_EP93XX_DMA is
> >    enabled
> > 
> > I tried to put all the acks in place, hope I got them right.
> > 
> > There is a dependency between patch 1 and patch 4 which I'm not entirely sure
> > how to solve. Basically it is required that we have patch 1 applied before
> > patch 4 or merge conflict results.
> > 
> > Otherwise it shouldn't matter in which order the patches arrive to the
> > mainline.
> > 
> > Unless someone has a better idea, I suggest that these patches will go through
> > their respective subsystem trees. All the maintainers should be copied.
> > 
> > Thanks,
> > MW
> > 
> > Mika Westerberg (5):
> >   dmaengine: add ep93xx DMA support
> >   ep93xx: add dmaengine platform code
> >   ASoC: ep93xx: convert to use the DMA engine API
> >   ep93xx: remove the old M2P DMA code
> >   spi/ep93xx: add DMA support
> > 
> >  Documentation/spi/ep93xx_spi                   |   10 +
> >  arch/arm/mach-ep93xx/Makefile                  |    4 +-
> >  arch/arm/mach-ep93xx/core.c                    |    6 +-
> >  arch/arm/mach-ep93xx/dma-m2p.c                 |  411 -------
> >  arch/arm/mach-ep93xx/dma.c                     |  108 ++
> >  arch/arm/mach-ep93xx/include/mach/dma.h        |  190 ++---
> >  arch/arm/mach-ep93xx/include/mach/ep93xx_spi.h |    2 +
> >  drivers/dma/Kconfig                            |    7 +
> >  drivers/dma/Makefile                           |    1 +
> >  drivers/dma/ep93xx_dma.c                       | 1355 ++++++++++++++++++++++++
> >  drivers/spi/ep93xx_spi.c                       |  303 +++++-
> >  sound/soc/ep93xx/ep93xx-ac97.c                 |    4 +-
> >  sound/soc/ep93xx/ep93xx-i2s.c                  |    4 +-
> >  sound/soc/ep93xx/ep93xx-pcm.c                  |  137 ++--
> >  14 files changed, 1930 insertions(+), 612 deletions(-)
> >  delete mode 100644 arch/arm/mach-ep93xx/dma-m2p.c
> >  create mode 100644 arch/arm/mach-ep93xx/dma.c
> >  create mode 100644 drivers/dma/ep93xx_dma.c
> > 
> > -- 
> > 1.7.4.4
> --
> To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
> the body of a message to majordomo at vger.kernel.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
> Please read the FAQ at  http://www.tux.org/lkml/


-- 
~Vinod

  reply	other threads:[~2011-06-06  6:39 UTC|newest]

Thread overview: 36+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-29 10:10 [PATCH v2 0/5] ep93xx DMA patches Mika Westerberg
2011-05-29 10:10 ` [PATCH v2 1/5] dmaengine: add ep93xx DMA support Mika Westerberg
2011-11-15 15:02   ` Rafal Prylowski
2011-11-15 17:59     ` H Hartley Sweeten
2011-11-16  6:48       ` Mika Westerberg
2011-11-16  9:00       ` Rafal Prylowski
2011-11-16  6:55     ` Mika Westerberg
2011-11-16  8:31       ` Rafal Prylowski
2011-11-19 12:38         ` Mika Westerberg
2011-11-21  7:44           ` Rafal Prylowski
2011-11-21  8:01             ` Mika Westerberg
2011-11-21  8:32               ` Vinod Koul
2011-11-22  5:59                 ` Mika Westerberg
2011-11-23 10:47                   ` Vinod Koul
2011-11-21  8:54               ` Rafal Prylowski
2011-11-22  6:47                 ` Mika Westerberg
2011-11-22  8:45                   ` Rafal Prylowski
2011-05-29 10:10 ` [PATCH v2 2/5] ep93xx: add dmaengine platform code Mika Westerberg
2011-05-29 10:10 ` [PATCH v2 3/5] ASoC: ep93xx: convert to use the DMA engine API Mika Westerberg
2011-05-29 10:10 ` [PATCH v2 4/5] ep93xx: remove the old M2P DMA code Mika Westerberg
2011-05-29 10:10 ` [PATCH v2 5/5] spi/ep93xx: add DMA support Mika Westerberg
2011-06-03 20:44   ` Grant Likely
2011-06-07 17:14     ` Mika Westerberg
2011-06-07 18:45       ` Grant Likely
2011-06-07 19:06         ` Mika Westerberg
2011-06-07 19:18           ` Grant Likely
2011-06-07 19:29             ` Mika Westerberg
2011-06-07 19:40               ` Grant Likely
2011-06-08  3:58                 ` Koul, Vinod
2011-06-08 21:53                   ` Grant Likely
2011-06-09 16:42                     ` Koul, Vinod
2011-06-09 18:46                       ` Grant Likely
2011-06-09 19:15                         ` Mika Westerberg
2011-06-05  8:19 ` [PATCH v2 0/5] ep93xx DMA patches Mika Westerberg
2011-06-06  6:39   ` Koul, Vinod [this message]
2011-06-06 16:42     ` Mika Westerberg

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=1307342380.10976.79.camel@vkoul-udesk3 \
    --to=vinod.koul@intel.com \
    --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