Add SoundWire devices to alsa-info reported in ACPI

[Chris Chiu]

[SRU Justifications]

[Impact]
Modern Intel platforms (RPL, MTL, LNL...etc) connect audio codecs on Soundwire instead of HDA, but the soundwire devices are not well reflected on the alsa-info report. In order to meet the increasing demands for SoundWire debugging, we must enable alsa-info to provide more information about SoundWire.

[Fix]
Backport the upstream commit cc0bcef81389 ("alsa-info.sh: log SoundWire devices reported in ACPI") of v1.2.12. The Oracular is expected to sync with v1.2.12 and we may not have to backport to Oracular. The reported information can reflect which soundwire devices are connected and which soundware link the device connects to. It's quite sufficient for what driver should be ready and what tplg/firmware file should be loaded.

[Test Case]
1. Find a machine with (RTK/Cirrus/TI) Soundwire audio device.
2. Install the new alsa-utils debian package
3. Execute `alsa-info` to generate the report
4. Check if the section "ACPI SoundWire Device Status Information" exists in the output report.

[Where problems could occur]
It's simply an additional soundwire information when ACPI exposed the soundwire device. The risk for regression is low.

[Other Info]
Verify if the official Oracular starts from version v1.2.12 to determine if we have to land it on Oracular.

[Chris Chiu (mschiu77)]

MR proposed for review on Noble
https://code.launchpad.net/~mschiu77/ubuntu/+source/alsa-utils/+git/alsa-utils/+merge/469920

MR proposed for review on Jammy
https://code.launchpad.net/~mschiu77/ubuntu/+source/alsa-utils/+git/alsa-utils/+merge/469921

[Dan Bungert (dbungert)]

> The Oracular is expected to sync with v1.2.12 and we may not have to backport to Oracular.

What happens if the merge of alsa-utils doesn't occur? Right now we are in a state where a merge is required, so this isn't going to autosync, and if the merge doesn't happen in Oracular then users will see regressions in this behavior.

To satisfy SRU requirements (https://wiki.ubuntu.com/StableReleaseUpdates#Development_Release_Fixed_First) I request that this merge be completed first, or at least a backport of the relevant fix if a merge is unrealistic.

Unsubscribing sponsors for the moment, please resubscribe when ready.

The patches themselves look fine but I'll request dep3 consideration.

[Chris Chiu (mschiu77)]

@Dan, I though the alsa-utils of Oracular should be rebased on v1.2.12 and I don't know how it will happen.

Can you suggest what I should do? I think the correct way is to trigger the sync? Or I should do it manually?