From mboxrd@z Thu Jan  1 00:00:00 1970
From: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
Subject: Re: Audio Miniconference 2013 schedule - Edinburgh
 21st October
Date: Mon, 07 Oct 2013 22:59:06 +0300
Message-ID: <1381175946.16362.10.camel@dev-laptop>
References: <20131003181754.GE27287@sirena.org.uk>
 <524F34FD.8090404@linux.intel.com> <1381075859.3245.31.camel@laptop>
 <20131007151411.GO21581@sirena.org.uk>
Mime-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Return-path: <alsa-devel-bounces@alsa-project.org>
Received: from mga09.intel.com (mga09.intel.com [134.134.136.24])
 by alsa0.perex.cz (Postfix) with ESMTP id 1CF19265193
 for <alsa-devel@alsa-project.org>; Mon,  7 Oct 2013 21:59:55 +0200 (CEST)
In-Reply-To: <20131007151411.GO21581@sirena.org.uk>
List-Unsubscribe: <http://mailman.alsa-project.org/mailman/options/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=unsubscribe>
List-Archive: <http://mailman.alsa-project.org/pipermail/alsa-devel/>
List-Post: <mailto:alsa-devel@alsa-project.org>
List-Help: <mailto:alsa-devel-request@alsa-project.org?subject=help>
List-Subscribe: <http://mailman.alsa-project.org/mailman/listinfo/alsa-devel>,
 <mailto:alsa-devel-request@alsa-project.org?subject=subscribe>
Errors-To: alsa-devel-bounces@alsa-project.org
Sender: alsa-devel-bounces@alsa-project.org
To: Mark Brown <broonie@kernel.org>
Cc: Colin Guthrie <colin@guthr.ie>, alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>, Arun Raghavan <arun.raghavan@collabora.co.uk>, Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>, Vinod Koul <vinod.koul@intel.com>, Liam Girdwood <liam.r.girdwood@intel.com>, David Henningsson <david.henningsson@canonical.com>, "Bossart,
 Pierre-louis" <pierre-louis.bossart@intel.com>
List-Id: alsa-devel@alsa-project.org

On Mon, 2013-10-07 at 16:14 +0100, Mark Brown wrote:
> On Sun, Oct 06, 2013 at 07:10:59PM +0300, Tanu Kaskinen wrote:
> 
> > Perhaps I should present our (Murphy[1] team at Intel) plans for the
> > routing infrastructure and policy in PulseAudio? It might be relevant
> > for this, although effect offloading and firmware handling is not
> > something that we have thought about. Even without effect offloading and
> > firmware handling the routing system has to deal with use case
> > prioritizing and constraints regarding what audio paths are available
> > and what paths can be used simultaneously.
> 
> That sounds interesting, there was also a use case management thing on
> the agenda - do you want to take that?

Sure, why not.

-- 
Tanu