All of lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
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>,
	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: Mon, 07 Oct 2013 18:39:48 +0200	[thread overview]
Message-ID: <5252E3D4.2020400@metafoo.de> (raw)
In-Reply-To: <20131003181754.GE27287@sirena.org.uk>

On 10/03/2013 08:17 PM, Mark Brown wrote:
> The audio mini-summit in Edinburgh is now less than a month away so it
> seems like a good time to start pulling together a schedule.  Looking at
> the topics people mentioned when filling out the registration form there
> were three major topics that people wanted to cover:
> 
>  - Compressed audio review: tinycompress, integration into userspace,
>    driver upstreaming.
> 
>  - UCM and other use case management status & review.
> 
>  - Effects offload to DSPs with dynamically instantiatable algorithms,
>    and general dynamic DSP firmware handling.
> 
> 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.
> 
>  - General routing control in userspace - UIs, automation.
> 
> The first question is if there is anything important that is missing
> from the above list - please speak up soon if there is!  It'd also be
> good to have volunteers to lead the discussions in each area.
> 

One thing I think that would be good to discuss, considering how often this
has come up over the last few months, is devicetree bindings for audio
devices. And what should and needs to be done on the framework side to
better support this.

- Lars

  parent reply	other threads:[~2013-10-07 16:38 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
2013-10-07 16:39 ` Lars-Peter Clausen [this message]
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=5252E3D4.2020400@metafoo.de \
    --to=lars@metafoo.de \
    --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 \
    --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.