From: Mark Brown <broonie@kernel.org>
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>,
Liam Girdwood <liam.r.girdwood@intel.com>,
Tanu Kaskinen <tanuk@iki.fi>,
David Henningsson <david.henningsson@canonical.com>,
"Bossart, Pierre-louis" <pierre-louis.bossart@intel.com>
Subject: Re: Audio Miniconference 2013 schedule - Edinburgh 21st October
Date: Fri, 4 Oct 2013 23:18:14 +0100 [thread overview]
Message-ID: <20131004221814.GW27287@sirena.org.uk> (raw)
In-Reply-To: <524F34FD.8090404@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 898 bytes --]
On Fri, Oct 04, 2013 at 04:37:01PM -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
Thanks, that'd be great.
> 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.
Yes, all that stuff needs covering - I think I was trying to include
that with "dynamic DSP firmware handling" but it really isn't at all
clear.
[-- Attachment #1.2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2013-10-04 22:18 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 [this message]
2013-10-06 16:10 ` Tanu Kaskinen
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=20131004221814.GW27287@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--cc=arun.raghavan@collabora.co.uk \
--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=tanuk@iki.fi \
--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.