Orchid Bay MLK2/Maya Bay MLK soundwire support

WIP: https://kernel.ubuntu.com/gitea/kernel/jammy-linux-oem/pulls/104

Attach proposed debdiff for firmware-sof for Jammy, Mantic and Noble.

Note that it contains binary files that cannot be correctly rendered
by debdiff and a PPA at
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2042090 is provided
at the same time.

Will proceed to SRU once verified working on actual hardware.

Attach proposed debdiff for firmware-sof for Jammy, Mantic and Noble.

V2: include changes for bug 2044330.

Note that it contains binary files that cannot be correctly rendered
by debdiff and a PPA at
https://launchpad.net/~vicamo/+archive/ubuntu/ppa-2042090 is provided
at the same time.

Need sponsor.

SRU for kernels:
* https://kernel.ubuntu.com/gitea/kernel/jammy-linux-oem/pulls/104 (oem-6.5)
* https://lists.ubuntu.com/archives/kernel-team/2023-November/147315.html (mantic)
* https://lists.ubuntu.com/archives/kernel-team/2023-November/147320.html (noble)
* https://lists.ubuntu.com/archives/kernel-team/2023-November/147325.html (unstable)

This bug was fixed in the package firmware-sof - 2.2.6-1ubuntu4

---------------
firmware-sof (2.2.6-1ubuntu4) noble; urgency=medium

  * Orchid Bay MLK2/Maya Bay MLK soundwire support. LP: #2042090
    - Add Intel SOF2.7.2 topology files.
  * Update soundwire topology files for Intel RPL platforms. LP: #2044330
    - Update v2.2.8 topology files for Intel RPL platforms

 -- You-Sheng Yang <email address hidden> Wed, 15 Nov 2023 23:32:40 +0800

Hello You-Sheng, or anyone else affected,

Accepted firmware-sof into mantic-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware-sof/2.2.6-1ubuntu1.3 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-mantic to verification-done-mantic. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-mantic. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

Hello You-Sheng, or anyone else affected,

Accepted firmware-sof into jammy-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/firmware-sof/2.0-1ubuntu4.5 in a few hours, and then in the -proposed repository.

Please help us by testing this new package. See https://wiki.ubuntu.com/Testing/EnableProposed for documentation on how to enable and use -proposed. Your feedback will aid us getting this update out to other Ubuntu users.

If this package fixes the bug for you, please add a comment to this bug, mentioning the version of the package you tested, what testing has been performed on the package and change the tag from verification-needed-jammy to verification-done-jammy. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-jammy. In either case, without details of your testing we will not be able to proceed.

Further information regarding the verification process can be found at https://wiki.ubuntu.com/QATeam/PerformingSRUVerification . Thank you in advance for helping!

N.B. The updated package will be released to -updates after the bug(s) fixed by this package have been verified and the package has been in -proposed for a minimum of 7 days.

verified firmware-sof/mantic-proposed version 2.2.6-1ubuntu1.3, firmware-sof/jammy-proposed version 2.0-1ubuntu4.5.

This bug is awaiting verification that the linux-oem-6.5/6.5.0-1010.11 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-jammy-linux-oem-6.5' to 'verification-done-jammy-linux-oem-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-oem-6.5' to 'verification-failed-jammy-linux-oem-6.5'.

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!

There doesn't seem to be anything to sponsor here, so I'm unsubscribing ubuntu-sponsors. Please make sure to keep your ubuntu-sponsors subscriptions current so we don't waste time in complex multi package bugs trying to figure out if there's anything to do for us.

verified linux-oem-6.5 version 6.5.0-1010.11

This bug is awaiting verification that the linux/6.5.0-16.16 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-mantic-linux' to 'verification-done-mantic-linux'. If the problem still exists, change the tag 'verification-needed-mantic-linux' to 'verification-failed-mantic-linux'.

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!

This bug was fixed in the package linux-oem-6.5 - 6.5.0-1011.12

---------------
linux-oem-6.5 (6.5.0-1011.12) jammy; urgency=medium

  * jammy/linux-oem-6.5: 6.5.0-1011.12 -proposed tracker (LP: #2047946)

  * [needs-packaging] usbio-drivers (LP: #2041800)
    - SAUCE: usbio-drivers: import intel-usbio-dkms source
    - debian/dkms-versions -- build usbio-drivers from the in-tree copy

  * Support standalone dkms source tree embedded in kernel source (LP: #2047909)
    - [Packaging] dkms-build -- support in-tree dkms source directory

  * jammy-oem-6.5: one more panel needs to disable psr2 (LP: #2046681)
    - SAUCE: drm/i915/display/psr: disable psr2 for panel_0x4d_0x10_0x8f_0x15

 -- Timo Aaltonen <email address hidden> Wed, 03 Jan 2024 21:03:45 +0200

verified linux/mantic-proposed version 6.5.0-17.17.

Looking at the firmware-sof SRU, it looks like both this package and the kernel need updating to complete the hardware enablement. So have these been tested from -proposed together? It looks like verification was done separately for the kernel and for the userspace package, and that makes no sense to me. What about HWE vs. non-HWE kernels?

Please confirm that you have completed SRU verification using the Test Plan and using packages only from the main archive (including packages from -proposed as appropriate) and from no other sources.

Please detail the specific combinations of kernel and firmware-sof tested.

Once done, please flip the tags back.

@Robie,

The proposed patches, binaries are first included in intermediate PPAs meant for oem integration since the day it's confirmed effective for the issue, and then SRU process proceeds to ensure these changes will be included in targeted milestones. That is, while -proposed packages for different source packages, e.g. kernel and firmware-sof here, may not arrive at the same time for testing, we're still able to verify them separately against existing intermediate PPAs. With the last jigsaw in position, people may then test all necessary components as a whole. So, yes, they were verified as an integrated set with all proposed parts installed.

HWE kernels are based on the corresponding -generic kernel. Once the kernel fixes are in -generic, HWE kernels will rebase onto them and receive the same fixes as well. OEM-6.5 is also based on generic-6.5 (linux/mantic), but usually with a tie schedule and we may like to land it on oem-6.5 first and release early. It will also rebase onto linux/mantic in the next cycle, and oem-6.5 will no longer carry the fixes itself but from linux/mantic instead.

Thanks @vicamo, but what we want to ensure is much simpler than that whole release process.

We just want to be sure that the firmware-sof from proposed, and the updated kernel from proposed (and updates, i.e., currently available outside proposed) were tested together according to the test plan.

In other words:

> Please confirm that you have completed SRU verification using the Test Plan and using packages only
> from the main archive (including packages from -proposed as appropriate) and from no other sources.
> Please detail the specific combinations of kernel and firmware-sof tested.

No PPAs must be involved at this stage, since everything is in proposed.

This bug was fixed in the package linux - 6.5.0-17.17

---------------
linux (6.5.0-17.17) mantic; urgency=medium

  * mantic/linux: 6.5.0-17.17 -proposed tracker (LP: #2049026)

  * [UBUNTU 23.04] Regression: Ubuntu 23.04/23.10 do not include uvdevice
    anymore (LP: #2048919)
    - [Config] Enable S390_UV_UAPI (built-in)

linux (6.5.0-16.16) mantic; urgency=medium

  * mantic/linux: 6.5.0-16.16 -proposed tracker (LP: #2048372)

  * Packaging resync (LP: #1786013)
    - [Packaging] resync git-ubuntu-log
    - [Packaging] resync update-dkms-versions helper
    - [Packaging] remove helper scripts
    - [Packaging] update annotations scripts
    - debian/dkms-versions -- update from kernel-versions (main/2024.01.08)

  * Add missing RPL P/U CPU IDs (LP: #2047398)
    - drm/i915/rpl: Update pci ids for RPL P/U

  * Fix BCM57416 lost after resume (LP: #2047518)
    - bnxt_en: Clear resource reservation during resume

  * Hotplugging SCSI disk in QEMU VM fails (LP: #2047382)
    - Revert "PCI: acpiphp: Reassign resources on bridge if necessary"

  * Update bnxt_en with bug fixes and support for Broadcom 5760X network
    adapters (LP: #2045796)
    - bnxt_en: use dev_consume_skb_any() in bnxt_tx_int
    - eth: bnxt: move and rename reset helpers
    - eth: bnxt: take the bit to set as argument of bnxt_queue_sp_work()
    - eth: bnxt: handle invalid Tx completions more gracefully
    - eth: bnxt: fix one of the W=1 warnings about fortified memcpy()
    - eth: bnxt: fix warning for define in struct_group
    - bnxt_en: Fix W=1 warning in bnxt_dcb.c from fortify memcpy()
    - bnxt_en: Fix W=stringop-overflow warning in bnxt_dcb.c
    - bnxt_en: Use the unified RX page pool buffers for XDP and non-XDP
    - bnxt_en: Let the page pool manage the DMA mapping
    - bnxt_en: Increment rx_resets counter in bnxt_disable_napi()
    - bnxt_en: Save ring error counters across reset
    - bnxt_en: Display the ring error counters under ethtool -S
    - bnxt_en: Add tx_resets ring counter
    - bnxt: use the NAPI skb allocation cache
    - bnxt_en: Update firmware interface to 1.10.2.171
    - bnxt_en: Enhance hwmon temperature reporting
    - bnxt_en: Move hwmon functions into a dedicated file
    - bnxt_en: Modify the driver to use hwmon_device_register_with_info
    - bnxt_en: Expose threshold temperatures through hwmon
    - bnxt_en: Use non-standard attribute to expose shutdown temperature
    - bnxt_en: Event handler for Thermal event
    - bnxt_en: Support QOS and TPID settings for the SRIOV VLAN
    - bnxt_en: Update VNIC resource calculation for VFs
    - Revert "bnxt_en: Support QOS and TPID settings for the SRIOV VLAN"
    - eth: bnxt: fix backward compatibility with older devices
    - bnxt_en: Do not call sleeping hwmon_notify_event() from NAPI
    - bnxt_en: Fix invoking hwmon_notify_event
    - bnxt_en: add infrastructure to lookup ethtool link mode
    - bnxt_en: support lane configuration via ethtool
    - bnxt_en: refactor speed independent ethtool modes
    - bnxt_en: Refactor NRZ/PAM4 link speed related logic
    - bnxt_en: convert to linkmode_set_bit() API
    - bnxt_en: extend media types to supported and autoneg modes
    - bnxt_en: Fix 2...

This bug is awaiting verification that the linux-gcp-6.5/6.5.0-1013.13~22.04.1 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-jammy-linux-gcp-6.5' to 'verification-done-jammy-linux-gcp-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-gcp-6.5' to 'verification-failed-jammy-linux-gcp-6.5'.

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!

This bug is awaiting verification that the linux-azure/6.5.0-1013.13 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-mantic-linux-azure' to 'verification-done-mantic-linux-azure'. If the problem still exists, change the tag 'verification-needed-mantic-linux-azure' to 'verification-failed-mantic-linux-azure'.

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!

This bug is awaiting verification that the linux-aws-6.5/6.5.0-1013.13~22.04.1 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-jammy-linux-aws-6.5' to 'verification-done-jammy-linux-aws-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-aws-6.5' to 'verification-failed-jammy-linux-aws-6.5'.

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!

QA has done regression test on jammy.

> With the last jigsaw in position, people may then test all necessary components as a whole. So, yes, they were verified as an integrated set with all proposed parts installed.

* linux/mantic-proposed version 6.5.0-17.17
* linux-oem-6.5 version 6.5.0-1010.11
* firmware-sof/mantic-proposed version 2.2.6-1ubuntu1.3
* firmware-sof/jammy-proposed version 2.0-1ubuntu4.5.

This bug was fixed in the package firmware-sof - 2.2.6-1ubuntu1.3

---------------
firmware-sof (2.2.6-1ubuntu1.3) mantic; urgency=medium

  * Orchid Bay MLK2/Maya Bay MLK soundwire support. LP: #2042090
    - Add Intel SOF2.7.2 topology files.
  * Update soundwire topology files for Intel RPL platforms. LP: #2044330
    - Update v2.2.8 topology files for Intel RPL platforms

 -- You-Sheng Yang <email address hidden> Wed, 15 Nov 2023 23:32:40 +0800

The verification of the Stable Release Update for firmware-sof has completed successfully and the package is now being released to -updates. Subsequently, the Ubuntu Stable Release Updates Team is being unsubscribed and will not receive messages about this bug report. In the event that you encounter a regression using the package from -updates please report a new bug using ubuntu-bug and tag the bug report regression-update so we can easily find any regressions.

This bug was fixed in the package firmware-sof - 2.0-1ubuntu4.5

---------------
firmware-sof (2.0-1ubuntu4.5) jammy; urgency=medium

  * Orchid Bay MLK2/Maya Bay MLK soundwire support. LP: #2042090
    - Add Intel SOF2.7.2 topology files.
  * Update soundwire topology files for Intel RPL platforms. LP: #2044330
    - Update v2.2.8 topology files for Intel RPL platforms

 -- You-Sheng Yang <email address hidden> Wed, 15 Nov 2023 23:32:40 +0800

This bug is awaiting verification that the linux-nvidia-6.5/6.5.0-1014.14 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-jammy-linux-nvidia-6.5' to 'verification-done-jammy-linux-nvidia-6.5'. If the problem still exists, change the tag 'verification-needed-jammy-linux-nvidia-6.5' to 'verification-failed-jammy-linux-nvidia-6.5'.

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!