As log information says, SBC log info have to have one of two subband count
values: 4 or 8, instead of subband flag.
---
src/modules/bluetooth/module-bluez5-device.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/src/modules/bluetooth/module-bluez5-device.c
b/src/modules/blue
This removes the need to hardcode the ELD device index in the path
configuration. The hardcoded values don't work with the Intel HDMI LPE
driver.
BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=100488
---
src/modules/alsa/alsa-mixer.c | 31 +++---
src/mo
These patches hopefully fix jack detection (and ELD information
querying too) for Intel HDMI LPE. I don't have the hardware myself, so
further testing would be very welcome. Hans, Takashi and Pierre, you're
in Cc, because you indicated in this[1] thread that you have the
hardware.
Testing instruct
We have so far assumed that HDMI always uses device indexes 3, 7, 8, 9,
10, 11, 12 and 13. These values are hardcoded in the path configuration.
The Intel HDMI LPE driver, however, uses a different device numbering
scheme.
This patch adds a new configuration option for mappings. The option
tells P
This removes the need to hardcode the PCM device index in the HDMI jack
names. The hardcoded values don't work with the Intel HDMI LPE driver.
BugLink: https://bugs.freedesktop.org/show_bug.cgi?id=100488
---
src/modules/alsa/alsa-mixer.c | 50 --
src/modul
On Mon, 2017-06-12 at 18:45 +0300, Tanu Kaskinen wrote:
> These patches hopefully fix jack detection (and ELD information
> querying too) for Intel HDMI LPE. I don't have the hardware myself, so
> further testing would be very welcome. Hans, Takashi and Pierre, you're
> in Cc, because you indicated
