lp:~vicamo/hwe-next/+git/intermediate-kernel

Author: Imre Deak
Author Date: 2022-06-21 05:34:00 UTC

drm/dp/mst: Read the extended DPCD capabilities during system resume

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

The WD22TB4 Thunderbolt dock at least will revert its DP_MAX_LINK_RATE
from HBR3 to HBR2 after system suspend/resume if the DP_DP13_DPCD_REV
registers are not read subsequently also as required.

Fix this by reading DP_DP13_DPCD_REV registers as well, matching what is
done during connector detection. While at it also fix up the same call
in drm_dp_mst_dump_topology().

Cc: Lyude Paul <lyude@redhat.com>
Closes: https://gitlab.freedesktop.org/drm/intel/-/issues/5292
Signed-off-by: Imre Deak <imre.deak@intel.com>
Reviewed-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Lyude Paul <lyude@redhat.com>
Ref: https://patchwork.freedesktop.org/patch/489424/?series=105101&rev=1
Signed-off-by: Koba Ko <koba.ko@canonical.com>

Author: Pavel Skripkin
Author Date: 2022-06-13 18:43:59 UTC

ath9k: fix use-after-free in ath9k_hif_usb_rx_cb

Syzbot reported use-after-free Read in ath9k_hif_usb_rx_cb() [0]. The
problem was in incorrect htc_handle->drv_priv initialization.

Probable call trace which can trigger use-after-free:

ath9k_htc_probe_device()
  /* htc_handle->drv_priv = priv; */
  ath9k_htc_wait_for_target() <--- Failed
  ieee80211_free_hw() <--- priv pointer is freed

<IRQ>
...
ath9k_hif_usb_rx_cb()
  ath9k_hif_usb_rx_stream()
   RX_STAT_INC() <--- htc_handle->drv_priv access

In order to not add fancy protection for drv_priv we can move
htc_handle->drv_priv initialization at the end of the
ath9k_htc_probe_device() and add helper macro to make
all *_STAT_* macros NULL safe, since syzbot has reported related NULL
deref in that macros [1]

Link: https://syzkaller.appspot.com/bug?id=6ead44e37afb6866ac0c7dd121b4ce07cb665f60 [0]
Link: https://syzkaller.appspot.com/bug?id=b8101ffcec107c0567a0cd8acbbacec91e9ee8de [1]
Fixes: fb9987d0f748 ("ath9k_htc: Support for AR9271 chipset.")
Reported-and-tested-by: syzbot+03110230a11411024147@syzkaller.appspotmail.com
Reported-and-tested-by: syzbot+c6dde1f690b60e0b9fbe@syzkaller.appspotmail.com
Signed-off-by: Pavel Skripkin <paskripkin@gmail.com>
Acked-by: Toke Høiland-Jørgensen <toke@toke.dk>
Signed-off-by: Kalle Valo <quic_kvalo@quicinc.com>
Link: https://lore.kernel.org/r/d57bbedc857950659bfacac0ab48790c1eda00c8.1655145743.git.paskripkin@gmail.com
(cherry picked from commit 0ac4827f78c7ffe8eef074bc010e7e34bc22f533 linux-next)
Signed-off-by: You-Sheng Yang (vicamo) <vicamo@gmail.com>

Author: Deren Wu
Author Date: 2022-06-08 12:53:26 UTC

UBUNTU: SAUCE: 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 <sean.wang@mediatek.com>
Signed-off-by: Deren Wu <deren.wu@mediatek.com>
(cherry picked from https://patchwork.kernel.org/project/linux-wireless/patch/21366e8bc70573794b5f12372f2e55e9059d8457.1654691030.git.deren.wu@mediatek.com/)
Signed-off-by: You-Sheng Yang (vicamo) <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2021-09-16 07:22:04 UTC

UBUNTU: SAUCE: vmd: fixup bridge ASPM by driver name instead

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

Additional VMD bridge IDs needed for new Alder Lake platforms, but
actually there is no a complete list for them. Here we match bridge
devices if they're directly attached to a VMD controller instead.

Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>
Signed-off-by: Timo Aaltonen <timo.aaltonen@canonical.com>

Author: Haijun Liu
Author Date: 2022-06-28 16:50:24 UTC

UBUNTU: SAUCE: net: wwan: t7xx: Add AP CLDMA and GNSS port

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

The t7xx device contains two Cross Layer DMA (CLDMA) interfaces to
communicate with AP and Modem processors respectively. So far only
MD-CLDMA was being used, this patch enables AP-CLDMA and the GNSS
port which requires such channel.

GNSS AT control port allows Modem Manager to control GPS for:
- Start/Stop GNSS sessions,
- Configuration commands to support Assisted GNSS positioning
- Crash & reboot (notifications when resetting device (AP) & host)
- Settings to Enable/Disable GNSS solution
- Geofencing

Rename small Application Processor (sAP) to AP.

Signed-off-by: Haijun Liu <haijun.liu@mediatek.com>
Co-developed-by: Madhusmita Sahu <madhusmita.sahu@intel.com>
Signed-off-by: Madhusmita Sahu <madhusmita.sahu@intel.com>
Signed-off-by: Moises Veleta <moises.veleta@linux.intel.com>

Change log in v2:
- Add to commit message renaming sAP to AP
- Add to commit message GNSS AT port info
- Lowercase X in constant prefix
- Add GNSS AT comment in static port file
Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
Reviewed-by: M Chetan Kumar <m.chetan.kumar@intel.com>
(cherry picked from commit
https://patchwork.kernel.org/project/netdevbpf/patch/20220628165024.25718-1-moises.veleta@linux.intel.com/)
Signed-off-by: You-Sheng Yang (vicamo) <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2022-01-05 14:28:52 UTC

UBUNTU: [Config] enable X86_AMD_PSTATE as built-in on amd64

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

X86_AMD_PSTATE must be a built-in module so that it may take take
precedence over acpi-cpufreq.

Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Linus Torvalds
Author Date: 2005-04-16 22:20:36 UTC

Linux-2.6.12-rc2

Initial git repository build. I'm not bothering with the full history,
even though we have it. We can create a separate "historical" git
archive of that later if we want to, and in the meantime it's about
3.2GB when imported into git - space that would just make the early
git days unnecessarily complicated, when we don't have a lot of good
infrastructure for it.

Let it rip!