From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Selma Bensaid <selma.bensaid@intel.com>
Cc: vinod.koul@intel.com, sylvain.centelles@intel.com,
alsa-devel@alsa-project.org, louis.le.gall@intel.com, lrg@ti.com
Subject: Re: [PATCH] ASOC: utils: Update dummy codec DAI settings to allow stream creation
Date: Mon, 11 Jun 2012 17:33:10 +0800 [thread overview]
Message-ID: <20120611093309.GF11439@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FD5A0CF.4040606@intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 561 bytes --]
On Mon, Jun 11, 2012 at 09:39:59AM +0200, Selma Bensaid wrote:
> are done @AP side. But I really do not understand why ASoC provides the
> soc-utils dummy codec? The current version of the dummy codec is
> useless since it blocks the stream creation: please refer to soc_new_pcm.
The commit log refers to usage in conjunction with soc-pcm, I presume
it's going to be substituted in as a placeholder in cases where there's
loopback or otherwise nothing connected. Like I say it shouldn't be
used for real devices since we should at least specify constraints.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
prev parent reply other threads:[~2012-06-11 9:33 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-06-06 8:02 [PATCH] ASOC: utils: Fix the dummy_codec Selma Bensaid
2012-06-07 8:35 ` Vinod Koul
2012-06-07 10:08 ` [PATCH] ASOC: utils: Update dummy codec DAI settings to allow stream creation Selma Bensaid
2012-06-07 21:30 ` Mark Brown
2012-06-08 8:02 ` Selma Bensaid
2012-06-08 14:26 ` Selma Bensaid
2012-06-11 3:13 ` Mark Brown
2012-06-11 7:39 ` Selma Bensaid
2012-06-11 9:33 ` Mark Brown [this message]
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=20120611093309.GF11439@opensource.wolfsonmicro.com \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=louis.le.gall@intel.com \
--cc=lrg@ti.com \
--cc=selma.bensaid@intel.com \
--cc=sylvain.centelles@intel.com \
--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.