pipewire/spa/plugins/bluez5
Pauli Virtanen 2fa3120486 bluez5: driver should produce buffers before ready
The graph cycle goes: driver timeout -> process output nodes -> process
driver node.  Hence, driver should produce buffers in the timeout,
otherwise there's one quantum extra latency.

Make the bluez5 media/sco sources as drivers put a buffer to io before
indicating ready, and as follower do it in process. Also make checks if
io == NULL, and don't set io->status to HAVE_DATA unless there really is
a buffer ready.
2022-10-22 15:23:06 +03:00
..
a2dp-codec-aac.c
a2dp-codec-aptx.c
a2dp-codec-caps.h
a2dp-codec-faststream.c
a2dp-codec-lc3plus.c
a2dp-codec-ldac.c
a2dp-codec-opus.c
a2dp-codec-sbc.c
backend-hsphfpd.c
backend-native.c
backend-ofono.c
bap-codec-caps.h
bap-codec-lc3.c
bluez-hardware.conf
bluez5-dbus.c
bluez5-device.c
codec-loader.c
codec-loader.h
decode-buffer.h
defs.h
hci.c
media-codecs.c
media-codecs.h
media-sink.c
media-source.c
meson.build
modemmanager.c
modemmanager.h
player.c
player.h
plugin.c
quirks.c
README-OPUS-A2DP.md
README-SBC-XQ.md
rtp.h
sco-io.c
sco-sink.c
sco-source.c
upower.c
upower.h