Wim Taymans 0f6aae914f alsa: don't add MAX_LATENCY when using IRQ scheduling ... The Max latency property only works for timer based scheduling so that we don't select a quantum larger than we can handle in our buffer. With IRQ based scheduling this does not make sense because we will reconfigure the buffer completely when we change quantums and so the currently selected buffer size does not limit the latency in any way. Fixes #4877		2025-09-02 18:52:38 +02:00
..
examples	spa: examples: local-libcamera: pass camera id to the plugin	2025-08-01 15:40:28 +00:00
include	ump: make sure we set the group correctly	2025-08-29 16:59:38 +02:00
include-private/spa-private	spa: move dbus helpers out of bluez plugin	2024-02-05 13:03:20 +00:00
lib	pod: rework the parser	2025-07-29 15:15:02 +02:00
plugins	alsa: don't add MAX_LATENCY when using IRQ scheduling	2025-09-02 18:52:38 +02:00
tests	pod: check that choices are not empty	2025-07-15 10:13:18 +02:00
tools	meson.build: make spa-json-dump available for subprojects	2025-07-23 12:19:21 +00:00
meson.build	meson: Always use -fno-strict-aliasing and -fno-strict-overflow	2025-07-24 07:30:28 +00:00