From: Pierre-Louis Bossart <pierre-louis.bossart@linux.intel.com>
To: Bard Liao <bardliao@realtek.com>, Mark Brown <broonie@kernel.org>,
Takashi Iwai <tiwai@suse.de>, Liam Girdwood <lgirdwood@gmail.com>,
Jaroslav Kysela <perex@perex.cz>
Cc: "alsa-devel@alsa-project.org" <alsa-devel@alsa-project.org>
Subject: Re: [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin
Date: Mon, 27 Jul 2015 18:05:15 -0500 [thread overview]
Message-ID: <55B6B92B.5010305@linux.intel.com> (raw)
In-Reply-To: <ABFD875FF5FB574BA706497D987D48D70108CC68@RTITMBSV03.realtek.com.tw>
On 7/21/15 6:29 AM, Bard Liao wrote:
>> -----Original Message-----
>> From: Mark Brown [mailto:broonie@kernel.org]
>> Sent: Tuesday, July 14, 2015 11:04 PM
>> To: Takashi Iwai; Liam Girdwood; Jaroslav Kysela
>> Cc: alsa-devel@alsa-project.org
>> Subject: [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin
>>
>> Like previous years, we're going to hold a meeting to discuss lowlevel
>> audio on Linux. This will be held the day after ELC Europe on 8th
>> October at CCD (The Convention Centre) in Dublin.
>>
>> If you're interested please sign up in the attendee list:
>>
>> https://docs.google.com/spreadsheets/d/1bi-8GHsqlzt41FR20WiMuWILe_
>> cZowFireVMBd-QM8Q/edit?usp=sharing
>>
>> and please follow up to this mail with any topics you'd like to see raised so
>> we can start collecting them (probably another Google doc will be
>> forthcoming for them).
>>
>> Previously suggested topics include:
>>
>> - Reducing kernel size for IoT applications
>> - ACPI simple-card
I think we should also share findings on DeviceTree vs. ACPI support for
machine drivers and subnodes.
>> - Testing tools
>>
>
> Could we also discuss the driver support for MIPI SoundWire ?
Yes we should. This might require additional time or a dedicated session
though.
> Is there any existing code in kernel using MIPI SoundWire?
Not yet, this is work-in-progress. Note that a list of device properties
has already been defined and is available to MIPI contributors, it'll be
released more widely at some point.
>
>> Thanks,
>> Mark
>>
>> ------Please consider the environment before printing this e-mail.
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
>
next prev parent reply other threads:[~2015-07-28 14:21 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-07-14 15:03 [REANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin Mark Brown
2015-07-14 16:04 ` Alexander E. Patrakov
2015-07-14 16:17 ` Mark Brown
2015-07-14 16:36 ` Alexander E. Patrakov
2015-07-14 17:05 ` Alexander E. Patrakov
2015-07-27 23:26 ` Pierre-Louis Bossart
2015-07-18 17:07 ` Vinod Koul
2015-09-10 21:35 ` Eric Laurent
2015-09-14 18:02 ` Mark Brown
2015-09-14 18:10 ` Eric Laurent
2015-07-21 11:29 ` Bard Liao
2015-07-27 23:05 ` Pierre-Louis Bossart [this message]
2015-08-03 3:15 ` Vinod Koul
2015-09-22 8:49 ` Arun Raghavan
2015-10-03 16:13 ` Takashi Iwai
2015-10-04 22:57 ` Mark Brown
2015-10-04 23:19 ` Mark Brown
2015-10-04 9:24 ` Arun Raghavan
2015-08-01 7:37 ` Lars-Peter Clausen
2015-08-03 3:21 ` Vinod Koul
2015-08-04 16:13 ` Mark Brown
2015-08-05 2:56 ` Vinod Koul
2015-08-05 9:39 ` Mark Brown
2015-08-03 19:11 ` Pierre-Louis Bossart
2015-08-04 16:03 ` Mark Brown
2015-08-04 18:50 ` 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=55B6B92B.5010305@linux.intel.com \
--to=pierre-louis.bossart@linux.intel.com \
--cc=alsa-devel@alsa-project.org \
--cc=bardliao@realtek.com \
--cc=broonie@kernel.org \
--cc=lgirdwood@gmail.com \
--cc=perex@perex.cz \
--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.