AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes

[You-Sheng Yang]

[SRU Justification]

[Impact]

On AMD Yellow Carp B0 platforms, S0i3 is still not working.

[Fix]

This denpends on a few fixes for kernel driver that are all either in
v5.17-rc1 or in stable linux-5.1x.y, along with an already upstreamed
dmcub firmware.

[Test Case]

On AMD RMT CRB board,
1. apply both kernel and firmware fixes
2. module blacklist amd_sfh as it's still under development,
3. trigger system suspend. Use power button to wake up the device.
4. check /sys/kernel/debug/amd_pmc/s0ix_stats, the values shall be non-zero

On without any of above, the board may not cut device power during suspend, and/or fail to resume and leaving a blank screen, and/or s0ix stats remain all zeros.

[Where problems could occur]

On AMD RMT CRB board, Sensor Fusion Hub (amd_sfh) still doesn't support S0ix and has to be disabled. For the kernel side, the driver fixes addressed a few procedure errors that should be unlikely to introduce regressions; for the firmware side, also tested loading new firmware on unpatched kernels and there is no difference found yet.

[Other Info]

For kernel driver fixes, patches for both oem-5.14 and jammy are necessary; for firmware, that has been available in jammy branch but not yet released, so only Focal will be nominated.

[You-Sheng Yang (vicamo)]

PPA: https://launchpad.net/~vicamo/+archive/ubuntu/ppa-1957026

[You-Sheng Yang (vicamo)]

Already in jammy branch but not yet released.

[You-Sheng Yang (vicamo)]

SRU:
* https://lists.ubuntu.com/archives/kernel-team/2022-January/127429.html (linux-firmware/focal)
* https://lists.ubuntu.com/archives/kernel-team/2022-January/127434.html (oem-5.14, jammy)

[Timo Aaltonen (tjaalton)]

could you update the "where problems.." part, it doesn't make sense for the firmware

[Timo Aaltonen (tjaalton)]

Hello You-Sheng, or anyone else affected,

Accepted linux-firmware into focal-proposed. The package will build now and be available at https://launchpad.net/ubuntu/+source/linux-firmware/1.187.26 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-focal to verification-done-focal. If it does not fix the bug for you, please add a comment stating that, and change the tag to verification-failed-focal. 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.

[You-Sheng Yang (vicamo)]

verified linux-firmware/focal-proposed version 1.187.26.

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-firmware - 1.187.26

---------------
linux-firmware (1.187.26) focal; urgency=medium

  * [SRU][F] Add firmware of MT7922 (LP: #1958153)
    - linux-firmware: add firmware for MT7922
    - linux-firmware: add frimware for mediatek bluetooth chip (MT7922)
  * linux-firmware missing renoir_ta (LP: #1958283)
    - amdgpu: update renoir firmware for 20.10
    - amdgpu: update renoir firmware from 20.20 release
    - amdgpu: update renoir firmware for 20.30
    - amdgpu: update renoir firmware for 20.40
    - amdgpu: update renoir firmware for 20.45
    - amdgpu: update renoir firmware for 20.50
    - amdgpu: update renoir firmware from 21.10
    - amdgpu: update renoir firmware from 21.20
    - amdgpu: update vcn firmware for renoir for 21.20
    - amdgpu: update renoir firmware from 21.30
    - amdgpu: update VCN firmware for renoir
  * mt7921e 0000:02:00.0: PM: failed to resume async: error -110 (LP: #1958286)
    - linux-firmware: update frimware for mediatek bluetooth chip (MT7921)
    - linux-firmware: update firmware for mediatek bluetooth chip (MT7921)
    - linux-firmware: update firmware for MT7921 WiFi device
    - linux-firmware: update firmware for MT7921 WiFi device
    - linux-firmware: update firmware for mediatek bluetooth chip(MT7921)
  * [SRU][F] Add mt8183 SCP firmware (LP: #1959064)
    - mediatek: Add mt8183 SCP firmware
  * AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes (LP: #1957026)
    - amdgpu: update yellow carp dmcub firmware

 -- Juerg Haefliger <email address hidden> Fri, 28 Jan 2022 10:54:30 +0100

[Timo Aaltonen (tjaalton)]

The verification of the Stable Release Update for linux-firmware 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.

[Juerg Haefliger (juergh)]

Released with linux-firmware 20220124.git0c6a7b3b-0ubuntu1 in Jammy.

[You-Sheng Yang (vicamo)]

Verified linux-oem-5.14/focal-proposed version 5.14.0-1023

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux-oem-5.14 - 5.14.0-1024.26

---------------
linux-oem-5.14 (5.14.0-1024.26) focal; urgency=medium

  * focal/linux-oem-5.14: 5.14.0-1024.26 -proposed tracker (LP: #1961191)

  * Packaging resync (LP: #1786013)
    - [Config] Update config to match upstream stable release
    - [Packaging] update variants

  * CVE-2022-0435
    - tipc: improve size validations for received domain records

  * CVE-2022-0492
    - cgroup-v1: Require capabilities to set release_agent

  * Use EC GPE for s2idle wakeup on AMD platforms (LP: #1960771)
    - ACPI: PM: Revert "Only mark EC GPE for wakeup on Intel systems"

  * USB port lost function after unplugging usb drive (LP: #1958850)
    - block: add disk sequence number
    - mm: hide laptop_mode_wb_timer entirely behind the BDI API
    - block: pass a gendisk to blk_queue_update_readahead
    - block: add a queue_has_disk helper
    - block: move the bdi from the request_queue to the gendisk
    - block: remove the bd_bdi in struct block_device
    - nvme: use blk_mq_alloc_disk
    - st: do not allocate a gendisk
    - sg: do not allocate a gendisk
    - block: cleanup the lockdep handling in *alloc_disk
    - block: remove alloc_disk and alloc_disk_node
    - block: remove the minors argument to __alloc_disk_node
    - block: pass a request_queue to __blk_alloc_disk
    - block: hold a request_queue reference for the lifetime of struct gendisk
    - block: add an explicit ->disk backpointer to the request_queue
    - writeback: make the laptop_mode prototypes available unconditionally
    - sg: pass the device name to blk_trace_setup
    - block: factor out a blk_try_enter_queue helper
    - block: drain file system I/O on del_gendisk
    - block: keep q_usage_counter in atomic mode after del_gendisk
    - block: drain queue after disk is removed from sysfs
    - nvdimm/pmem: stop using q_usage_count as external pgmap refcount
    - nvdimm/pmem: cleanup the disk if pmem_release_disk() is yet assigned

  * Focal update: upstream stable patchset 2022-01-31 (LP: #1959569)
    - iommu/amd: Restore GA log/tail pointer on host resume

 -- Timo Aaltonen <email address hidden> Thu, 17 Feb 2022 13:23:43 +0200

[You-Sheng Yang (vicamo)]

All proposed patches have been in 5.17 or above.

[You-Sheng Yang (vicamo)]

SRU: https://lists.ubuntu.com/archives/kernel-team/2022-July/132126.html (jammy, V2)

[Launchpad Janitor (janitor)]

This bug was fixed in the package linux - 5.15.0-47.51

---------------
linux (5.15.0-47.51) jammy; urgency=medium

  * jammy/linux: 5.15.0-47.51 -proposed tracker (LP: #1983903)

  * Jammy update: v5.15.46 upstream stable release (LP: #1981864)
    - UBUNTU: [Packaging] Move python3-dev to build-depends

  * touchpad and touchscreen doesn't work at all on ACER Spin 5 (SP513-54N)
    (LP: #1884232)
    - x86/PCI: Eliminate remove_e820_regions() common subexpressions
    - x86: Log resource clipping for E820 regions
    - x86/PCI: Clip only host bridge windows for E820 regions
    - x86/PCI: Add kernel cmdline options to use/ignore E820 reserved regions
    - x86/PCI: Disable E820 reserved region clipping via quirks
    - x86/PCI: Revert "x86/PCI: Clip only host bridge windows for E820 regions"

  * [SRU][H/OEM-5.13/OEM-5.14/U][J/OEM-5.17/U] Fix invalid MAC address after
    hotplug tbt dock (LP: #1942999)
    - SAUCE: igc: wait for the MAC copy when enabled MAC passthrough

  * Mass Storage Gadget driver truncates device >2TB (LP: #1981390)
    - usb: gadget: storage: add support for media larger than 2T

  * AMD Rembrandt: DP tunneling fails with Thunderbolt monitors (LP: #1983143)
    - SAUCE: drm/amd: Fix DP Tunneling with Thunderbolt monitors
    - drm/amd/display: Fix for dmub outbox notification enable
    - Revert "drm/amd/display: Fix DPIA outbox timeout after S3/S4/reset"
    - drm/amd/display: Reset link encoder assignments for GPU reset
    - drm/amd/display: Fix DPIA outbox timeout after S3/S4/reset
    - drm/amd/display: Fix new dmub notification enabling in DM
    - SAUCE: thunderbolt: Add DP out resource when DP tunnel is discovered.

  * Fix sub-optimal I210 network speed (LP: #1976438)
    - igb: Make DMA faster when CPU is active on the PCIe link

  * e1000e report hardware hang (LP: #1973104)
    - e1000e: Enable GPT clock before sending message to CSME
    - Revert "e1000e: Fix possible HW unit hang after an s0ix exit"

  * ioam6.sh in net from ubuntu_kernel_selftests fails with 5.15 kernels in
    Focal (LP: #1982930)
    - selftests: net: fix IOAM test skip return code

  * Additional fix for TGL + AUO panel flickering (LP: #1983297)
    - Revert "UBUNTU: SAUCE: drm/i915/display/psr: Fix flicker on TGL + AUO panel"
    - drm/i915/display: Fix sel fetch plane offset calculation
    - drm/i915: Nuke ORIGIN_GTT
    - drm/i915/display: Drop PSR support from HSW and BDW
    - drm/i915/display/psr: Handle plane and pipe restrictions at every page flip
    - drm/i915/display/psr: Do full fetch when handling multi-planar formats
    - drm/i915/display: Drop unnecessary frontbuffer flushes
    - drm/i915/display: Handle frontbuffer rendering when PSR2 selective fetch is
      enabled
    - drm/i915/display: Fix glitches when moving cursor with PSR2 selective fetch
      enabled
    - SAUCE: drm/i915/display/psr: Reinstate fix for TGL + AUO panel flicker

  * AMD Yellow Carp DMCUB fw update for s0i3 B0 fixes (LP: #1957026)
    - drm/amd/display: Optimize bandwidth on following fast update
    - drm/amd/display: Fix surface optimization regression on Carrizo
    - drm/amd/display: Reset DMCUB before HW init

  * GPIO character devi...

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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

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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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

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!

[Ubuntu Kernel Bot (ubuntu-kernel-bot)]

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

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!