~ztahenakos/ubuntu/+source/linux/+git/jammy:master-next

Last commit made on 2022-08-02
Get this branch:
git clone -b master-next https://git.launchpad.net/~ztahenakos/ubuntu/+source/linux/+git/jammy
Only Zachary Tahenakos can upload to this branch. If you are Zachary Tahenakos please log in for upload directions.

Branch merges

Branch information

Name:
master-next
Repository:
lp:~ztahenakos/ubuntu/+source/linux/+git/jammy

Recent commits

45b35e1... by nikhil kshirsagar

bcache: memset on stack variables in bch_btree_check() and bch_sectors_dirty_init()

BugLink: https://bugs.launchpad.net/bugs/1980925

From: Coly Li <email address hidden>

The local variables check_state (in bch_btree_check()) and state (in
bch_sectors_dirty_init()) should be fully filled by 0, because before
allocating them on stack, they were dynamically allocated by kzalloc().

Signed-off-by: Coly Li <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Jens Axboe <email address hidden>

(cherry picked from commit 7d6b902ea0e02b2a25c480edf471cbaa4ebe6b3c)
Signed-off-by: Nikhil Kshirsagar <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

e141bb1... by jeremyszu

ALSA: hda/realtek: fix mute/micmute LEDs for HP machines

BugLink: https://bugs.launchpad.net/bugs/1982716

The HP ProBook 440/450 G9 and EliteBook 640/650 G9 have multiple
motherboard design and they are using different subsystem ID of audio
codec. Add the same quirk for other MBs.

Signed-off-by: Jeremy Szu <email address hidden>
Cc: <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Takashi Iwai <email address hidden>

(backported from commit 61d307855eb1a2ae849da445edd5389db8a58a5c)
Signed-off-by: Jeremy Szu <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

d868316... by Deren Wu

mt76: mt7921: fix command timeout in AP stop period

BugLink: https://bugs.launchpad.net/bugs/1979173

Due to AP stop improperly, mt7921 driver would face random command timeout
by chip fw problem. Migrate AP start/stop process to .start_ap/.stop_ap and
congiure BSS network settings in both hooks.

The new flow is shown below.
* AP start
    .start_ap()
      configure BSS network resource
      set BSS to connected state
    .bss_info_changed()
      enable fw beacon offload

* AP stop
    .bss_info_changed()
      disable fw beacon offload (skip this command)
    .stop_ap()
      set BSS to disconnected state (beacon offload disabled automatically)
      destroy BSS network resource

Fixes: 116c69603b01 ("mt76: mt7921: Add AP mode support")
Signed-off-by: Sean Wang <email address hidden>
Signed-off-by: Deren Wu <email address hidden>

(backported from 9d958b60ebc2434f2b7eae83d77849e22d1059eb linux-next)
[Chris: revise the MCU_UNI_CMD(SET_BSS_ABORT) to fix the compatibility issues on 5.15]
Signed-off-by: Chris Chiu <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Acked-by: Luke Nowakowski-Krijger <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

6495049... by Deren Wu

mt76: mt7921: not support beacon offload disable command

BugLink: https://bugs.launchpad.net/bugs/1979173

Beacon disable flow would be handled in bss stop handler automatically.
Force return -EOPNOTSUPP in disable case.

Fixes: 116c69603b01 ("mt76: mt7921: Add AP mode support")
Reviewed-by: Sean Wang <email address hidden>
Signed-off-by: Deren Wu <email address hidden>

(backported from c149d3a9058616ff942a6e44b6e968e18a84dd5a linux-next)
[Chris: revise the MCU_UNI_CMD(BSS_INFO_UPDATE) to fix the compatibility issues on 5.15]
Signed-off-by: Chris Chiu <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Acked-by: Luke Nowakowski-Krijger <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

572bcfb... by mtkapsoc

mt76: mt7921: Add AP mode support

BugLink: https://bugs.launchpad.net/bugs/1979173

add AP mode support to mt7921 that can work for mt7921[e,s,u]
with the common code.

Tested-by: Deren Wu <email address hidden>
Tested-by: Lorenzo Bianconi <email address hidden>
Signed-off-by: Sean Wang <email address hidden>
Signed-off-by: Felix Fietkau <email address hidden>

(backported from commit 116c69603b01f2d6e4499ca5d535f5b71c52052c)
[Chris: revise the mt7921_mac_write_txwi() and
MCU_UNI_CMD(BSS_INFO_UPDATE) to fix the compatibility issues on 5.15]
Signed-off-by: Chris Chiu <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Acked-by: Luke Nowakowski-Krijger <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

dec849b... by Richard Gong

drm/amdgpu: vi: disable ASPM on Intel Alder Lake based systems

BugLink: https://bugs.launchpad.net/bugs/1966680

Active State Power Management (ASPM) feature is enabled since kernel 5.14.
There are some AMD Volcanic Islands (VI) GFX cards, such as the WX3200 and
RX640, that do not work with ASPM-enabled Intel Alder Lake based systems.
Using these GFX cards as video/display output, Intel Alder Lake based
systems will freeze after suspend/resume.

The issue was originally reported on one system (Dell Precision 3660 with
BIOS version 0.14.81), but was later confirmed to affect at least 4
pre-production Alder Lake based systems.

Add an extra check to disable ASPM on Intel Alder Lake based systems with
the problematic AMD Volcanic Islands GFX cards.

Fixes: 0064b0ce85bb ("drm/amd/pm: enable ASPM by default")
Link: https://gitlab.freedesktop.org/drm/amd/-/issues/1885
Signed-off-by: Richard Gong <email address hidden>
Signed-off-by: Alex Deucher <email address hidden>

(cherry picked from commit e02fe3bc7aba2f7b292c6005b8334fffd4ac5e5f)
Signed-off-by: Koba Ko <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

5ecd5e5... by Mario Limonciello <email address hidden>

drm/amd: Use amdgpu_device_should_use_aspm on navi umd pstate switching

BugLink: https://bugs.launchpad.net/bugs/1966680

The `program_aspm` callback is already guarded for aspm, but the
`enable_aspm` callback doesn't follow the module parameter.

Update it to use the helper `amdgpu_device_should_use_aspm`.

Reviewed-by: Lijo Lazar <email address hidden>
Signed-off-by: Mario Limonciello <email address hidden>
Reviewed-by: Alex Deucher <email address hidden>
Signed-off-by: Alex Deucher <email address hidden>

(cherry picked from commit d01899d3db2a553268dd4bc03641d9e80e41d67a)
Signed-off-by: Koba Ko <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

83fd39d... by Mario Limonciello <email address hidden>

drm/amd: Refactor `amdgpu_aspm` to be evaluated per device

BugLink: https://bugs.launchpad.net/bugs/1966680

Evaluating `pcie_aspm_enabled` as part of driver probe has the implication
that if one PCIe bridge with an AMD GPU connected doesn't support ASPM
then none of them do. This is an invalid assumption as the PCIe core will
configure ASPM for individual PCIe bridges.

Create a new helper function that can be called by individual dGPUs to
react to the `amdgpu_aspm` module parameter without having negative results
for other dGPUs on the PCIe bus.

Suggested-by: Lijo Lazar <email address hidden>
Reviewed-by: Lijo Lazar <email address hidden>
Signed-off-by: Mario Limonciello <email address hidden>
Reviewed-by: Alex Deucher <email address hidden>
Signed-off-by: Alex Deucher <email address hidden>

(backported from commit 0ab5d711ec74d9e60673900974806b7688857947)
[smb: context adjustment in amdgpu_drv.c for now backported bdbeb0dde425
      "drm/amdgpu: filter out radeon PCI device IDs"]
Signed-off-by: Koba Ko <email address hidden>
Acked-by: Stefan Bader <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

84f55f5... by Mathias Nyman

xhci: turn off port power in shutdown

BugLink: https://bugs.launchpad.net/bugs/1976503

If ports are not turned off in shutdown then runtime suspended
self-powered USB devices may survive in U3 link state over S5.

During subsequent boot, if firmware sends an IPC command to program
the port in DISCONNECT state, it will time out, causing significant
delay in the boot time.

Turning off roothub port power is also recommended in xhci
specification 4.19.4 "Port Power" in the additional note.

Cc: <email address hidden>
Signed-off-by: Mathias Nyman <email address hidden>
Link: https://<email address hidden>
Signed-off-by: Greg Kroah-Hartman <email address hidden>

(cherry picked from commit 83810f84ecf11dfc5a9414a8b762c3501b328185)
Signed-off-by: Kai-Heng Feng <email address hidden>
Acked-by: Tim Gardner <email address hidden>
Acked-by: Luke Nowakowski-Krijger <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>

c51afc2... by Kamal Mostafa

UBUNTU: Upstream stable to v5.15.46

BugLink: https://bugs.launchpad.net/bugs/1981864

Ignore: yes
Signed-off-by: Kamal Mostafa <email address hidden>
Signed-off-by: Stefan Bader <email address hidden>