From: "Koul, Vinod" <vinod.koul@intel.com>
To: "broonie@kernel.org" <broonie@kernel.org>,
"alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Cc: "tiwai@suse.de" <tiwai@suse.de>,
"lgirdwood@gmail.com" <lgirdwood@gmail.com>
Subject: Re: Audio Mini Summit 2015, 8th October, Dublin
Date: Tue, 6 Oct 2015 10:59:03 +0000 [thread overview]
Message-ID: <1444129142.25504.7.camel@intel.com> (raw)
In-Reply-To: <20151004231752.GA22609@sirena.org.uk>
On Mon, 2015-10-05 at 00:17 +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:
>
> - Power saving and general system design decisions (is what we're doing
> lining up with modern hardware with things like multiple output
> streams?).
> - What to do with HDMI and its integration with graphics.
> - Test tools (Intel BAT and others).
> - BATCH flag.
> - ACPI simple-card and general generic card support.
> - Topology & media controller integration.
> - Kernel tinification.
> - Android <-> alsa-lib configuration translation.
> - HDA restructuring.
> - PCM core simplification - the code is currently quite complex!
> - Soundwire driver support plans.
Few more topics:
- tinycompress release with alsa lib. And when is next alsa-lib release?
- ASoC Multichannel support. We have talked about it, I want recheck assumption
before we implement something
- ASoC/DAPM Changes we would like to do:
- add kcontrol suport for PGA so that we cna add user controls for DSPs
- add internal sink in DAPM for DSPs, like siggen
- Fix TLV byte controls
- Discuss BE-BE loops
Thanks
--
~Vinod
next prev parent reply other threads:[~2015-10-06 10:59 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 [this message]
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
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=1444129142.25504.7.camel@intel.com \
--to=vinod.koul@intel.com \
--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