Planning for UCM support for Android on Linaro dev boards

Registered by Kurt Taylor on 2011-10-17

Planning session for work needed to support UCM on Android for the Linaro development boards.

Blueprint information

Status:
Complete
Approver:
Ilias Biris
Priority:
Medium
Drafter:
Kurt Taylor
Direction:
Needs approval
Assignee:
None
Definition:
Discussion
Series goal:
Accepted for trunk
Implementation:
Implemented
Milestone target:
milestone icon backlog
Started by
Jesse Barker on 2012-11-14
Completed by
Jesse Barker on 2012-11-14

Related branches

Sprints

Whiteboard

1) Brief UCM background - bring application configuration of audio h/w to Android, ASoC driven simplification, settled on Tinyasla instead of alsa-lib, config file support for ARM (Panda, i.MX53 - need Origen, Snowball)
2) Enumerate dev boards and priority - Panda (TI), Origen (Samsung), i.MX53 (Freescale), Snowball (ST-E) - needs ALSA. BeagleXM, Others ?, Currently only Nexus S.
3) Need for common configuration files, or can they be close? OK to just tolerate differences?
4) libaudio support for existing hardware via AudioHardware and Policy, Tinyalsa/Tinyhardware seperate stack for UCM - integrated, or separate?
5) Prioritizing steps to deployment - port, Android environment, development board support, Ubuntu dev - pulseaudio/tinyalsa, beyond basics, additional features, test cases and applications

Notes from the session:
http://summit.linaro.org/uds-p/meeting/19347/linaro-gfxmm-audio-ucm4android/

List of action points
----
#ACTION: Kurt to provide a link for patch for Android source code

#ACTION: Kurt to provide a link to the configuration files and examples
of new vs. old formats and brief background paragraphs in the
specification wiki page

#ACTION: Kurt - get progress on the Android audio stack with Vishal
(code based on Alsa and libaudio)

#ACTION: Kurt to check with pabhishek on what could be the use cases for
testing (Android QA)

#ACTION: Kurt to provide a reference for the jack detection discussion

#ACTION: Ilias/Kurt to check what configuration files could be disclosed
from the vendors side.

(?)

Work Items

This blueprint contains Public information 
Everyone can see this information.