From: Selma Bensaid <selma.bensaid@intel.com>
To: Mark Brown <broonie@opensource.wolfsonmicro.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: Fri, 08 Jun 2012 10:02:38 +0200 [thread overview]
Message-ID: <4FD1B19E.1030808@intel.com> (raw)
In-Reply-To: <20120607213057.GA19485@sirena.org.uk>
On 06/07/2012 11:30 PM, Mark Brown wrote:
>
> I still don't understand what this is actually supposed to fix - why are
> we trying to set up a stream to something that isn't there? Though it
> looks like this was added for dynamic PCM which has no mainline users so
> perhaps there's a sensible use for this...
I'm trying to use the dummy codec for BT and Modem device where the
coded is handled
@ AP side.
Without updating the dummy codec, I fails when opening my devices due to
the check
performed in soc_pcm_open: No matching rates, No matching formats and No
matching
channels Errors.
>
> The other question is how we decide that these are sensible values to
> set for the dummy CODEC.
For formats the dummy codec support all formats so it does not impact
the runtime->hw.formats = codec_dai_drv->playback.formats &
cpu_dai_drv->playback.formats;
For rates, I 'll submit a new version of the patch since the
SNDRV_PCM_RATE_CONTINUOUS is not the right value to use.
For channels_min, the value 1 does not impact the
runtime->hw.channels_min = max(codec_dai_drv->capture.channels_min,
cpu_dai_drv->capture.channels_min);
For channels_max, I 'll submit a new version of the patch to set it to
MAX so does not impact the runtime->hw.channels_max =
min(codec_dai_drv->playback.channels_max
cpu_dai_drv->playback.channels_max);
---------------------------------------------------------------------
Intel Corporation SAS (French simplified joint stock company)
Registered headquarters: "Les Montalets"- 2, rue de Paris,
92196 Meudon Cedex, France
Registration Number: 302 456 199 R.C.S. NANTERRE
Capital: 4,572,000 Euros
This e-mail and any attachments may contain confidential material for
the sole use of the intended recipient(s). Any review or distribution
by others is strictly prohibited. If you are not the intended
recipient, please contact the sender and delete all copies.
next prev parent reply other threads:[~2012-06-08 8:03 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 [this message]
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
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=4FD1B19E.1030808@intel.com \
--to=selma.bensaid@intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=louis.le.gall@intel.com \
--cc=lrg@ti.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.