From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Mark Brown <broonie@kernel.org>, alsa-devel@alsa-project.org
Cc: Takashi Iwai <tiwai@suse.de>,
Liam Girdwood <liam.r.girdwood@linux.intel.com>,
Curtis Malainey <cujomalainey@google.com>
Subject: Re: [alsa-devel] [ANNOUNCE] 2019 Linux Audio miniconference
Date: Wed, 9 Oct 2019 14:16:21 -0500 [thread overview]
Message-ID: <e6539727-429d-8cd0-af01-d23a4b8af89b@linux.intel.com> (raw)
In-Reply-To: <20191009181356.GO2036@sirena.org.uk>
On 10/9/19 1:13 PM, Mark Brown wrote:
> Hi,
>
> As in previous years we're going to have an audio miniconference so we can
> get together and talk through issues, especially design decisions, face to
> face. This year's event will be held on October 31st in Lyon, France,
> the day after ELC-E. This will be held at the Lyon Convention Center (the
> ELC-E venue) and will be free of charge to attend, generously
> sponsored by Intel.
>
> Thus far for the agenda we have:
>
> - Use case management enhancements (Curtis)
> - DSP framework integration (Liam?)
> - Soundwire status (Pierre?)
I am unfortunately not going to make it this year due to conflicts.
I will repost the 50-odd SoundWire patches we have when Vinod is back at
his desk. For now we have most of the issues ironed out, with all known
race conditions sorted out and with audio streaming to/from SoundWire
links on CometLake, IceLake and TigerLake, with 4 different codecs from
Realtek supported. We are trying to clean-up the last suspend/resume
issues in collaboration with Realtek.
The latest code is here if anyone is interested:
https://github.com/thesofproject/linux/tree/integration/soundwire-latest
The only big topic is the multi-cpu support. We will need to support
playback synchronized on multiple amplifiers/speakers, and our plan was
to create a dailink that connect 2 CPU dais (possibly dealing with
different links) to 2 codec DAIs.
The other interesting topic is the likely mix of SoundWire, I2S and yes
HDaudio links for some platforms. This will make the autodetection a bit
complex, not to mention all the possible topology variants. Ideally we
should limit this complexity by exposing different cards for the
different links with Ranjani's work on MFD.
We are also planning to try and use the Up Extreme board which exposes 2
SoundWire links on the 40-pin connector, this will make it simpler for
developers to get access to an open SoundWire-enabled platform and
extend the pool of codecs supported, as we did with Minnow and Up boards.
-Pierre
_______________________________________________
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-09 19:19 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-10-09 18:13 [alsa-devel] [ANNOUNCE] 2019 Linux Audio miniconference Mark Brown
2019-10-09 18:48 ` Daniel Baluta
2019-10-10 15:57 ` Mark Brown
2019-10-10 16:43 ` Pierre-Louis Bossart
2019-10-10 19:43 ` Daniel Baluta
2019-10-09 19:16 ` Pierre-Louis Bossart [this message]
2019-10-25 10:05 ` Vinod Koul
2019-10-14 19:47 ` Liam Girdwood
2019-10-14 20:16 ` Curtis Malainey
2019-10-15 20:11 ` Mark Brown
2019-10-15 20:11 ` Mark Brown
2019-10-22 18:59 ` Mark Brown
2019-10-23 9:20 ` Jerome Brunet
2019-10-23 16:53 ` Mark Brown
2019-10-24 14:20 ` Patrick Lai
2019-10-24 14:31 ` Pierre-Louis Bossart
2019-10-25 9:45 ` Vinod Koul
2019-10-25 14:27 ` Pierre-Louis Bossart
2019-10-25 17:26 ` Patrick Lai
2019-10-24 19:15 ` 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=e6539727-429d-8cd0-af01-d23a4b8af89b@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@kernel.org \
--cc=cujomalainey@google.com \
--cc=liam.r.girdwood@linux.intel.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 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.