summaryrefslogtreecommitdiffstats
path: root/meta-audio-4a-framework/recipes-connectivity/bluez-alsa
AgeCommit message (Collapse)AuthorFilesLines
2019-06-11Supporting commits for the switch to pipewireJan-Simon Möller5-1086/+0
We move all components around meta-audio-soundmanager-framework to that layer (still kept on request). We deprecate the meta-audio-4a-framework layer for Happy Halibut. Bug-AGL: SPEC-2473 Change-Id: I2a7c9d815801a3f8ea80943165ea6fd1422533ea Signed-off-by: Jan-Simon Möller <jsmoeller@linuxfoundation.org>
2019-02-13bluez-alsa: added a patch of bug fix in the ioplugThierry Bultel2-1/+37
This adds an early patch for fixing the "stuck poll" issue when using the PCM ioplug. This patch has already been discussed with the bluez-alsa maintainer, and submitted as a pull request: https://github.com/Arkq/bluez-alsa/pull/184 Change-Id: I3cec6625b501025286878d9da2c782014b224d41 Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2019-02-01bluez-alsa: updated patches due to latest bumpThierry Bultel6-269/+211
This updates the needed patches for 4a. The latest bump (version of 2019-01-17) has make one of the previous patch obsolete (SIGSEGV when closing the PCM), thus the patch has simply been removed. Also add a patch for having bluez-alsa request a name on dbus. BUG-AGL: SPEC-2126 Change-Id: I351b55e0d440f8f271ccb14a0d51111570659026 Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-12-26bluez-alsa: Added a patch to fix the crash at PCM closeThierry Bultel2-2/+181
This fixes the random crash at PCM close Change-Id: I373e4b7e55d6d7d4c3be4a4a7a9f460c00758215 Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-12-20bluez-alsa: removed the PCM hack, and build a shared libThierry Bultel6-1063/+924
This removes the deprecated PCM proxy hack, and brings mandatory features for the softmixer. This change applies on top of the latest bluez-alsa master of 2018-12-04 and brings 3 patches: 1) builds a shared library and links bluez-alsa and ioplug controls & pcm to it. 2) func log by default 3) increase the number of max connections from clients (pcm & ctrls) ----- Upstream status for the patches: 1) pending. Based on a submitted PR that is not clean enough and that the maintainer does not want to take before at least 6 months https://github.com/Arkq/bluez-alsa/pull/95 2) pending. Was submitted as part of the Ofono support in bluez-alsa, but was not retained. See the original PR for Ofono for that. 3) pending. The maintainer is OK with this but wants to refactor the client-server protocol in the coming months. In a private mail of 12/06/2018: "Yes, you can increase this hardcoded limit as a temporary workaround. I've put in there (and made it rather low) as a reminder, that clients are stored in the list, which might not be optimal for larger number of connected clients. In the future bluealsa will support audio mixing, so connecting many clients to a single transport will be a common case. So, I've thought about incorporating more efficient structure for storing (in particular searching) connected client - something with log(n) search complexity. Then, it might be worth to implement this container to be dynamic with an upper capacity limit (which might be high, like 200-300 clients)." Change-Id: Ia771613a7a83cc9ed6108399cdaacdeda603d39b Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-09-11bluez-alsa: added patch for null deviceThierry Bultel2-0/+47
This closes the transport connection when a null device is specified. Change-Id: I6d69c68a2ca91bd9fb3d7fdf51f470f243e76d5f Signed-off-by: Thierry Bultel <thierry.bultel@iot.bzh>
2018-08-31[4A/bluez-alsa]: use temporary solution pcm alsa-proxyStephane Desneux2-0/+1021
This plugin always keeps the opened PCM in a consistent state for the sound application, despite of bluez-alsa server or device disconnection. Bug: SPEC-1679 Change-Id: I0caaa6abe6fb9133b4d43479d452e542a04620c3 Signed-off-by: Ronan Le Martret <ronan.lemartret@iot.bzh> Signed-off-by: Stephane Desneux <stephane.desneux@iot.bzh>