From: Tanu Kaskinen <tanu.kaskinen@linux.intel.com>
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>
Subject: Re: Audio Miniconference 2013 schedule - Edinburgh 21st October
Date: Mon, 07 Oct 2013 22:59:06 +0300 [thread overview]
Message-ID: <1381175946.16362.10.camel@dev-laptop> (raw)
In-Reply-To: <20131007151411.GO21581@sirena.org.uk>
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
next prev parent reply other threads:[~2013-10-07 19:59 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-03 18:17 Audio Miniconference 2013 schedule - Edinburgh 21st October Mark Brown
2013-10-04 10:04 ` Daniel Mack
2013-10-04 10:32 ` Liam Girdwood
2013-10-04 10:39 ` Mark Brown
2013-10-04 21:37 ` Pierre-Louis Bossart
2013-10-04 22:18 ` Mark Brown
2013-10-06 16:10 ` Tanu Kaskinen
2013-10-07 15:14 ` Mark Brown
2013-10-07 19:59 ` Tanu Kaskinen [this message]
2013-10-07 16:39 ` Lars-Peter Clausen
2013-10-07 16:53 ` Mark Brown
2013-10-07 17:22 ` Patrick Lai
2013-10-07 17:44 ` Mark Brown
2013-10-07 20:45 ` 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=1381175946.16362.10.camel@dev-laptop \
--to=tanu.kaskinen@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=arun.raghavan@collabora.co.uk \
--cc=broonie@kernel.org \
--cc=colin@guthr.ie \
--cc=david.henningsson@canonical.com \
--cc=liam.r.girdwood@intel.com \
--cc=pierre-louis.bossart@intel.com \
--cc=pierre-louis.bossart@linux.intel.com \
--cc=tiwai@suse.de \
--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.