From: Liam Girdwood <lrg@slimlogic.co.uk>
To: CE Linux Developers List <celinux-dev@tree.celinuxforum.org>,
linux-embedded <linux-embedded@vger.kernel.org>
Cc: Tim Bird <tim.bird@am.sony.com>,
Stefan Schmidt <stefan@datenfreihafen.org>,
Mark Brown <broonie@opensource.wolfsonmicro.com>,
Takashi Iwai <tiwai@suse.de>, Jaroslav Kysela <perex@perex.cz>,
alsa-devel <alsa-devel@alsa-project.org>
Subject: CELF Project Proposal - ALSA scenario/use case support
Date: Wed, 16 Dec 2009 17:26:53 +0000 [thread overview]
Message-ID: <1260984413.3525.351.camel@odin> (raw)
Summary: Complete ALSA hardware scenario/use case support in alsa-lib
and salsa-lib
Proposer: Liam Girdwood
Description:
Modern mobile devices are increasingly required to provide a rich set of
audio functionality required by today's applications. ALSA currently
lacks a portable and high level API to configure audio hardware function
and signal routing.
e.g. there is no portable method atm to configure the audio hardware to
make a "handset gsm phone call" or "handset voip phone call", etc.
This purpose of this project would be to complete the ALSA scenario
manager API and get it accepted upstream in alsa-lib and salsa-lib. The
code is nearly ready for upstream, with some work required on it's file
format as the main piece of outstanding work.
More Info:
** http://www.slimlogic.co.uk/?p=40
API header:
http://git.alsa-project.org/?p=alsa-lib.git;a=blob;f=include/ascenario.h;h=b1395515b035629d09cd9b3d3a224743053aa159;hb=ascenario
Development branch now hosted as alsa-lib branch here :-
** http://git.alsa-project.org/?p=alsa-lib.git;a=shortlog;h=ascenario
Scope: This project will probably take between 2 - 4 weeks.
Thanks
Liam
next reply other threads:[~2009-12-16 17:26 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-12-16 17:26 Liam Girdwood [this message]
2009-12-16 22:35 ` CELF Project Proposal - ALSA scenario/use case support Tim Bird
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=1260984413.3525.351.camel@odin \
--to=lrg@slimlogic.co.uk \
--cc=alsa-devel@alsa-project.org \
--cc=broonie@opensource.wolfsonmicro.com \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=linux-embedded@vger.kernel.org \
--cc=perex@perex.cz \
--cc=stefan@datenfreihafen.org \
--cc=tim.bird@am.sony.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).