Support different Cirrus audio codec configurations on Dell laptops
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
In Progress
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Medium
|
Unassigned | ||
Kinetic |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem-5.14 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
Jammy |
Invalid
|
Undecided
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned | ||
linux-oem-5.17 (Ubuntu) |
Invalid
|
Undecided
|
Unassigned | ||
Focal |
Invalid
|
Undecided
|
Unassigned | ||
Jammy |
Fix Released
|
Undecided
|
Unassigned | ||
Kinetic |
Invalid
|
Undecided
|
Unassigned |
Bug Description
[SRU Justification]
[Impact]
On Dell's platform, Warlock/Bullseye Laptops have a mono DMIC, Cyborg and some Warlock variants uses a stereo DMIC. They are not correctly mapped to the corresponding configurations so the microphone function are not working as expected.
[Fix]
Cirrus upstream new FIXUPs to support different microphone configurations on different Dell laptop variants.
[Test Case]
1. Go to Audio Settings
2. Make sure the microphone is correctly detected and responds to audio input.
3. Issue command "arecord record_file" and check the record_file is consistent with audio input.
[Where problems could occur]
Risk should be Low. The patches come from Cirrus and the configurations are mapped based on the audio codec's SSIDs for different Dell variants.
CVE References
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | New → In Progress |
Changed in linux (Ubuntu Jammy): | |
status: | New → In Progress |
tags: | added: oem-priority originate-from-1964057 somerville |
Changed in linux (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux-oem-5.14 (Ubuntu Focal): | |
status: | In Progress → Fix Committed |
Changed in linux-oem-5.14 (Ubuntu Jammy): | |
status: | New → Invalid |
tags: |
added: verification-done-focal removed: verification-needed-focal |
Changed in linux (Ubuntu Jammy): | |
importance: | Undecided → Medium |
status: | In Progress → Fix Committed |
tags: |
added: verification-done-jammy removed: verification-needed-jammy |
Changed in linux-oem-5.17 (Ubuntu): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Focal): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Jammy): | |
status: | New → Fix Committed |
Changed in hwe-next: | |
status: | New → Fix Released |
Changed in linux (Ubuntu Kinetic): | |
status: | New → Fix Released |
Changed in linux-oem-5.14 (Ubuntu Kinetic): | |
status: | New → Invalid |
Changed in linux-oem-5.17 (Ubuntu Kinetic): | |
status: | New → Invalid |
This bug is awaiting verification that the linux-oem- 5.14/5. 14.0-1034. 37 kernel in -proposed solves the problem. Please test the kernel and update this bug with the results. If the problem is solved, change the tag 'verification- needed- focal' to 'verification- done-focal' . If the problem still exists, change the tag 'verification- needed- focal' to 'verification- failed- focal'.
If verification is not done by 5 working days from today, this fix will be dropped from the source code, and this bug will be closed.
See https:/ /wiki.ubuntu. com/Testing/ EnableProposed for documentation how to enable and use -proposed. Thank you!