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

[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.


** Description changed:

- This bug is for tracking purpose.
+ 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.

** Description changed:

  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.
+ tested it both on soundwire machines and non-soundwire machines, all worked well.

** Patch added: "alsa-utils_1.2.2-1ubuntu2.debdiff"
   https://bugs.launchpad.net/ubuntu/+source/alsa-utils/+bug/1899745/+attachment/5422066/+files/alsa-utils_1.2.2-1ubuntu2.debdiff

-- 
You received this bug notification because you are a member of Ubuntu
Sponsors Team, which is subscribed to the bug report.
https://bugs.launchpad.net/bugs/1899745

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

Status in HWE Next:
  New
Status in alsa-utils package in Ubuntu:
  In Progress
Status in alsa-utils source package in Focal:
  In Progress

Bug description:
  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.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/1899745/+subscriptions