Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@ti.com>
Cc: alsa-devel@alsa-project.org, patches@opensource.wolfsonmicro.com
Subject: Re: [PATCH] ASoC: Provide a more complete DMA driver stub
Date: Mon, 5 Dec 2011 23:19:46 +0000	[thread overview]
Message-ID: <20111205231946.GB21083@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <1323122570.8134.1.camel@odin>

On Mon, Dec 05, 2011 at 10:02:50PM +0000, Liam Girdwood wrote:
> On Mon, 2011-12-05 at 20:56 +0000, Mark Brown wrote:
> > Allow userspace applications to do more parameter setting by providing a
> > more complete stub DMA driver specifying a wildcard set of formats and
> > channels and essentially random values for the DMA parameters. This is
> > required for useful runtime operation of the dummy DMA driver until we
> > are able to figure out how to power up links and do hw_params() from DAPM.

> Is this also intended to be used for hostless DAI links e.g.

> MODEM <-> MCBSP <-> DSP

It's for any sort of link that doesn't go through a DMA controller the
kernel can see - this is the DMA driver that gets stubbed in when the
DAI doesn't have a DMA driver.  In the case above I guess it depends on
if the DMA controller is hidden by the DSP or not.

  reply	other threads:[~2011-12-05 23:19 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-05 20:56 [PATCH] ASoC: Provide a more complete DMA driver stub Mark Brown
2011-12-05 22:02 ` Liam Girdwood
2011-12-05 23:19   ` Mark Brown [this message]
2011-12-06 13:32     ` Girdwood, Liam

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=20111205231946.GB21083@opensource.wolfsonmicro.com \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=lrg@ti.com \
    --cc=patches@opensource.wolfsonmicro.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