** Also affects: linux (Ubuntu)
Importance: Undecided
Status: New
** Also affects: linux (Ubuntu Plucky)
Importance: Undecided
Status: New
** Also affects: linux-oem-6.11 (Ubuntu Plucky)
Importance: Undecided
Status: New
** Changed in: linux-oem-6.11 (Ubuntu Plucky)
Status: New => Invalid
** Changed in: linux (Ubuntu Noble)
Status: New => Won't Fix
--
You received this bug notification because you are subscribed to linux
in Ubuntu.
Matching subscriptions: Bgg, Bmail, Nb
https://bugs.launchpad.net/bugs/2089273
Title:
Add soundwire support for AMD platforms
Status in OEM Priority Project:
New
Status in linux package in Ubuntu:
New
Status in linux-oem-6.11 package in Ubuntu:
Invalid
Status in linux source package in Noble:
Won't Fix
Status in linux-oem-6.11 source package in Noble:
New
Status in linux source package in Plucky:
New
Status in linux-oem-6.11 source package in Plucky:
Invalid
Bug description:
[ Impact ]
This patch series introduce soundwire support for AMD platform, as
well as code reorganization in preparation for that.
[ Test ]
1. Install the test kernel
2. Install proper alsa-ucm-confs
3. Confirm the audio function normally on the DUT with 1) AMD soundwire and 2) existing Intel platforms using soundwire. Might include:
* Checkbox audio test plan
* Built-in speaker and built-in mic
* Audio function when headphone is connected to the DUT.
[ Where problems could occur ]
Patches needed, other than 3 SAUCE patches that planned to upstream in
6.13 cycle, are listed in [1] to [8] below.
Soundwire used to appear mostly on Intel platforms and is almost
always in combination with sof. To support AMD, it has to be
refactored into a more generic framework (or at least that's what AMD
people did). This happens in patch series [1][2] and [3], extracting
soundwire code from the sound/soc/intel directory to a more generic
location, as well as rename/refactor things to better fit the ASoC
context. This will impact all other soundwire platforms and if not
done correctly, regression risk may be high.
The all other patch sets other than [5] are AMD specific, so
theoretically the impact is limited to AMD platforms with soundwire,
which are rather uncommon.
[1] https://lore.kernel.org/all/20240801091446.10457-1-Vijendar.Mukunda@amd.com/
[2] https://lore.kernel.org/lkml/20240913090631.1834543-1-Vijendar.Mukunda@amd.com/
[3] https://lore.kernel.org/all/20241101020802.1103181-1-Vijendar.Mukunda@amd.com/
[4] https://lore.kernel.org/all/20240924081846.1834612-1-Vijendar.Mukunda@amd.com/
[5] https://lore.kernel.org/all/20241105100557.1987917-1-shumingf@realtek.com/
[6] https://lore.kernel.org/all/20241113115223.3274868-1-Vijendar.Mukunda@amd.com/
[7] https://lore.kernel.org/all/20241112185138.3235375-1-Vijendar.Mukunda@amd.com/
[8] https://lore.kernel.org/all/20241112161142.28974-1-mario.limonciello@amd.com/
To manage notifications about this bug go to:
https://bugs.launchpad.net/oem-priority/+bug/2089273/+subscriptions
Комментариев нет:
Отправить комментарий