From: Vinod Koul <vinod.koul@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>,
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 II - Edinburgh 21st October
Date: Tue, 15 Oct 2013 22:14:08 +0530 [thread overview]
Message-ID: <20131015164408.GQ2954@intel.com> (raw)
In-Reply-To: <20131014161003.GC2443@sirena.org.uk>
[-- Attachment #1.1: Type: text/plain, Size: 1960 bytes --]
On Mon, Oct 14, 2013 at 05:10:03PM +0100, Mark Brown wrote:
> Another go at the schedule for the mini-summit based on the feedback
> last time. Same three major topics:
>
> - Compressed audio review: tinycompress, integration into userspace,
> driver upstreaming.
Sorry I am not going to make it the conf!
I will send out the status of offload, challanges, drivers (not many) before you
guys start the meeting. Together with Eric's usermode and Android update it
should cover well. I would have loved to see something on PA side too.
Arun any plans to implement support for compressed offload?
> - UCM and other use case management status & review (Tanu).
>
> - Effects offload to DSPs with dynamically instantiatable algorithms,
> and general dynamic DSP firmware handling including DSP resource
> management (Pierre).
We are working on effect offloading part and creating framework in sound for
DSPs to do that. Hopefully we should be able to push an RFC before this week and
you guys with Pierre can discuss this over the meeting and provide feedback for
future work on this topic
> Plus a few things that only one or two people brought up:
>
> - Process stuff (the list, bug tracking and so on).
>
> - Some relatively specific hardware support topics:
> - HDMI hotplug handling throughout the stack
> - Mic status LED handling throughout the stack.
>
> - Code cleanups:
> - Moving away from the custom ALSA device registration infrastructure.
> - General code modernisation.
>
> - Performance, especially DAPM (Patrick)
I want to bring the attention to DAPM framework bugs. Somehow recently I
stumbled on quite a few occasions of DAPM bugs and the best part was that the
fix was already availble upstream, ported to stable later version than I had or
NOT ported. Mark, can you pls help by ensuring the right fixes are marked to
stable so that users dont get hit by it!
~Vinod
[-- 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-15 17:37 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-10-14 16:10 Audio Miniconference 2013 schedule II - Edinburgh 21st October Mark Brown
2013-10-15 16:00 ` Eric Laurent
2013-10-15 17:04 ` Mark Brown
2013-10-15 16:44 ` Vinod Koul [this message]
2013-10-15 19:26 ` Mark Brown
2013-10-16 2:17 ` Vinod Koul
2013-10-16 10:28 ` Mark Brown
2013-10-16 10:39 ` Arun Raghavan
2013-10-18 15:48 ` Takashi Iwai
2013-10-18 17:19 ` Mark Brown
2013-10-20 21:25 ` Patrick Lai
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=20131015164408.GQ2954@intel.com \
--to=vinod.koul@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=tanuk@iki.fi \
--cc=tiwai@suse.de \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).