summaryrefslogtreecommitdiffstats
path: root/mixer-binding
AgeCommit message (Collapse)AuthorFilesLines
2019-04-02pre-init: Add a config detectionPierre MARZIN1-2/+37
Scan the loaded modules during pre-init to know which config file to load. If Avirt core module is loaded then load the avirt config file. Otherwise, load the default config file. Change the config file name in order to use the prefix to select them. Change-Id: I8f9d5ed568fa20b06ac3bef443a2392de26c8235 Signed-off-by: Pierre MARZIN <pierre.marzin@iot.bzh>
2019-01-24Git submodule migration to separated librariesRomain Forlot2-19/+13
- Replace controller binder functions definition with the binder ones. and remove the last used submodules to use the separated libraries. - Add liburcu as a project dependency in addition to the others ones. Bug-AGL: SPEC-2139 Change-Id: If46eed24018e28e58d1e62397f4355d2aa46a58e Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
2018-10-31Migrate app-templates to CMake moduleapp-templates-migrationRomain Forlot1-1/+0
Bug-AGL SPEC-1682 Change-Id: Ia8d8bc6b614065d9cc9ab73a33d4643267686bcf Signed-off-by: Romain Forlot <romain.forlot@iot.bzh>
2018-08-31Added bluez sound playback supportThierry Bultel1-14/+16
This adds sound playback for incoming sound from connected bluetooth devices. In this version, the softmixer relies on a modified bluez-alsa version (https://github.com/iotbzh/bluez-alsa), that provides an ioplug PCM bluezalsa connection proxy. The softmixer api has a new verb to dynamically set the device to listen to: afb-client-demo ws://localhost:1234/api?token=\uuid=123 smixer bluezalsa_dev '{"interface":"hci0", "device":"F6:32:15:2A:80:70", "profile":"a2dp"}' In this way it is possible to switch from a bluezalsa audio source to another without any further configuration. For now, only interface hci0 is supported. This commit also migrates the softmixer binding to API v3 Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-07-11stops the read/write loop when the stream is mutedThierry Bultel1-2/+9
when the stream is muted (due to the configuration, or due to a HAL request), the read/write loop is stopped. The benefit is that muting will work with capture devices that do not implement the mute in their driver. The inconvenient of stopping the read loop is that it has made appear an unexpected side-effect: the poll on capture does not trig for further incoming frames. The workaround is to completely close, then reopen and configure the capture PCM. Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-07-03Uses the APIv3 compatibility to vdynThierry Bultel1-2/+1
Uses the new compatibility for vdyn based on V3 Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-06-10Cleanup and added return of previous volume when setting new valuefulup1-1/+1
2018-06-06Move smixer API create+attach into controller onload sectionfulup1-21/+9
2018-06-04Move to Dynamic Mixer API (work in progress)Fulup Ar Foll1-2/+2
2018-05-18Implements volume rampingFulup Ar Foll1-1/+1
2018-05-17Initial version with dynamic APIsFulup Ar Foll1-2/+3
2018-05-16Move to new config syntaxfulup1-1/+1
2018-05-14Move to new Romain controller versionfulup1-0/+7
2018-04-30On going effort, now load and support LUA+C pluginFulup Ar Foll2-2/+3
2018-04-29Hack config to bypass limitation and load pluginFulup Ar Foll1-8/+4
2018-04-29Initial push work in progressFulup Ar Foll3-0/+230