soc/amd/renoir: change the module name to make it work with ucm3
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
HWE Next |
Fix Released
|
Undecided
|
Unassigned | ||
linux (Ubuntu) |
Fix Released
|
Undecided
|
Hui Wang | ||
Focal |
Fix Released
|
Undecided
|
Unassigned | ||
linux-oem-5.6 (Ubuntu) |
Fix Released
|
Undecided
|
Unassigned | ||
Focal |
Fix Released
|
Undecided
|
Unassigned |
Bug Description
[Impact]
the alsa upstream worte the ucm3 files for amd renoir audio, but to
load the ucm3, it depends on the kernel module name, and the upstream
ucm3 needs the name snd-xxx, so we need to backport the patch
from mainline kernel to change the kernel module name to meet ucm3
requirement.
[Fix]
Backport 1 patch from upstream.
[Test Case]
boot the kernel with the patch on amd renoir machines (lenovo
machines), the audio driver works well (via command line like
aplay or areord), then upgrade the alsa-lib and alsa-ucm-conf to
1.2.3.2, now we could see the audio devices from gnome, and they work
well.
[Regression Risk]
Low, this SRU are only specific to soc/amd/renoir, and we already
tested on 2 lenovo machines, their audio worked as before.
summary: |
- soc/amd/renoir: change the module name to mke it work with ucm3 + soc/amd/renoir: change the module name to make it work with ucm3 |
tags: | added: oem-priority originate-from-1867844 sutton |
description: | updated |
description: | updated |
description: | updated |
Changed in linux-oem-5.6 (Ubuntu Focal): | |
status: | New → Fix Committed |
Changed in linux (Ubuntu Focal): | |
status: | Incomplete → Fix Committed |
Changed in linux (Ubuntu): | |
status: | Incomplete → Fix Released |
Changed in hwe-next: | |
status: | New → Fix Released |
This bug is missing log files that will aid in diagnosing the problem. While running an Ubuntu kernel (not a mainline or third-party kernel) please enter the following command in a terminal window:
apport-collect 1888166
and then change the status of the bug to 'Confirmed'.
If, due to the nature of the issue you have encountered, you are unable to run this command, please add a comment stating that fact and change the bug status to 'Confirmed'.
This change has been made by an automated script, maintained by the Ubuntu Kernel Team.