bluetooth.conf: open secondary access to pipewire 39/28639/3
authorAshok Sidipotu <ashok.sidipotu@collabora.com>
Thu, 13 Apr 2023 16:20:08 +0000 (21:50 +0530)
committerJan-Simon Moeller <jsmoeller@linuxfoundation.org>
Fri, 14 Apr 2023 10:40:28 +0000 (10:40 +0000)
with out having a secondary access to pipewire(export core), wireplumber creates
bluetooth device objects as well as access the existing pipewire objects using
the same pipewire connection, which can some times create race conditions.

Enable export core, so that wireplumber bluetooth monitor has access to both the
regular core and the export core.

Bug-AGL: SPEC-4750
Change-Id: I0db9b276ecd6972294c36722bf5a31c5ac00f186
Signed-off-by: Ashok Sidipotu <ashok.sidipotu@collabora.com>
Reviewed-on: https://gerrit.automotivelinux.org/gerrit/c/AGL/meta-agl/+/28639
Reviewed-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
Tested-by: Jan-Simon Moeller <jsmoeller@linuxfoundation.org>
meta-pipewire/recipes-multimedia/wireplumber/wireplumber-config-agl/bluetooth.conf

index ebd0b60..9077e3f 100644 (file)
@@ -6,7 +6,7 @@ context.properties = {
   application.name = "WirePlumber Bluetooth"
   log.level = 2
   wireplumber.script-engine = lua-scripting
-  wireplumber.export-core = false
+  wireplumber.export-core = true
 
   #mem.mlock-all = false
   #support.dbus  = true