Alsa-Devel Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Lars-Peter Clausen <lars@metafoo.de>
To: Mark Brown <broonie@kernel.org>, alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: Audio Mini Summit 2015, 8th October, Dublin
Date: Thu, 08 Oct 2015 16:13:18 +0200	[thread overview]
Message-ID: <561679FE.3060809@metafoo.de> (raw)
In-Reply-To: <20151007152047.GQ12635@sirena.org.uk>


[-- Attachment #1.1: Type: text/plain, Size: 1299 bytes --]

On 10/07/2015 05:20 PM, Mark Brown wrote:
> On Mon, Oct 05, 2015 at 12:17:52AM +0100, Mark Brown wrote:
>> [This message is BCCed to everyone currently on the signup list]
>>
>> As previously announce the audio mini-summit for this year will be this
>> Thursday (8th August) at CCD in Dublin.  Topics we currently have on the
>> list for discussion are:
> 
> Current list:
> 
>  - Power saving and general system design decisions (is what we're doing
>    lining up with modern hardware with things like multiple output
>    streams?).
>  - Documentation.
>  - alsa-lib releae plans.
>  - What to do with HDMI and its integration with graphics.
>  - Test tools (Intel BAT and others).
>  - BATCH flag.
>  - Fuzz control PCM APIs.
>  - Splitting out root only controls.
>  - ACPI simple-card and general generic card support.
>  - Topology & media controller integration.
>  - Kernel tinification.
>  - Android <-> alsa-lib configuration translation.
>  - HDA restructuring.
>   - Support for DisplayPort MST.
>  - PCM core simplification - the code is currently quite complex!
>  - Soundwire driver support plans.
>  - ASoC multichannel.
>  - Random DAPM changes.

Media controller:
http://blogs.s-osg.org/working-complicated-problems-media-controller-workshop/



[-- Attachment #1.2: OpenPGP digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]

[-- Attachment #2: Type: text/plain, Size: 0 bytes --]



  reply	other threads:[~2015-10-08 14:13 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-10-04 23:17 Audio Mini Summit 2015, 8th October, Dublin Mark Brown
2015-10-06  8:02 ` Alexander E. Patrakov
2015-10-06  9:35   ` Mark Brown
2015-10-06 10:50 ` Mark Brown
2015-10-06 10:59 ` Koul, Vinod
2015-10-06 16:56   ` Mark Brown
2015-10-08 15:43     ` Koul, Vinod
2015-10-09  7:11       ` Jie, Yang
2015-10-06 15:09 ` Takashi Iwai
2015-10-06 17:01   ` Mark Brown
2015-10-07  8:49 ` Lin, Mengdong
2015-10-07 14:22   ` Mark Brown
2015-10-07 15:20 ` Mark Brown
2015-10-08 14:13   ` Lars-Peter Clausen [this message]
2015-10-08 14:29     ` Lars-Peter Clausen
2015-10-09 13:29       ` Lars-Peter Clausen
2015-10-11 19:13         ` Jaroslav Kysela
2015-10-12  9:01           ` Koul, Vinod
2015-10-12  9:35             ` Liam Girdwood
2015-10-12  8:46         ` Takashi Iwai
2015-10-12 15:54           ` Lars-Peter Clausen
2015-10-12 16:21             ` Jaroslav Kysela
2015-10-13  1:34               ` Jie, Yang
2015-10-15 13:06                 ` Jie, Yang
2015-10-12  8:43       ` Takashi Iwai
2015-10-12  9:11         ` Lars-Peter Clausen

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=561679FE.3060809@metafoo.de \
    --to=lars@metafoo.de \
    --cc=alsa-devel@alsa-project.org \
    --cc=broonie@kernel.org \
    --cc=lgirdwood@gmail.com \
    --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