From mboxrd@z Thu Jan 1 00:00:00 1970 From: Mark Brown Subject: Re: [PATCH] ascenario: Add scenario support to alsa-lib Date: Wed, 7 Oct 2009 14:53:20 +0100 Message-ID: <20091007135320.GI19135@sirena.org.uk> References: <20091001150849.GE5936@excalibur.local> <20091005082747.GA3983@excalibur.local> <20091005093502.GC3983@excalibur.local> Mime-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Return-path: Received: from cassiel.sirena.org.uk (cassiel.sirena.org.uk [80.68.93.111]) by alsa0.perex.cz (Postfix) with ESMTP id 3675C103899 for ; Wed, 7 Oct 2009 15:53:22 +0200 (CEST) Content-Disposition: inline In-Reply-To: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Sender: alsa-devel-bounces@alsa-project.org Errors-To: alsa-devel-bounces@alsa-project.org To: Jaroslav Kysela Cc: ALSA development , Takashi Iwai , Ian Molton , Graeme Gregory , Stefan Schmidt , Liam Girdwood List-Id: alsa-devel@alsa-project.org 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.