[BUG] ASoC: tas2783-sdw: 3-field vs 4-field firmware filename mismatch on HP OmniBook (8EA1-8EA8, etc.)

From: Michael Coppola

Date: Tue Nov 17 2026 - 01:44:21 EST


Hi Baojun, Mark, and all,

I am testing an HP OmniBook X Flip Laptop 14-kb0xxx (Intel Core Ultra
Series 3 / Panther Lake, PCI 8086:e428, subsystem 103c:8ea4), which has
two TI TAS2783 smart amplifiers on SoundWire link 2 (UIDs 0x9 and 0xC)
and a Realtek RT712-VB on SoundWire link 3.

In sound/soc/codecs/tas2783-sdw.c, tas_generate_fw_name() formats a
3-field firmware filename:

scnprintf(name, size, "%04X-%1X-%s%1X.bin",
pci->subsystem_device, bus->link_id,
fw_uid_prefix, unique_id);

On 103c:8ea4 (link 2, UIDs 0x9 and 0xC), the driver requests:
- 8EA4-2-0x9.bin (fallback: 8EA4-2-9.bin)
- 8EA4-2-0xC.bin (fallback: 8EA4-2-C.bin)

However, linux-firmware (commit 43cc9de7, "linux-firmware: Add firmware
for new soundwire projects") ships 4-field filenames that include a
speaker vendor ID field (<SSID>-<spk_id>-<link>-0x<uid>.bin):
- ti/audio/tas2783/8EA4-0-2-0x9.bin
- ti/audio/tas2783/8EA4-0-2-0xC.bin
- ti/audio/tas2783/8EA4-1-2-0x9.bin
- ti/audio/tas2783/8EA4-1-2-0xC.bin
(and similarly for 8EA1, 8EA2, 8EA5, 8EA6, 8EA7, 8EA8, 1954, 1964, 1994,
1AC4, 1AD4, 1B04, 1B94, 9013, 9014, 9015, 9026).

As a result, request_firmware_nowait() fails with -ENOENT out of the box
on all of these boards unless the user manually creates symlinks in
/lib/firmware (e.g. 8EA4-2-0x{9,C}.bin ->
ti/audio/tas2783/8EA4-0-2-0x{9,C}.bin).

On HP systems, the speaker ID (0 = AAC, 1 = FG) is stored in the UEFI
variable HPSpeakerID-c49593a4-d099-419b-a2c3-67e980e61d1e (as ASCII '0'
or '1'). Should tas_generate_fw_name() read HPSpeakerID (or fall back to
"%04X-0-%1X-0x%1X.bin" when the 3-field binary is not present), or how is
the 4-field filename intended to be resolved upstream? I would be happy to
send and test a patch for this on 8EA4.

Thanks,
Michael Coppola