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 04:13:32 +0100 [thread overview]
Message-ID: <20120611031331.GG28211@opensource.wolfsonmicro.com> (raw)
In-Reply-To: <4FD1B19E.1030808@intel.com>
On Fri, Jun 08, 2012 at 10:02:38AM +0200, Selma Bensaid wrote:
Please check your mailer configuration, it's doing something really odd
with the word wrapping which makes things hard to read.
>> 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.
You shouldn't be doing this, you should have actual devices for these
with appropriate capabilities for the device. Ideally we'd even have
real drivers for these things! For example, you're currently setting
them up as supporting continuous audio rates but both BT and baseband
devices won't do anything like that. Even your new version which has
all the rates enabled has about the same issue.
next prev parent reply other threads:[~2012-06-11 3:13 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 [this message]
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=20120611031331.GG28211@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.