[SRU] alsa-utils: let alsactl support _boot section defined in ucm

[Hui Wang]

This patchset was backported from mainline alsa-utils 1.2.3, and
groovy already integrated alsa-utils 1.2.3, there is no need to SRU
this patchset to groovy, so only for focal.

[Impact]
We enabled 2 Dell soundwire audio machines, these machines depend on
ucm to make the audio work, and in the ucm, the _boot section defined
some amixers values for the 1st booting, these amixer values should
be set to audio driver at the 1st booting, otherwise the whole audio
doesn't work.

[Fix]
Backport some patches from mainline v1.2.3, these patches make the
alsactl support _boot section in the ucm, then the systemd will call
alsactl init after booting, the alsactl init will setting all amixers
defined in the _boot section of ucm.

[Test Case]
On the Dell soundwire audio machines, After booting up, run 'amixer
contents | less' to check all amixer values defined in the _boot
section of ucm, all values read from driver are same as the ones in
the ucm, test speaker/microphone/headset, all work well.

[Regression Risk]
This could introduce failure on runing 'alsactl init' for some machines,
then the amixers will not be initialized correctly, users will experience
all audio can't work like speaker doesn't output sound or microphone can't
record sound. But this regression possibility is very low, since We have
tested it both on soundwire machines and non-soundwire machines, all worked well.

[Hui Wang (hui.wang)]

This is the debdiff for focal, and since groovy already had the alsa-utils 1.2.3, there is no SRU for groovy.

thx.

[Sebastien Bacher (seb128)]

thanks, that has been uploaded to focal now

[Sebastien Bacher (seb128)]

(reuploaded after it got rejected, Hui the bottom line generated in your changelog is wrong ('+ -- Hui...') which leads to the .changes missing a date which makes launchpad reject the upload, it's something you might want to fix in your configuration

[Hui Wang (hui.wang)]

OK, got it. will investigate it and fix it in the future.

thx.

[Kai-Chuan Hsieh (kchsieh)]

@hui.wang

hello,

Do you know what blocks it?

Thanks,

[Hui Wang (hui.wang)]

Don't know

[Brian Murray (brian-murray)]

Hello Hui, or anyone else affected,

Accepted alsa-utils into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/alsa-utils/1.2.2-1ubuntu2 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

[Kai-Chuan Hsieh (kchsieh)]

Finish verification on CID: 202010-28346

kernel version: 5.6.0-1032-oem
BIOS version: 0.5.9

verify step:

1. add proposed channel
2. $ sudo apt install alsa-utils
3. Check alsa-utils version is 1.2.2-1ubuntu2
4. $ sudo rm /var/lib/alsa/asound.state
5. $ sudo sh -c 'echo b > /proc/sysrq-trigger'

After reboot, check if the ucm init.conf has been applied successfully.
The BootSequence in ucm config are applied successfully.

[Chris Halse Rogers (raof)]

The verification of the Stable Release Update for alsa-utils has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

[Launchpad Janitor (janitor)]

This bug was fixed in the package alsa-utils - 1.2.2-1ubuntu2

---------------
alsa-utils (1.2.2-1ubuntu2) focal; urgency=medium

  * d/p/0001-alsactl-init-iterate-through-all-cards-for-the-initi.patch
  * d/p/0002-alsactl-add-initial-support-for-UCM-init.patch
  * d/p/0003-alsactl-redirect-alsa-lib-errors.patch
  * d/p/0004-alsactl-add-D-argument-to-execute-also-the-UCM-defau.patch
  * d/p/0005-alsactl-use-the-right-priority-for-syslog-messages.patch
  * d/p/0006-alsactl-allow-to-compile-alsactl-without-UCM-support.patch
  * d/p/0007-alsactl-ucm-rename-_once-command-to-_boot-command.patch
  * d/p/0008-alsaucm-remove-custom-rules-alsactl-is-UCM-aware-now.patch
    Make alsactl support _boot section defined in the ucm, then the
    mixer values defined in the _boot section for Dell soundwire audio
    machines could be executed at the first booting. (LP: #1899745)

 -- Hui Wang <email address hidden> Fri, 16 Oct 2020 17:50:30 +0200