All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tony Lindgren <tony@atomide.com>
To: Russell King - ARM Linux <linux@arm.linux.org.uk>
Cc: linux-arm-kernel@lists.infradead.org, linux-omap@vger.kernel.org,
	linux-mmc@vger.kernel.org,
	Jarkko Lavinen <jarkko.lavinen@nokia.com>,
	Chris Ball <cjb@laptop.org>
Subject: Re: [PATCH 07/12] mmc: omap: add DMA engine support
Date: Mon, 30 Apr 2012 08:59:38 -0700	[thread overview]
Message-ID: <20120430155937.GB3739@atomide.com> (raw)
In-Reply-To: <20120428163716.GI28062@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [120428 09:40]:
> On Mon, Apr 23, 2012 at 05:13:30PM -0700, Tony Lindgren wrote:
> > * Russell King <rmk+kernel@arm.linux.org.uk> [120423 09:11]:
> > > Add DMA engine support to the OMAP driver.  This supplements the
> > > private DMA API implementation contained within this driver, and the
> > > driver can be switched at build time between using DMA engine and the
> > > private DMA API.
> > 
> > Below is what's needed to use DMA request lines from platform data.
> > Note also the release_mem_region change that we'll now need for
> > this one also (but not as a fix).
> > 
> > I've posted a cleanup patch series to mostly remove plat-omap/devices.c
> > that takes care of passing the DMA request lines in platform data.
> > That series should get merged before the driver changes for this
> > driver to keep DMA working.
> 
> Okay, how do we want to handle this patch?  I don't think there's any
> urgency for this patch at the present time, so I'm quite happy for this
> to be delayed after the next merge window after we have the pre-requisits
> for it in place.  (And trying to get it in earlier is only going to give
> us git tree dependencies to deal with.)

Sounds good to me.

Regards,

Tony

WARNING: multiple messages have this Message-ID (diff)
From: tony@atomide.com (Tony Lindgren)
To: linux-arm-kernel@lists.infradead.org
Subject: [PATCH 07/12] mmc: omap: add DMA engine support
Date: Mon, 30 Apr 2012 08:59:38 -0700	[thread overview]
Message-ID: <20120430155937.GB3739@atomide.com> (raw)
In-Reply-To: <20120428163716.GI28062@n2100.arm.linux.org.uk>

* Russell King - ARM Linux <linux@arm.linux.org.uk> [120428 09:40]:
> On Mon, Apr 23, 2012 at 05:13:30PM -0700, Tony Lindgren wrote:
> > * Russell King <rmk+kernel@arm.linux.org.uk> [120423 09:11]:
> > > Add DMA engine support to the OMAP driver.  This supplements the
> > > private DMA API implementation contained within this driver, and the
> > > driver can be switched at build time between using DMA engine and the
> > > private DMA API.
> > 
> > Below is what's needed to use DMA request lines from platform data.
> > Note also the release_mem_region change that we'll now need for
> > this one also (but not as a fix).
> > 
> > I've posted a cleanup patch series to mostly remove plat-omap/devices.c
> > that takes care of passing the DMA request lines in platform data.
> > That series should get merged before the driver changes for this
> > driver to keep DMA working.
> 
> Okay, how do we want to handle this patch?  I don't think there's any
> urgency for this patch at the present time, so I'm quite happy for this
> to be delayed after the next merge window after we have the pre-requisits
> for it in place.  (And trying to get it in earlier is only going to give
> us git tree dependencies to deal with.)

Sounds good to me.

Regards,

Tony

  reply	other threads:[~2012-04-30 16:00 UTC|newest]

Thread overview: 74+ 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 ` 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   ` Russell King
2012-04-23 16:04 ` [PATCH 02/12] dmaengine: split out virtual channel DMA support from sa11x0 driver Russell King
2012-04-23 16:04   ` Russell King
2012-04-27 18:57   ` Linus Walleij
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   ` Russell King
2012-04-23 16:05 ` [PATCH 04/12] mmc: omap_hsmmc: release correct resource Russell King
2012-04-23 16:05   ` Russell King
2012-04-23 16:05 ` [PATCH 05/12] mmc: omap_hsmmc: add DMA engine support Russell King
2012-04-23 16:05   ` Russell King
2012-04-24  0:16   ` Tony Lindgren
2012-04-24  0:16     ` Tony Lindgren
2012-04-27 19:00   ` Linus Walleij
2012-04-27 19:00     ` Linus Walleij
2012-04-27 19:03     ` Russell King - ARM Linux
2012-04-27 19:03       ` Russell King - ARM Linux
2012-04-27 20:34       ` Linus Walleij
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-23 16:06   ` Russell King
2012-04-24  0:17   ` Tony Lindgren
2012-04-24  0:17     ` Tony Lindgren
2012-04-24 21:51   ` Grazvydas Ignotas
2012-04-24 21:51     ` Grazvydas Ignotas
2012-04-24 22:05     ` Russell King - ARM Linux
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-23 16:06   ` Russell King
2012-04-24  0:13   ` Tony Lindgren
2012-04-24  0:13     ` Tony Lindgren
2012-04-28 16:37     ` Russell King - ARM Linux
2012-04-28 16:37       ` Russell King - ARM Linux
2012-04-30 15:59       ` Tony Lindgren [this message]
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:06   ` 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   ` Russell King
2012-04-23 16:07 ` [PATCH 10/12] spi: omap2-mcspi: add DMA engine support Russell King
2012-04-23 16:07   ` Russell King
2012-04-27 17:20   ` Grant Likely
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:07   ` 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-23 16:08   ` Russell King
2012-04-24  0:17   ` Tony Lindgren
2012-04-24  0:17     ` Tony Lindgren
2012-04-27 20:19   ` Linus Walleij
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 10:38   ` Russell King - ARM Linux
2012-04-24 16:51   ` Tony Lindgren
2012-04-24 16:51     ` Tony Lindgren
2012-04-24 22:47     ` Grazvydas Ignotas
2012-04-24 22:47       ` Grazvydas Ignotas
2012-04-24 23:29       ` Russell King - ARM Linux
2012-04-24 23:29         ` Russell King - ARM Linux
2012-04-24 23:59         ` Grazvydas Ignotas
2012-04-24 23:59           ` Grazvydas Ignotas
2012-05-09 12:25 ` T Krishnamoorthy, Balaji
2012-05-09 12:25   ` T Krishnamoorthy, Balaji
2012-05-15  4:19 ` Vinod Koul
2012-05-15  4:19   ` Vinod Koul
2012-05-15  7:41   ` Russell King - ARM Linux
2012-05-15  7:41     ` Russell King - ARM Linux
2012-05-15  8:59     ` Vinod Koul
2012-05-15  8:59       ` Vinod Koul
2012-05-15  9:32       ` Russell King - ARM Linux
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=20120430155937.GB3739@atomide.com \
    --to=tony@atomide.com \
    --cc=cjb@laptop.org \
    --cc=jarkko.lavinen@nokia.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-mmc@vger.kernel.org \
    --cc=linux-omap@vger.kernel.org \
    --cc=linux@arm.linux.org.uk \
    /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.