From: Mark Brown <broonie@opensource.wolfsonmicro.com>
To: Jaroslav Kysela <perex@perex.cz>
Cc: ALSA development <alsa-devel@alsa-project.org>,
Takashi Iwai <tiwai@suse.de>, Ian Molton <ian@mnementh.co.uk>,
Graeme Gregory <gg@slimlogic.co.uk>,
Stefan Schmidt <stefan@datenfreihafen.org>,
Liam Girdwood <lrg@slimlogic.co.uk>
Subject: Re: [PATCH] ascenario: Add scenario support to alsa-lib
Date: Wed, 7 Oct 2009 14:53:20 +0100 [thread overview]
Message-ID: <20091007135320.GI19135@sirena.org.uk> (raw)
In-Reply-To: <alpine.LNX.2.00.0910061510320.31529@eeebox2.perex-int.cz>
On Tue, Oct 06, 2009 at 03:33:39PM +0200, Jaroslav Kysela wrote:
> - represent QoS with string (name) rather than integer -
> QoS is also quite use-case specific
I believe the idea is that QoS should be relatively generic - the long
term idea is that the application should be able to give some idea of
the sort of output it is trying to provide to the stack to enable the
stack to make decisions about configuration.
next prev parent reply other threads:[~2009-10-07 13:53 UTC|newest]
Thread overview: 49+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-10-01 9:47 [RFC] Add scenario management Stefan Schmidt
2009-10-01 9:47 ` [PATCH] ascenario: Add scenario support to alsa-lib Stefan Schmidt
2009-10-01 12:28 ` Mark Brown
2009-10-01 12:48 ` Liam Girdwood
2009-10-01 13:02 ` Mark Brown
2009-10-01 14:06 ` Liam Girdwood
2009-10-01 14:18 ` Mark Brown
2009-10-01 13:19 ` Stefan Schmidt
2009-10-01 13:24 ` Mark Brown
2009-10-01 13:38 ` Stefan Schmidt
2009-10-01 13:39 ` pl bossart
2009-10-01 13:54 ` Liam Girdwood
2009-10-01 14:11 ` Stefan Schmidt
2009-10-01 15:08 ` Stefan Schmidt
2009-10-05 8:27 ` Stefan Schmidt
2009-10-05 9:14 ` Jaroslav Kysela
2009-10-05 9:35 ` Stefan Schmidt
2009-10-06 8:23 ` Jaroslav Kysela
2009-10-06 8:41 ` Takashi Iwai
2009-10-06 9:00 ` Jaroslav Kysela
2009-10-06 9:13 ` Takashi Iwai
2009-10-07 8:10 ` Jaroslav Kysela
2009-10-07 8:52 ` Takashi Iwai
2009-10-07 9:47 ` Jaroslav Kysela
2009-10-07 9:55 ` Takashi Iwai
2009-10-06 9:28 ` Takashi Iwai
2009-10-06 11:05 ` Jaroslav Kysela
2009-10-06 13:33 ` Jaroslav Kysela
2009-10-06 13:46 ` Takashi Iwai
2009-10-07 13:48 ` Stefan Schmidt
2009-10-06 15:12 ` Stefan Schmidt
2009-10-06 15:54 ` [PATCH 0/3] ascenario: Bring it to compile after API changes Stefan Schmidt
2009-10-06 15:54 ` [PATCH 1/3] ascenario: Fix typedef for snd_scenario_t Stefan Schmidt
2009-10-06 16:04 ` Takashi Iwai
2009-10-06 17:08 ` Stefan Schmidt
2009-10-06 17:16 ` Jaroslav Kysela
2009-10-06 17:42 ` Stefan Schmidt
2009-10-06 15:54 ` [PATCH 2/3] ascenario: Fix usage of new typedefed snd_scenario_t Stefan Schmidt
2009-10-06 15:54 ` [PATCH 3/3] ascenario: Catchup with function declaration changes Stefan Schmidt
2009-10-07 13:53 ` Mark Brown [this message]
2009-10-06 10:29 ` [PATCH] ascenario: Add scenario support to alsa-lib Stefan Schmidt
2009-10-01 9:47 ` [PATCH] ascenario: Add dump and configure utils for ascneario Stefan Schmidt
2009-10-02 9:12 ` [RFC] Add scenario management Takashi Iwai
2009-10-02 9:55 ` Stefan Schmidt
2009-10-02 9:58 ` Takashi Iwai
2009-10-02 9:58 ` Jaroslav Kysela
2009-10-02 10:12 ` Takashi Iwai
2009-10-02 10:45 ` Liam Girdwood
2009-10-02 11:03 ` Jaroslav Kysela
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=20091007135320.GI19135@sirena.org.uk \
--to=broonie@opensource.wolfsonmicro.com \
--cc=alsa-devel@alsa-project.org \
--cc=gg@slimlogic.co.uk \
--cc=ian@mnementh.co.uk \
--cc=lrg@slimlogic.co.uk \
--cc=perex@perex.cz \
--cc=stefan@datenfreihafen.org \
--cc=tiwai@suse.de \
/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.