From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Ramesh Babu <ramesh.babu@linux.intel.com>,
Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Trent Piepho <tpiepho@gmail.com>,
Liam Girdwood <lrg@ti.com>
Subject: Re: ASoC:Question rate constraint between the dais
Date: Fri, 16 Mar 2012 21:00:12 +0100 [thread overview]
Message-ID: <4F639BCC.2050703@metafoo.de> (raw)
In-Reply-To: <20120316192513.GJ3158@opensource.wolfsonmicro.com>
On 03/16/2012 08:25 PM, Mark Brown wrote:
> On Thu, Mar 15, 2012 at 05:28:13PM -0400, Trent Piepho wrote:
>
>> There is a race when the constraints change dynamically. See the
>> fsl_ssi.c driver and the sample size constraint in synchronous mode.
>
> This is just a limitation of the ALSA ABI - there's nothing we can do
> about it without changing the userspace interface so we just have to
> live with it and error out if an application ever manages to hit the
> race and pick something incompatible with other active streams (note
> that the symmetric rates support has a dev_warn() complaining about
> hitting the race).
>
I think the real problem with this is, that currently a userspace application
will usually exit with an error when such a race occurs, while it should be
possible to just restart the enumeration process and try with another format.
So I'm wondering if we can make it easier for userspace to detect that the
constraints have changed and it may retry with other parameters? E.g. return a
special error code in such a case.
- Lars
next prev parent reply other threads:[~2012-03-16 19:59 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-03-15 9:53 ASoC:Question rate constraint between the dais Ramesh Babu
2012-03-15 17:53 ` Mark Brown
2012-03-15 21:28 ` Trent Piepho
2012-03-16 19:25 ` Mark Brown
2012-03-16 20:00 ` Lars-Peter Clausen [this message]
2012-03-17 11:41 ` Mark Brown
2012-03-17 13:00 ` Clemens Ladisch
[not found] ` <9DF50024A2F6A5439EBFE2E74F4E9198055254@BGSMSX101.gar.corp.intel.com>
2012-03-16 10:05 ` Omair Mohammed Abdullah
2012-03-16 19:22 ` Mark Brown
2012-03-16 22:01 ` Trent Piepho
2012-03-17 11:48 ` Mark Brown
2012-03-17 19:49 ` Trent Piepho
2012-03-17 20:31 ` Mark Brown
2012-03-18 6:22 ` Jassi Brar
2012-03-18 21:27 ` Mark Brown
2012-03-19 16:12 ` James Courtier-Dutton
2012-03-19 16:32 ` 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=4F639BCC.2050703@metafoo.de \
--to=lars@metafoo.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=lrg@ti.com \
--cc=ramesh.babu@linux.intel.com \
--cc=tiwai@suse.de \
--cc=tpiepho@gmail.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;
as well as URLs for NNTP newsgroup(s).