Public bug reported: [Impact] Speakers do not show up on HP systems (CID: 202512-38250) with four TAS2783 SoundWire speaker amplifiers. The audio detect_sources test fails.
Error log from the test: media.class:[Audio/Source] couldn't find The machine driver's card->components string never includes "spk:tas2783" because the TAS2783 entry in sdw_utils is missing .component_name. WirePlumber/PipeWire cannot match the speaker codec, so only a Dummy Output is shown and no Speaker sink or audio source is exposed. Happens with updated BIOS that already fixes the SDCA function type. [Fix] Add the missing component_name string to the TAS2783 entry in codec_info_list in sound/soc/sdw_utils/soc_sdw_utils.c: .component_name = "tas2783", With this, card->components includes "spk:tas2783" so WirePlumber/UCM can match the codec and build the Speaker device. Upstream commit: 79bec46381942 ASoC: sdw_utils: Add missed component_name strings for TI amps Merged in Linus' tree and linux-next for v7.1 (no released tag yet). Patch: https://patch.msgid.link/[email protected] This is one of three pieces of the full fix. The BIOS update adds the missing mipi-sdca-control-dc-value for SDCA function type. This kernel patch exposes the codec name. A separate userspace patch (alsa-ucm-conf tas2783.conf, TI PR #812) provides the UCM profile. This SRU is for the kernel piece only. [Test Plan] On a HP system with 4x TAS2783 amps, BIOS Y90 99.15.23 or newer: 1. Check the speaker codec is matched: $ wpctl status Without patch: no Speaker device, only Dummy Output. With patch: a Speaker sink appears under Audio. 2. Run the failing test: $ sudo checkbox-cli run com.canonical.certification::audio/detect_sources Without patch: fails with "media.class:[Audio/Source] couldn't find". With patch: passes. Note: full speaker playback also needs the tas2783.conf UCM profile installed. [Where problems could occur] Could break ASoC SoundWire machine setup. The change only adds a string to one codec entry, so the risk is small. If the component_name does not match the UCM profile name, the Speaker still will not be created and the test keeps failing (no worse than today). If the component matching picks up the codec with a wrong UCM profile, there could be no speaker output or wrong default audio routing after boot. ** Affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-7.0 (Ubuntu) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Affects: linux-oem-7.0 (Ubuntu Noble) Importance: Undecided Status: Invalid ** Affects: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided Status: Invalid ** Affects: linux-oem-7.0 (Ubuntu Resolute) Importance: Undecided Assignee: AceLan Kao (acelankao) Status: In Progress ** Also affects: linux-oem-6.17 (Ubuntu) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu Resolute) Importance: Undecided Status: New ** Also affects: linux-oem-6.17 (Ubuntu Noble) Importance: Undecided Status: New ** Also affects: linux-oem-7.0 (Ubuntu Noble) Importance: Undecided Status: New ** Changed in: linux-oem-6.17 (Ubuntu Noble) Status: New => In Progress ** Changed in: linux-oem-6.17 (Ubuntu Resolute) Status: New => Invalid ** Changed in: linux-oem-7.0 (Ubuntu Noble) Status: New => Invalid ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Status: New => In Progress ** Changed in: linux-oem-7.0 (Ubuntu Resolute) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.17 (Ubuntu Noble) Assignee: (unassigned) => AceLan Kao (acelankao) ** Changed in: linux-oem-6.17 (Ubuntu) Status: New => Invalid ** Changed in: linux-oem-7.0 (Ubuntu) Status: New => Invalid -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/2164504 Title: Speakers not detected on HP systems with TI TAS2783 SoundWire amps To manage notifications about this bug go to: https://bugs.launchpad.net/ubuntu/+source/linux-oem-6.17/+bug/2164504/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
