All of lore.kernel.org
 help / color / mirror / Atom feed
From: Tanu Kaskinen <tanuk@iki.fi>
To: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
Cc: Colin Guthrie <colin@guthr.ie>,
	alsa-devel@alsa-project.org, Takashi Iwai <tiwai@suse.de>,
	Arun Raghavan <arun.raghavan@collabora.co.uk>,
	Vinod Koul <vinod.koul@intel.com>,
	Mark Brown <broonie@kernel.org>,
	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: Sun, 06 Oct 2013 19:10:59 +0300	[thread overview]
Message-ID: <1381075859.3245.31.camel@laptop> (raw)
In-Reply-To: <524F34FD.8090404@linux.intel.com>

On Fri, 2013-10-04 at 16:37 -0500, Pierre-Louis Bossart wrote:
> >   - Effects offload to DSPs with dynamically instantiatable algorithms,
> >     and general dynamic DSP firmware handling.
> 
> I can try and prepare an overview about what we've started to look at 
> for effect offload. The one thing that's missing from the agenda is that 
> DSP offload and dynamic firmware handling do require control on audio 
> policy (high level arbitration between use cases), audio routing (some 
> paths may not be available at all times) and resource management 
> (memory/MCPS/etc). We not be able to solve this in a generic manner but 
> having hooks to detect/notify a DSP resource is or is not available 
> might be a good thing.

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.

BTW, there will also be a Murphy meeting/BoF on Wednesday at 13:00 in
the Dunvegan room at the Sheraton hotel next to the conference center.
Anyone who's interested in Murphy is welcome to attend. I'd expect there
to be a general overview of Murphy from Janos, and I should present the
status and plans for the routing work in PulseAudio (perhaps in more
detail than in the audio miniconf). Other than that, there's not much
else planned, just general Q&A with the Murphy developers (Janos Kovacs
and Jaska Uimonen will be present - too bad they couldn't make it to the
audio miniconf).

[1] Murphy is the resource policy daemon in Tizen IVI,
https://01.org/murphy/

-- 
Tanu

  parent reply	other threads:[~2013-10-06 16:11 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 [this message]
2013-10-07 15:14     ` Mark Brown
2013-10-07 19:59       ` Tanu Kaskinen
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=1381075859.3245.31.camel@laptop \
    --to=tanuk@iki.fi \
    --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=tanu.kaskinen@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.