From: Liam Girdwood <liam.r.girdwood@linux.intel.com>
To: Mark Brown <broonie@kernel.org>
Cc: Takashi Iwai <tiwai@suse.de>,
alsa-devel@alsa-project.org, Liam Girdwood <lgirdwood@gmail.com>
Subject: Re: [ANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin
Date: Fri, 24 Apr 2015 04:11:26 +0100 [thread overview]
Message-ID: <1429845086.2702.45.camel@loki> (raw)
In-Reply-To: <20150423205745.GH22845@sirena.org.uk>
On Thu, 2015-04-23 at 21:57 +0100, Mark Brown wrote:
> Hi,
>
> 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).
My initial topics would be :-
o Reducing alsa kernel and driver size for IoT devices with limited
DRAM. Look at Tinyalsa and salsalib too for IoT userspace.
o Generic machine drivers based on ACPI table data from multiple
devices. i.e. create a machine driver based on ACPI HW topology data
from codec and DSP drivers. This seems to be done for DT, so we probably
need to combine ACPI support into the existing code. The device property
API can be used to abstract any differences between reading data from DT
and ACPI. The difference with DT is that we will need to aggregate data
from the codec and DSP tables as we wont have any ACPI table data for a
machine driver device.
o Intels audio testing tool (currently called BAT). What new features
are needed/wanted most. This is a tool Intel are working on for
automated testing of audio drivers and sound servers. It will be GPL
licensed and is intended to be part of alsa-utils when ready. I'll make
an announcement with more details and a git repo in the next few weeks.
We are using this internally atm for testing current upstream SST
drivers.
Liam
>
> Thanks,
> Mark
> _______________________________________________
> Alsa-devel mailing list
> Alsa-devel@alsa-project.org
> http://mailman.alsa-project.org/mailman/listinfo/alsa-devel
prev parent reply other threads:[~2015-04-24 3:11 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-09-05 16:19 [ANNOUNCE] Audio Mini Summit 2014, Oct. 14, Düsseldorf, Germany Takashi Iwai
2015-04-23 20:57 ` [ANNOUNCE] Audio Mini Summit 2015, 8th October, Dublin Mark Brown
2015-04-24 3:11 ` Liam Girdwood [this message]
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=1429845086.2702.45.camel@loki \
--to=liam.r.girdwood@linux.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