All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mika Westerberg <mika.westerberg@iki.fi>
To: Linus Walleij <linus.walleij@linaro.org>
Cc: linux-arm-kernel@lists.infradead.org,
	Vinod Koul <vinod.koul@intel.com>,
	linux-kernel@vger.kernel.org, hsweeten@visionengravers.com,
	ryan@bluewatersys.com, Dan Williams <dan.j.williams@intel.com>,
	Grant Likely <grant.likely@secretlab.ca>,
	spi mailing list <spi-devel-general@lists.sourceforge.net>
Subject: Re: [PATCH 1/5] dmaengine: add ep93xx DMA support
Date: Thu, 26 May 2011 21:38:01 +0300	[thread overview]
Message-ID: <20110526183800.GE2957@acer> (raw)
In-Reply-To: <BANLkTikzrXRmdnv_v_nmJw7Nvsr6TY-5RQ@mail.gmail.com>

On Thu, May 26, 2011 at 09:15:25AM +0200, Linus Walleij wrote:
> On Thu, May 26, 2011 at 6:33 AM, Mika Westerberg <mika.westerberg@iki.fi> wrote:
> 
> > Do you think that we can go forward with this patch series if I drop the last
> > patch (spi/ep93xx: add DMA support)? This way we will have dmaengine
> > implementation in place, whatever SPI driver we choose to use with ep93xx.
> 
> Yes and you don't have to drop any DMA support for the existing driver
> for me alone, now that it's in the tree it should be maintained. I only
> wanted to raise the issue of code duplication, not block any patches.

Ok, so I'll keep the last patch for now.

BTW: if we get amba-pl022 driver to work with ep93xx, do you have any ideas
how to proceed from there? I mean, should we convert existing users to use
that driver instead and finally remove the ep93xx_spi driver?

WARNING: multiple messages have this Message-ID (diff)
From: mika.westerberg@iki.fi (Mika Westerberg)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 1/5] dmaengine: add ep93xx DMA support
Date: Thu, 26 May 2011 21:38:01 +0300	[thread overview]
Message-ID: <20110526183800.GE2957@acer> (raw)
In-Reply-To: <BANLkTikzrXRmdnv_v_nmJw7Nvsr6TY-5RQ@mail.gmail.com>

On Thu, May 26, 2011 at 09:15:25AM +0200, Linus Walleij wrote:
> On Thu, May 26, 2011 at 6:33 AM, Mika Westerberg <mika.westerberg@iki.fi> wrote:
> 
> > Do you think that we can go forward with this patch series if I drop the last
> > patch (spi/ep93xx: add DMA support)? This way we will have dmaengine
> > implementation in place, whatever SPI driver we choose to use with ep93xx.
> 
> Yes and you don't have to drop any DMA support for the existing driver
> for me alone, now that it's in the tree it should be maintained. I only
> wanted to raise the issue of code duplication, not block any patches.

Ok, so I'll keep the last patch for now.

BTW: if we get amba-pl022 driver to work with ep93xx, do you have any ideas
how to proceed from there? I mean, should we convert existing users to use
that driver instead and finally remove the ep93xx_spi driver?

  reply	other threads:[~2011-05-26 18:38 UTC|newest]

Thread overview: 68+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-05-22 17:03 [PATCH 0/5] ep93xx DMA patches Mika Westerberg
2011-05-22 17:03 ` Mika Westerberg
2011-05-22 17:03 ` [PATCH 1/5] dmaengine: add ep93xx DMA support Mika Westerberg
2011-05-22 17:03   ` Mika Westerberg
2011-05-25  8:00   ` Koul, Vinod
2011-05-25  8:00     ` Koul, Vinod
2011-05-25 19:00     ` Mika Westerberg
2011-05-25 19:00       ` Mika Westerberg
2011-05-26  4:38       ` Koul, Vinod
2011-05-26  4:38         ` Koul, Vinod
2011-05-26 18:15         ` Mika Westerberg
2011-05-26 18:15           ` Mika Westerberg
2011-05-26 18:42           ` H Hartley Sweeten
2011-05-26 18:42             ` H Hartley Sweeten
2011-05-25  8:39   ` Linus Walleij
2011-05-25  8:39     ` Linus Walleij
2011-05-25  8:19     ` Koul, Vinod
2011-05-25  8:19       ` Koul, Vinod
2011-05-25  9:09       ` Linus Walleij
2011-05-25  9:09         ` Linus Walleij
2011-05-25 19:54     ` Mika Westerberg
2011-05-25 19:54       ` Mika Westerberg
2011-05-25 20:47       ` Linus Walleij
2011-05-25 20:47         ` Linus Walleij
2011-05-26  4:33         ` Mika Westerberg
2011-05-26  4:33           ` Mika Westerberg
2011-05-26  5:26           ` Ryan Mallon
2011-05-26  5:26             ` Ryan Mallon
2011-05-26  7:15           ` Linus Walleij
2011-05-26  7:15             ` Linus Walleij
2011-05-26 18:38             ` Mika Westerberg [this message]
2011-05-26 18:38               ` Mika Westerberg
2011-05-26 18:48               ` H Hartley Sweeten
2011-05-26 18:48                 ` H Hartley Sweeten
2011-05-26 21:53                 ` Russell King - ARM Linux
2011-05-26 21:53                   ` Russell King - ARM Linux
2011-05-26 22:58                 ` Linus Walleij
2011-05-26 22:58                   ` Linus Walleij
2011-05-27  1:38   ` H Hartley Sweeten
2011-05-27  1:38     ` H Hartley Sweeten
2011-05-28 10:33     ` Mika Westerberg
2011-05-28 10:33       ` Mika Westerberg
2011-05-22 17:03 ` [PATCH 2/5] ep93xx: add dmaengine platform code Mika Westerberg
2011-05-22 17:03   ` Mika Westerberg
2011-05-27  1:44   ` H Hartley Sweeten
2011-05-27  1:44     ` H Hartley Sweeten
2011-05-22 17:03 ` [PATCH 3/5] ASoC: ep93xx: convert to use the DMA engine API Mika Westerberg
2011-05-22 17:03   ` Mika Westerberg
2011-05-23  5:11   ` Mark Brown
2011-05-23  5:11     ` Mark Brown
2011-05-23  9:38     ` Liam Girdwood
2011-05-23  9:38       ` Liam Girdwood
2011-05-27  1:43   ` H Hartley Sweeten
2011-05-27  1:43     ` H Hartley Sweeten
2011-05-22 17:03 ` [PATCH 4/5] ep93xx: remove the old M2P DMA code Mika Westerberg
2011-05-22 17:03   ` Mika Westerberg
2011-05-27  1:42   ` H Hartley Sweeten
2011-05-27  1:42     ` H Hartley Sweeten
2011-05-22 17:03 ` [PATCH 5/5] spi/ep93xx: add DMA support Mika Westerberg
2011-05-22 17:03   ` Mika Westerberg
2011-05-27  1:47   ` H Hartley Sweeten
2011-05-27  1:47     ` H Hartley Sweeten
2011-05-23 17:34 ` [PATCH 0/5] ep93xx DMA patches H Hartley Sweeten
2011-05-23 17:34   ` H Hartley Sweeten
2011-05-23 20:10 ` Ryan Mallon
2011-05-23 20:10   ` Ryan Mallon
2011-05-24 14:42   ` Mika Westerberg
2011-05-24 14: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=20110526183800.GE2957@acer \
    --to=mika.westerberg@iki.fi \
    --cc=dan.j.williams@intel.com \
    --cc=grant.likely@secretlab.ca \
    --cc=hsweeten@visionengravers.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=ryan@bluewatersys.com \
    --cc=spi-devel-general@lists.sourceforge.net \
    --cc=vinod.koul@intel.com \
    /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.