From: Mark Brown <broonie@kernel.org>
To: Liam Girdwood <liam.r.girdwood@linux.intel.com>
Cc: Takashi Iwai <tiwai@suse.de>, alsa-devel@alsa-project.org
Subject: Re: [ANNOUNCE] 2018 Linux Audio miniconference
Date: Tue, 28 Aug 2018 20:13:57 +0100 [thread overview]
Message-ID: <20180828191357.GN2414@sirena.org.uk> (raw)
In-Reply-To: <ee7acc7f7754dd76b730874bae413a7f3c9804cc.camel@linux.intel.com>
[-- Attachment #1.1: Type: text/plain, Size: 610 bytes --]
On Thu, Aug 23, 2018 at 12:18:06PM +0100, Liam Girdwood wrote:
> I'm also thinking soundwire, AVB (audio over ethernet) and audio virtualisation
> as other topics too.
Yes, it'd be especially good to get an uodate on where SoundWire's at,
especially with regard to things like routing.
> Fwiw, we should be able to virtualise SOF soon so it would be probably good to
> discuss audio virtualisation in general and the pain points for virtualising
> audio around latency and reducing buffer copies.
Is there any hardware support for this in your audio blocks or is it
currently pure software?
[-- Attachment #1.2: signature.asc --]
[-- Type: application/pgp-signature, Size: 488 bytes --]
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2018-08-28 19:14 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-08-10 11:06 [ANNOUNCE] 2018 Linux Audio miniconference Mark Brown
2018-08-16 16:02 ` Mark Brown
2018-08-23 11:18 ` Liam Girdwood
2018-08-27 12:37 ` Vinod
2018-08-28 8:59 ` Charles Keepax
2018-08-28 19:13 ` Mark Brown [this message]
2018-10-12 5:41 ` Vinod
2018-08-26 18:33 ` Fulup Ar Foll
2018-08-28 19:10 ` Mark Brown
2018-10-10 16:33 ` Eric Laurent
2018-10-16 14:08 ` 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=20180828191357.GN2414@sirena.org.uk \
--to=broonie@kernel.org \
--cc=alsa-devel@alsa-project.org \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).