]> git.ipfire.org Git - thirdparty/kernel/stable.git/commit
ALSA: hda/tas2781: fix speaker id retrieval for multiple probes
authorAntheas Kapenekakis <lkml@antheas.dev>
Sun, 26 Oct 2025 19:16:34 +0000 (20:16 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Thu, 18 Dec 2025 13:03:42 +0000 (14:03 +0100)
commit3646c928bb77c28bd79f8e1893d32db49230b657
tree38d6a2abc6fa8c8f9abd24cabc78d43b4b77d76e
parentacacb5b7109acb83b6154b4654acdbec6aa5f54f
ALSA: hda/tas2781: fix speaker id retrieval for multiple probes

commit 945865a0ddf3e3950aea32e23e10d815ee9b21bc upstream.

Currently, on ASUS projects, the TAS2781 codec attaches the speaker GPIO
to the first tasdevice_priv instance using devm. This causes
tas2781_read_acpi to fail on subsequent probes since the GPIO is already
managed by the first device. This causes a failure on Xbox Ally X,
because it has two amplifiers, and prevents us from quirking both the
Xbox Ally and Xbox Ally X in the realtek codec driver.

It is unnecessary to attach the GPIO to a device as it is static.
Therefore, instead of attaching it and then reading it when loading the
firmware, read its value directly in tas2781_read_acpi and store it in
the private data structure. Then, make reading the value non-fatal so
that ASUS projects that miss a speaker pin can still work, perhaps using
fallback firmware.

Fixes: 4e7035a75da9 ("ALSA: hda/tas2781: Add speaker id check for ASUS projects")
Cc: stable@vger.kernel.org # 6.17
Signed-off-by: Antheas Kapenekakis <lkml@antheas.dev>
Reviewed-by: Baojun Xu <baojun.xu@ti.com>
Signed-off-by: Takashi Iwai <tiwai@suse.de>
Link: https://patch.msgid.link/20251026191635.2447593-1-lkml@antheas.dev
Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
include/sound/tas2781.h
sound/hda/codecs/side-codecs/tas2781_hda_i2c.c