alsa-devel.alsa-project.org archive mirror
 help / color / mirror / Atom feed
From: Russell King - ARM Linux <linux@arm.linux.org.uk>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: alsa-devel@alsa-project.org, Lars-Peter Clausen <lars@metafoo.de>,
	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 11:17:04 +0000	[thread overview]
Message-ID: <20130322111704.GZ4977@n2100.arm.linux.org.uk> (raw)
In-Reply-To: <20130321152206.GA14768@opensource.wolfsonmicro.com>

On Thu, Mar 21, 2013 at 04:22:06PM +0100, Mark Brown wrote:
> On Thu, Mar 21, 2013 at 04:06:27PM +0100, Lars-Peter Clausen wrote:
> 
> > Hm, I only saw this series today would have been good to be on Cc. I've been
> > working on something very similar. My series goes a bit further though, it
> > implements an (almost generic) dmaengine based PCM driver using the of
> > bindings. So you need almost no platform code. The only things that are
> > platform specific at the moment is the pcm_hardware struct, but I'd like to
> > replace that in the future with something that queries the pcm hardware
> > parameter like max_period from the DMA engine driver. And another bit that is
> > still driver specific is a callback that fills the dma_slave_config struct.
> 
> FWIW it might be worth looking at the one rmk wrote but has never wanted
> to submit for whatever reason.

Err no, stop twisting the facts.  I know nothing is ever your fault.  You
rejected it because it was providing support for non-cyclic supporting
DMA engine drivers.

I've since added support to it for cyclic DMA engines, but I've retained
the non-cyclic support in it because I don't see why I should remove it
when it works for me, especially given the difficulties with getting
anything in sound/soc changed once its been merged.

Plus, as I've already said to you, I no longer develop and test it because
the platform I was using is now doing service as my firewall, and you'll
forgive me for not wanting to take the whole of *.arm.linux.org.uk
offline to mess around with ASoC stuff.  But that's not to say I don't
care about the issue.

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

Thread overview: 27+ 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 ` [PATCH 1/2] dmaengine: add const for name parameter Shawn Guo
2013-03-15  8:53   ` Markus Pargmann
2013-03-21  9:47     ` Vinod Koul
2013-03-21 13:10       ` Markus Pargmann
2013-03-21 12:54         ` Vinod Koul
2013-03-21 14:45           ` [PATCH] DMA: of: const name fixup Markus Pargmann
2013-03-21 14:57       ` [PATCH 1/2] dmaengine: add const for name parameter Shawn Guo
2013-04-02 17:51         ` Vinod Koul
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 10:00   ` Sebastien Guiriec
2013-03-21  9:57   ` Vinod Koul
2013-03-21 14:53     ` Shawn Guo
2013-03-22  8:07       ` Sebastien Guiriec
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 15:06   ` Lars-Peter Clausen
2013-03-21 15:22     ` Mark Brown
2013-03-21 16:26       ` Lars-Peter Clausen
2013-03-21 16:47         ` Mark Brown
2013-03-22 11:30         ` Russell King - ARM Linux
2013-03-22 11:39           ` Lars-Peter Clausen
2013-03-22 11:17       ` Russell King - ARM Linux [this message]
2013-03-22 11:28         ` Mark Brown
2013-03-22 11:42           ` Lars-Peter Clausen
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=20130322111704.GZ4977@n2100.arm.linux.org.uk \
    --to=linux@arm.linux.org.uk \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=lars@metafoo.de \
    --cc=linux-arm-kernel@lists.infradead.org \
    --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 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).