** Description changed:

  [SRU Justifications]
  
  ========== alsa-ucm-conf ==========
  [Impact]
  
  Audio output doesn't work on Dell Tarako platforms with Cirrus CS42L43
  codec
  
  [Fix]
  This requires following conf file in alsa-ucm-conf package:
    - /usr/share/alsa/ucm2/sof-soundwire/cs42l43-spk.conf
  
  [Test Case]
- 1. Boot up the machine of Dell Bolan platform with CS42L43 codec
+ 1. Boot up the machine of Dell Tarako platform with CS42L43 codec
  2. Verify the existence of /usr/share/alsa/ucm2/sof-soundwire/cs42l43-spk.conf
  3. Make sure the sof driver are loaded correctly. (tplg and Intel DSP FW are 
ready)
  4. Verify with checking the output of `amixer -c 0` command with valid 
Digital Speaker `Simple mixer control 'cs42l43 Speaker Digital',0`.
  
  [Where problems could occur]
  It only affects the Dell Tarako platforms with the new CS42L43 codec w/o 
other soundwire devices. Should be low low risk of regression
  
  ========== firmware-sof ==========
  
  [Fix]
  This requires following tplg file in firmware-sof
  - sof-lnl-cs42l43-l0.tplg and sof-arl.ri with sof-arl-cs42l43-l0.tplg
  upstream firmware-sof 2.11.x will have these tplg file included.
  
  [Test Case]
  1. Boot up the machine of Dell Tarako LunarLake and ArrowLake platform with 
cs42l43 internal speakers
  2. Verify with checking the output of `aplay -l` command with valid sof 
output device. Should never be dummy output.
  
  [Other Info]
  The name of sof-lnl-cs42l43-l0.tplg includes useful information which 
indicates that the topology is for for the cs42l43 codec connected to soundwire 
bus 0 w/o other soundwire devices connected on 1/2/3. It only affects the 
machines which has exactly the same soundwire configuration. The upstream 
commit of a newer version usually include the topology files for the new 
platforms or missing configuration on old platforms. It would be better to 
catch up with upstream to have these configuration which can support more 
configurations we could be missing in the future. The the addtional 
0002-Add-SOF-v2.11.1-signed-Intel-binaries-for-MTL-LNL-AR.patch, it's required 
for each new Intel Platform and signed by Intel. In the case, the tplg file 
specify the `lnl`, a signed LunarLake DSP FW will be necessary. It would be 
better to have the Intel signed DSP FW up-to-date.
  
  [Where problems could occur]
  Although there're lots of new tplg files added, but they are mostly for 
missing configuration on old platforms or newly added for next-gen Intel 
platform. And they are specified for particular soundwire configurations which 
can hardly affect the existing machines. The risk for regression may come from 
sof-hda-generic-xxx.tplg which is for generic HDA. I'll consider it as low risk.

-- 
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/2088403

Title:
  Missing CS42L43 sof firmware and alsa-ucm-conf for Dell Tarako
  platform

Status in HWE Next:
  New
Status in alsa-ucm-conf package in Ubuntu:
  New
Status in firmware-sof package in Ubuntu:
  New
Status in alsa-ucm-conf source package in Noble:
  In Progress
Status in firmware-sof source package in Noble:
  New
Status in alsa-ucm-conf source package in Oracular:
  In Progress
Status in firmware-sof source package in Oracular:
  New
Status in alsa-ucm-conf source package in Plucky:
  Fix Released
Status in firmware-sof source package in Plucky:
  New

Bug description:
  [SRU Justifications]

  ========== alsa-ucm-conf ==========
  [Impact]

  Audio output doesn't work on Dell Tarako platforms with Cirrus CS42L43
  codec

  [Fix]
  This requires following conf file in alsa-ucm-conf package:
    - /usr/share/alsa/ucm2/sof-soundwire/cs42l43-spk.conf

  [Test Case]
  1. Boot up the machine of Dell Tarako platform with CS42L43 codec
  2. Verify the existence of /usr/share/alsa/ucm2/sof-soundwire/cs42l43-spk.conf
  3. Make sure the sof driver are loaded correctly. (tplg and Intel DSP FW are 
ready)
  4. Verify with checking the output of `amixer -c 0` command with valid 
Digital Speaker `Simple mixer control 'cs42l43 Speaker Digital',0`.

  [Where problems could occur]
  It only affects the Dell Tarako platforms with the new CS42L43 codec w/o 
other soundwire devices. Should be low low risk of regression

  ========== firmware-sof ==========

  [Fix]
  This requires following tplg file in firmware-sof
  - sof-lnl-cs42l43-l0.tplg and sof-arl.ri with sof-arl-cs42l43-l0.tplg
  upstream firmware-sof 2.11.x will have these tplg file included.

  [Test Case]
  1. Boot up the machine of Dell Tarako LunarLake and ArrowLake platform with 
cs42l43 internal speakers
  2. Verify with checking the output of `aplay -l` command with valid sof 
output device. Should never be dummy output.

  [Other Info]
  The name of sof-lnl-cs42l43-l0.tplg includes useful information which 
indicates that the topology is for for the cs42l43 codec connected to soundwire 
bus 0 w/o other soundwire devices connected on 1/2/3. It only affects the 
machines which has exactly the same soundwire configuration. The upstream 
commit of a newer version usually include the topology files for the new 
platforms or missing configuration on old platforms. It would be better to 
catch up with upstream to have these configuration which can support more 
configurations we could be missing in the future. The the addtional 
0002-Add-SOF-v2.11.1-signed-Intel-binaries-for-MTL-LNL-AR.patch, it's required 
for each new Intel Platform and signed by Intel. In the case, the tplg file 
specify the `lnl`, a signed LunarLake DSP FW will be necessary. It would be 
better to have the Intel signed DSP FW up-to-date.

  [Where problems could occur]
  Although there're lots of new tplg files added, but they are mostly for 
missing configuration on old platforms or newly added for next-gen Intel 
platform. And they are specified for particular soundwire configurations which 
can hardly affect the existing machines. The risk for regression may come from 
sof-hda-generic-xxx.tplg which is for generic HDA. I'll consider it as low risk.

To manage notifications about this bug go to:
https://bugs.launchpad.net/hwe-next/+bug/2088403/+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

Reply via email to