Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Liam Girdwood <lrg@slimlogic.co.uk>
Cc: pl bossart <bossart.nospam@gmail.com>, alsa-devel@alsa-project.org
Subject: Re: soc-dsp questions
Date: Tue, 26 Apr 2011 11:18:49 +0100	[thread overview]
Message-ID: <20110426101848.GA23812@sirena.org.uk> (raw)
In-Reply-To: <1303810865.3332.57.camel@odin>

On Tue, Apr 26, 2011 at 10:41:05AM +0100, Liam Girdwood wrote:
> On Mon, 2011-04-25 at 17:01 -0500, pl bossart wrote:
> > To prepare next week's ALSA-Asoc meeting, I reviewed Liam's
> > dsp-upstream code, and I am a bit unclear on the 'no_host_mode'
> > supported by some DAIs. Apparently these are regular ALSA PCM
> > substreams, except that there are no data exchanges to/from the host.

> Ah, this part is WIP and will not be part of the initial submission. We
> are currently using this for audio between the MODEM and ABE that does
> not pass through the CPU. 

This is roughly the same thing I've been talking about for digital DAPM
links.  I've got code which runs at the minute but the implementation
sucks too much, should be able to pull out some of the preparation work
in the next day or so.

> > - is this really important that such PCM devices be known in
> > userspace? Or are they declared only so that ALSA controls are enabled
> > for these streams?

> The intention is that userspace apps would know there is no data, but
> this is probably better discussed at conference. It may also require an
> alsa-lib update too.

Personally I think we should just hide them, but it's fairly painful to
do that immediately due to the ALSA core infrastructure we're using.  If
we refactor to reduce this or to support masking PCMs in the core this
should be less of an issue.

  reply	other threads:[~2011-04-26 10:18 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-04-25 22:01 soc-dsp questions pl bossart
2011-04-26  9:41 ` Liam Girdwood
2011-04-26 10:18   ` Mark Brown [this message]
2011-06-10  6:58     ` Patrick Lai
2011-06-10  9:42       ` Mark Brown
2011-06-11  1:19         ` Patrick Lai
2011-06-11 11:48           ` Mark Brown
2011-06-13  4:55             ` Patrick Lai
2011-06-13 18:01               ` Liam Girdwood
2011-06-13 17:55             ` Liam Girdwood
2011-06-13 17:49           ` Liam Girdwood
  -- strict thread matches above, loose matches on Subject: below --
2011-11-08  8:22 Vinod Koul
2011-11-08 20:20 ` Girdwood, Liam
2011-11-09  8:04   ` Vinod Koul

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=20110426101848.GA23812@sirena.org.uk \
    --to=broonie@opensource.wolfsonmicro.com \
    --cc=alsa-devel@alsa-project.org \
    --cc=bossart.nospam@gmail.com \
    --cc=lrg@slimlogic.co.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox