From: Takashi Iwai <tiwai@suse.de>
To: Mark Brown <broonie@kernel.org>
Cc: alsa-devel@alsa-project.org,
Curtis Malainey <cujomalainey@google.com>,
Patrick Lai <plai@codeaurora.org>,
Daniel Baluta <daniel.baluta@gmail.com>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Jerome Brunet <jbrunet@baylibre.com>
Subject: Re: [alsa-devel] [ANNOUNCE] Draft schedule for 2019 Linux Audio miniconference
Date: Mon, 28 Oct 2019 21:26:00 +0100 [thread overview]
Message-ID: <s5hk18oty5j.wl-tiwai@suse.de> (raw)
In-Reply-To: <20191028185112.GA22457@sirena.co.uk>
On Mon, 28 Oct 2019 19:51:12 +0100,
Mark Brown wrote:
>
> The agenda is looking pretty full now, what we've got so far is:
>
> - Use case management enhancements (Curtis)
> - DSP framework integration (Liam)
> - SOF integration with ACPI and DT (Daniel)
> - SOF support for non-modular drivers (Daniel)
> - Gapless compressed playback (Patrick)
> - Soundwire status (Liam?)
> - Multi-CPU support
> - Mixing with HDA/I2S in a single system
> - PCM issues (Patrick)
> - PCM device volume control
> - Attaching timestamps to buffers
> - Virtualization (Liam)
> - User experiences (Jerome)
> - Unified graph (Patrick)
> - Componentisation status/plans (Me)
May I add one more topic, about the standardization / conformance test
of kcontrol strings? Sorry for the late action.
> If you're planning to attend please fill out the form here:
>
> https://docs.google.com/forms/d/e/1FAIpQLSd6FV-tWYZ1fHlCmyzQhG98OtYH9W9GX-1dQ88mnLxVRGyPww/viewform?usp=sf_link
I suppose this is needed only for those who still hasn't registered,
right?
thanks,
Takashi
_______________________________________________
Alsa-devel mailing list
Alsa-devel@alsa-project.org
https://mailman.alsa-project.org/mailman/listinfo/alsa-devel
next prev parent reply other threads:[~2019-10-28 20:27 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-28 18:51 [alsa-devel] [ANNOUNCE] Draft schedule for 2019 Linux Audio miniconference Mark Brown
2019-10-28 20:26 ` Takashi Iwai [this message]
2019-10-29 11:05 ` 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=s5hk18oty5j.wl-tiwai@suse.de \
--to=tiwai@suse.de \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cujomalainey@google.com \
--cc=daniel.baluta@gmail.com \
--cc=jbrunet@baylibre.com \
--cc=liam.r.girdwood@linux.intel.com \
--cc=plai@codeaurora.org \
/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