All of lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Lars-Peter Clausen <lars@metafoo.de>
Cc: alsa-devel@alsa-project.org,
	Russell King - ARM Linux <linux@arm.linux.org.uk>,
	Vinod Koul <vinod.koul@intel.com>,
	Sebastien Guiriec <s-guiriec@ti.com>,
	Markus Pargmann <mpa@pengutronix.de>,
	Shawn Guo <shawn.guo@linaro.org>,
	linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 0/2] ASoC: dmaengine_pcm: support generic DMA binding users
Date: Fri, 22 Mar 2013 12:48:00 +0100	[thread overview]
Message-ID: <20130322114759.GM22890@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <514C43B4.1040403@metafoo.de>


[-- Attachment #1.1: Type: text/plain, Size: 821 bytes --]

On Fri, Mar 22, 2013 at 12:42:44PM +0100, Lars-Peter Clausen wrote:
> On 03/22/2013 12:28 PM, Mark Brown wrote:

> > We need support for both cyclic and non-cyclic devices, one doesn't
> > preclude the other and both kinds of hardware exist.  Cyclic is much
> > more common and generally more desirable but that doesn't mean that
> > hardware designers always provide it.

> The idea was to only have support for the cyclic dmaengine API in the ASoC
> PCM driver and deal with the emulation of cyclic transfers for hardware,
> which does not implement it, at the dmaengine layer.

Perhaps I'm misremembering but I thought there was pushback on that on
the basis that there are few if any other users of cyclic DMA so nobody
else cares or wants to deal with the hassle?  A quick grep seems not to
turn up any other users.

[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



WARNING: multiple messages have this Message-ID (diff)
From: broonie@opensource.wolfsonmicro.com (Mark Brown)
To: linux-arm-kernel@lists.infradead.org
Subject: [alsa-devel] [PATCH 0/2] ASoC: dmaengine_pcm: support generic DMA binding users
Date: Fri, 22 Mar 2013 12:48:00 +0100	[thread overview]
Message-ID: <20130322114759.GM22890@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <514C43B4.1040403@metafoo.de>

On Fri, Mar 22, 2013 at 12:42:44PM +0100, Lars-Peter Clausen wrote:
> On 03/22/2013 12:28 PM, Mark Brown wrote:

> > We need support for both cyclic and non-cyclic devices, one doesn't
> > preclude the other and both kinds of hardware exist.  Cyclic is much
> > more common and generally more desirable but that doesn't mean that
> > hardware designers always provide it.

> The idea was to only have support for the cyclic dmaengine API in the ASoC
> PCM driver and deal with the emulation of cyclic transfers for hardware,
> which does not implement it, at the dmaengine layer.

Perhaps I'm misremembering but I thought there was pushback on that on
the basis that there are few if any other users of cyclic DMA so nobody
else cares or wants to deal with the hassle?  A quick grep seems not to
turn up any other users.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: signature.asc
Type: application/pgp-signature
Size: 836 bytes
Desc: Digital signature
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20130322/e46380c3/attachment.sig>

  reply	other threads:[~2013-03-22 11:48 UTC|newest]

Thread overview: 54+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-03-15  3:36 [PATCH 0/2] ASoC: dmaengine_pcm: support generic DMA binding users Shawn Guo
2013-03-15  3:36 ` Shawn Guo
2013-03-15  3:36 ` [PATCH 1/2] dmaengine: add const for name parameter Shawn Guo
2013-03-15  3:36   ` Shawn Guo
2013-03-15  8:53   ` Markus Pargmann
2013-03-15  8:53     ` Markus Pargmann
2013-03-21  9:47     ` Vinod Koul
2013-03-21  9:47       ` Vinod Koul
2013-03-21 13:10       ` Markus Pargmann
2013-03-21 13:10         ` Markus Pargmann
2013-03-21 12:54         ` Vinod Koul
2013-03-21 12:54           ` Vinod Koul
2013-03-21 14:45           ` [PATCH] DMA: of: const name fixup Markus Pargmann
2013-03-21 14:45             ` Markus Pargmann
2013-03-21 14:57       ` [PATCH 1/2] dmaengine: add const for name parameter Shawn Guo
2013-03-21 14:57         ` Shawn Guo
2013-04-02 17:51         ` Vinod Koul
2013-04-02 17:51           ` Vinod Koul
2013-04-02 19:47           ` Mark Brown
2013-04-02 19:47             ` Mark Brown
2013-03-15  3:36 ` [PATCH 2/2] ASoC: dmaengine_pcm: add snd_dmaengine_generic_pcm_open() Shawn Guo
2013-03-15  3:36   ` Shawn Guo
2013-03-15 10:00   ` Sebastien Guiriec
2013-03-15 10:00     ` Sebastien Guiriec
2013-03-21  9:57   ` Vinod Koul
2013-03-21  9:57     ` Vinod Koul
2013-03-21 14:53     ` Shawn Guo
2013-03-21 14:53       ` Shawn Guo
2013-03-22  8:07       ` Sebastien Guiriec
2013-03-22  8:07         ` Sebastien Guiriec
2013-03-22  8:39         ` Shawn Guo
2013-03-22  8:39           ` Shawn Guo
2013-03-21  2:39 ` [PATCH 0/2] ASoC: dmaengine_pcm: support generic DMA binding users Shawn Guo
2013-03-21  2:39   ` Shawn Guo
2013-03-21 15:06   ` Lars-Peter Clausen
2013-03-21 15:06     ` [alsa-devel] " Lars-Peter Clausen
2013-03-21 15:22     ` Mark Brown
2013-03-21 15:22       ` [alsa-devel] " Mark Brown
2013-03-21 16:26       ` Lars-Peter Clausen
2013-03-21 16:26         ` [alsa-devel] " Lars-Peter Clausen
2013-03-21 16:47         ` Mark Brown
2013-03-21 16:47           ` [alsa-devel] " Mark Brown
2013-03-22 11:30         ` Russell King - ARM Linux
2013-03-22 11:30           ` [alsa-devel] " Russell King - ARM Linux
2013-03-22 11:39           ` Lars-Peter Clausen
2013-03-22 11:39             ` [alsa-devel] " Lars-Peter Clausen
2013-03-22 11:17       ` Russell King - ARM Linux
2013-03-22 11:17         ` [alsa-devel] " Russell King - ARM Linux
2013-03-22 11:28         ` Mark Brown
2013-03-22 11:28           ` [alsa-devel] " Mark Brown
2013-03-22 11:42           ` Lars-Peter Clausen
2013-03-22 11:42             ` [alsa-devel] " Lars-Peter Clausen
2013-03-22 11:48             ` Mark Brown [this message]
2013-03-22 11:48               ` Mark Brown

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=20130322114759.GM22890@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux@arm.linux.org.uk \
    --cc=mpa@pengutronix.de \
    --cc=s-guiriec@ti.com \
    --cc=shawn.guo@linaro.org \
    --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.