I got a ping on patch pilot duty, sadly on my ping back if they would be available for questions if I find more that needs to be sorted out was unanswered. So I need to carry all into this bug.
This is kind of a log of my own understanding process, feel free to ignore it: Proposed change: - It adds a few regex expressions to allow matching the new HW - and then configuration for those new matches - Accepted upstream - Other than fixup releases Upstream seems to tag two releases per year, one in Q2 one in Q4 - Due to that I'd this to be in a new revision v1.2.11 by May 2024 - that might be worth to mention for packages to know when they will be able to drop it Paride and Athos guided you to correctly obey the usual "fix -devel first" rule and due to noble being new that you need to start there. We are adding one particular device, but I see that due to having added Ubuntu delta in the past we have not yet picked up 1.2.10 which would have picked up plenty of other fixes and devices. => https://github.com/alsa-project/alsa-ucm-conf/releases/tag/v1.2.10 alsa-ucm-conf | 1.2.10-1 | unstable | source, all alsa-ucm-conf | 1.2.9-1ubuntu3 | noble | source, all The SRU fix is fine, those are meant to be surgical based on the need of our users, but for noble it feels we should aim for 1.2.10 + this. Checking who usually did that, ah Jürg and Ethan - fine we can ask them for opinions as they might know the subject matter. Great, so I'd propose we combine a merge of 1.2.10 with your fix on top. -- You received this bug notification because you are a member of Kernel Packages, which is subscribed to alsa-ucm-conf in Ubuntu. https://bugs.launchpad.net/bugs/2042902 Title: ucm2: soundwire: add rt713 SDCA device Status in OEM Priority Project: In Progress Status in alsa-ucm-conf package in Ubuntu: Fix Committed Status in alsa-ucm-conf source package in Jammy: New Status in alsa-ucm-conf source package in Lunar: New Status in alsa-ucm-conf source package in Mantic: New Status in alsa-ucm-conf source package in Noble: Fix Committed Bug description: [ Impact ] Affects devices with SoundWire-Audio Codec-ALC713 and SoundWire-Jack Codec-ALC713. Without correct configurations in userspace above codecs cannot be used. Thus in Settings > Sound > Output test doesn't produce sounds and Input device is greyed out. [ Fix ] Adding rt713 config files in ucm2 will allow to utilize those codecs. Upstream commit added support: https://github.com/alsa-project/alsa-ucm-conf/pull/363 [ Test Plan ] Device with the soundwire card $ cat /proc/asound/cards 0 [sofsoundwire ]: sof-soundwire - sof-soundwire Intel Soundwire SOF Before fix: 1. $ alsactl init alsa-lib utils.c:364:(uc_mgr_config_load_into) could not open configuration file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf alsa-lib parser.c:77:(uc_mgr_config_load_file) error: failed to open file /usr/share/alsa/ucm2/sof-soundwire/rt713.conf: -2 alsa-lib main.c:1412:(snd_use_case_mgr_open) error: failed to import hw:0 use case configuration -2 Found hardware: "sof-soundwire" "Intel Meteorlake HDMI" "HDA:8086281d,80860101,00100000 cfg-spk:2 cfg-amp:2 hs:rt713-sdca spk:rt1316 mic:rt713-dmic" "" "" Hardware is initialized using a generic method 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw------,values=1 : values=off ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw------,values=1 : values=off After fix: after adding patch files 1. $ alsactl init alsa-lib main.c:779:(execute_sequence) exec '/bin/rm -rf /var/lib/alsa/card0.conf.d' failed (exit code 1) (note: assuming that failed to remove the empty directory is not a critical problem) 2. $ amixer contents ... numid=24,iface=MIXER,name='Headphone Switch' ; type=BOOLEAN,access=rw------,values=1 : values=on ... numid=33,iface=MIXER,name='IEC958 Playback Switch' ; type=BOOLEAN,access=rw------,values=1 : values=on [Where problems could occur] * This change adds new hardware support. * The change only adds new hardware support, it will not affect other codec device. To manage notifications about this bug go to: https://bugs.launchpad.net/oem-priority/+bug/2042902/+subscriptions -- Mailing list: https://launchpad.net/~kernel-packages Post to : kernel-packages@lists.launchpad.net Unsubscribe : https://launchpad.net/~kernel-packages More help : https://help.launchpad.net/ListHelp