lp:~vicamo/+git/ubuntu-kernel

Author: mtkapsoc
Author Date: 2022-01-07 07:30:03 UTC

UBUNTU: SAUCE: mt76: mt7921e: fix possible probe failure after reboot

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

It doesn't guarantee the mt7921e gets started with ASPM L0 after each
machine reboot on every platform.

If mt7921e gets started with not ASPM L0, it would be possible that the
driver encounters time to time failure in mt7921_pci_probe, like a
weird chip identifier is read

[ 215.514503] mt7921e 0000:05:00.0: ASIC revision: feed0000
[ 216.604741] mt7921e: probe of 0000:05:00.0 failed with error -110

or failing to init hardware because the driver is not allowed to access the
register until the device is in ASPM L0 state. So, we call
__mt7921e_mcu_drv_pmctrl in early mt7921_pci_probe to force the device
to bring back to the L0 state for we can safely access registers in any
case.

In the patch, we move all functions from dma.c to pci.c and register mt76
bus operation earilier, that is the __mt7921e_mcu_drv_pmctrl depends on.

Fixes: bf3747ae2e25 ("mt76: mt7921: enable aspm by default")
Reported-by: Kai-Chuan Hsieh <kaichuan.hsieh@canonical.com>
Co-developed-by: Deren Wu <deren.wu@mediatek.com>
Signed-off-by: Deren Wu <deren.wu@mediatek.com>
Signed-off-by: Sean Wang <sean.wang@mediatek.com>
Tested-by: Khalid Aziz <khalid@gonehiking.org>
(cherry picked from https://patchwork.kernel.org/project/linux-mediatek/patch/70e27cbc652cbdb78277b9c691a3a5ba02653afb.1641540175.git.objelf@gmail.com/)
Signed-off-by: You-Sheng Yang (vicamo) <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2022-05-03 09:08:21 UTC

Bug 1950282: Fibocom WWAN FM350-GL-00 (Mediatek M80 5G) support

Author: You-Sheng Yang
Author Date: 2022-04-19 16:17:53 UTC

Bug 1969434: build backport-iwlwifi-dkms as linux-modules-iwlwifi-ABI

Author: You-Sheng Yang
Author Date: 2022-04-19 01:52:29 UTC

UBUNTU: [Packaging] enable iwlwifi standalone modules build

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

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

Author: Mario Limonciello via iommu
Author Date: 2022-04-04 20:47:23 UTC

UBUNTU: SAUCE: dma-iommu: Check that swiotlb is active before trying to use it

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

If the IOMMU is in use and an untrusted device is connected to an external
facing port but the address requested isn't page aligned will cause the
kernel to attempt to use bounce buffers.

If for some reason the bounce buffers have not been allocated this is a
problem that should be made apparent to the user.

Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
(cherry picked from https://lore.kernel.org/linux-iommu/20220404204723.9767-3-mario.limonciello@amd.com)
Signed-off-by: You-Sheng Yang (vicamo) <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2022-04-13 08:49:43 UTC

Bug 1968525: PCI: vmd: Enable PCIe ASPM and LTR

Author: You-Sheng Yang
Author Date: 2022-04-13 08:49:43 UTC

Bug 1968525: PCI: vmd: Enable PCIe ASPM and LTR

Author: You-Sheng Yang
Author Date: 2022-04-13 08:49:43 UTC

Bug 1968525: PCI: vmd: Enable PCIe ASPM and LTR

Author: David Box
Author Date: 2022-03-01 04:19:43 UTC

UBUNTU: SAUCE: PCI: vmd: Configure PCIe ASPM and LTR

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

PCIe ports reserved for VMD use are not visible to BIOS and therefore not
configured to enable PCIE ASPM. Additionally, PCIE LTR values may be left
unset since BIOS will set a default maximum LTR value on endpoints to
ensure that they don't block SoC power management. Lack of this programming
results in high power consumption on laptops as reported in bugzilla [1].
For currently affected products, use pci_enable_default_link_state to set
the allowed link states for devices on the root ports. Also set the LTR
value to the maximum value needed for the SoC. Per the VMD hardware team
future products using VMD will enable BIOS configuration of these
capabilities. This solution is a workaround for current products that
mainly targets laptops. Support is not provided if a switch used nor for
hotplug.

[1] https://bugzilla.kernel.org/show_bug.cgi?id=213717

Signed-off-by: Michael Bottini <michael.a.bottini@linux.intel.com>
Signed-off-by: David E. Box <david.e.box@linux.intel.com>
(cherry picked from https://lore.kernel.org/linux-pci/20220301041943.2935892-4-david.e.box@linux.intel.com/)
Signed-off-by: You-Sheng Yang (vicamo) <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2022-04-11 07:19:59 UTC

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

Author: You-Sheng Yang
Author Date: 2022-04-11 07:19:59 UTC

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

Author: You-Sheng Yang
Author Date: 2021-11-02 10:23:57 UTC

Experimental kernel changes

Author: Hao Yao
Author Date: 2022-03-30 12:44:40 UTC

UBUNTU: SAUCE: media: pci: intel: Avoid UBSAN warnings of index bound and shift

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

UBSAN is default enabled on 5.15 kernel on Ubuntu. The code to
allocate resources in IPU can cause some array-index-out-of-bounds
and shift-out-of-bounds warnings, so it needs to be fixed.

Signed-off-by: Hao Yao <hao.yao@intel.com>
(cherry picked from commit 8dcb7d8df28fd311a72f3d996b02231e38aac8a7)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2022-01-05 14:50:32 UTC

Bug 1956509: Enable AMD P-State

Author: You-Sheng Yang
Author Date: 2022-01-05 14:50:32 UTC

Bug 1956509: Enable AMD P-State

Author: You-Sheng Yang
Author Date: 2022-01-05 14:50:32 UTC

Bug 1956509: Enable AMD P-State

Author: You-Sheng Yang
Author Date: 2022-04-01 11:59:15 UTC

Bug 1967510: IPU6: 2022-04-01 Andrews MLK PV release

Author: Ricardo Martinez
Author Date: 2022-02-23 22:33:26 UTC

UBUNTU: SAUCE: net: wwan: t7xx: Add maintainers and documentation

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

Adds maintainers and documentation for MediaTek t7xx 5G WWAN modem
device driver.

Signed-off-by: Ricardo Martinez <ricardo.martinez@linux.intel.com>

>From a WWAN framework perspective:
Reviewed-by: Loic Poulain <loic.poulain@linaro.org>

(cherry picked from https://lore.kernel.org/netdev/20220114010627.21104-14-ricardo.martinez@linux.intel.com/raw)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2022-03-10 06:25:09 UTC

Bug 1962349: Bolt doesn't work with native USB4 hosts on AMD Yellow Carp

Author: Mario Limonciello
Author Date: 2022-03-09 22:43:02 UTC

UBUNTU: SAUCE: PCI: ACPI: Don't blindly trust `HotPlugSupportInD3`

BugLink: https://bugs.launchpad.net/amd/+bug/1962350

The `_DSD` `HotPlugSupportInD3` is supposed to indicate the ability for a
bridge to be able to wakeup from D3.

This however is static information in the ACPI table at BIOS compilation
time and on some platforms it's possible to configure the firmware at boot
up such that `_S0W` will not return "0" indicating the inability to wake
up the system from D3.

To fix these situations explicitly check that the ACPI device claims the
system can be awoken in `acpi_pci_bridge_d3`.

Link: https://uefi.org/htmlspecs/ACPI_Spec_6_4_html/07_Power_and_Performance_Mgmt/device-power-management-objects.html?highlight=s0w#s0w-s0-device-wake-state
Link: https://docs.microsoft.com/en-us/windows-hardware/drivers/pci/dsd-for-pcie-root-ports#identifying-pcie-root-ports-supporting-hot-plug-in-d3
Fixes: 26ad34d510a87 ("PCI / ACPI: Whitelist D3 for more PCIe hotplug ports")
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
(cherry picked from https://lore.kernel.org/linux-pci/20220309224302.2625343-1-mario.limonciello@amd.com/)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2022-02-23 03:14:07 UTC

Bug 1961746: drm/amd/display: Fix stream->link_enc unassigned during stream removal

Author: You-Sheng Yang
Author Date: 2022-02-22 03:31:50 UTC

Bug 1961646: Fix s2idle on AMD platforms without proper fw support

Author: You-Sheng Yang
Author Date: 2022-02-22 03:31:50 UTC

Bug 1961646: Fix s2idle on AMD platforms without proper fw support

Author: You-Sheng Yang
Author Date: 2022-02-22 03:31:50 UTC

Bug 1961646: Fix s2idle on AMD platforms without proper fw support

Author: You-Sheng Yang
Author Date: 2022-02-21 14:48:10 UTC

Bug 1948375: iwlwifi: bump FW API to 67 for AX devices

Author: You-Sheng Yang
Author Date: 2022-02-15 02:32:36 UTC

Bug 1950062: i2c: piix4: Replace cd6h/cd7h port I/O accesses with MMIO accesses

Author: You-Sheng Yang
Author Date: 2022-02-15 02:32:36 UTC

Bug 1950062: i2c: piix4: Replace cd6h/cd7h port I/O accesses with MMIO accesses

Author: mtkapsoc
Author Date: 2022-01-07 07:30:03 UTC

mt76: mt7921e: fix possible probe failure after reboot

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

It doesn't guarantee the mt7921e gets started with ASPM L0 after each
machine reboot on every platform.

If mt7921e gets started with not ASPM L0, it would be possible that the
driver encounters time to time failure in mt7921_pci_probe, like a
weird chip identifier is read

[ 215.514503] mt7921e 0000:05:00.0: ASIC revision: feed0000
[ 216.604741] mt7921e: probe of 0000:05:00.0 failed with error -110

or failing to init hardware because the driver is not allowed to access the
register until the device is in ASPM L0 state. So, we call
__mt7921e_mcu_drv_pmctrl in early mt7921_pci_probe to force the device
to bring back to the L0 state for we can safely access registers in any
case.

In the patch, we move all functions from dma.c to pci.c and register mt76
bus operation earilier, that is the __mt7921e_mcu_drv_pmctrl depends on.

Fixes: bf3747ae2e25 ("mt76: mt7921: enable aspm by default")
Reported-by: Kai-Chuan Hsieh <kaichuan.hsieh@canonical.com>
Co-developed-by: Deren Wu <deren.wu@mediatek.com>
Signed-off-by: Deren Wu <deren.wu@mediatek.com>
Signed-off-by: Sean Wang <sean.wang@mediatek.com>
Signed-off-by: Felix Fietkau <nbd@nbd.name>
(cherry picked from commit 602cc0c9618a819ab00ea3c9400742a0ca318380)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2022-01-27 09:24:26 UTC

Bug 1954938: UBUNTU: SAUCE: ath11k: shrink TCSR read mask for WCN6855 hw2.1

Author: You-Sheng Yang
Author Date: 2022-01-28 06:56:58 UTC

Bug 1945154/1952215/1958850: test kernel for K.C

Author: You-Sheng Yang
Author Date: 2022-01-27 09:24:26 UTC

Bug 1954938: UBUNTU: SAUCE: ath11k: shrink TCSR read mask for WCN6855 hw2.1

Author: You-Sheng Yang
Author Date: 2022-01-27 08:16:48 UTC

Bug 1954938: ath11k: add support for WCN6855 hw2.1

Author: You-Sheng Yang
Author Date: 2022-01-11 10:40:08 UTC

Bug 1957026: Enable S0i3 on AMD GPU Yellow Carp B0 Si

Author: You-Sheng Yang
Author Date: 2022-01-18 10:31:15 UTC

Bug 1958229: drm/amd/display: Fix out of bounds access on DNC31 stream encoder regs

Author: You-Sheng Yang
Author Date: 2022-01-06 09:13:52 UTC

Bug 1956497: drm/amd/display: explicitly set is_dsc_supported to false before use

Author: You-Sheng Yang
Author Date: 2021-12-27 07:20:29 UTC

Bug 1955383: Support MIPI camera through Intel IPU6

Author: You-Sheng Yang
Author Date: 2021-12-27 07:20:29 UTC

Bug 1955383: Support MIPI camera through Intel IPU6

Author: You-Sheng Yang
Author Date: 2021-12-27 07:20:29 UTC

Bug 1955383: Support MIPI camera through Intel IPU6

Author: You-Sheng Yang
Author Date: 2022-01-14 14:09:57 UTC

focal

Author: You-Sheng Yang
Author Date: 2021-12-27 07:20:29 UTC

Bug 1955383: Support MIPI camera through Intel IPU6

Author: You-Sheng Yang
Author Date: 2021-12-27 07:20:29 UTC

Bug 1955383: Support MIPI camera through Intel IPU6

Author: You-Sheng Yang
Author Date: 2022-01-12 10:53:24 UTC

Bug 1948375: iwlwifi: Increase microcodes loading timeout

Author: You-Sheng Yang
Author Date: 2022-01-04 07:53:52 UTC

Bug 1953008: Support USB4 DP alt mode for AMD Yellow Carp graphics card

Author: You-Sheng Yang
Author Date: 2022-01-06 10:12:18 UTC

Bug xxx: On AMD platforms only offer s2idle w/ proper FW

Author: Mario Limonciello
Author Date: 2022-01-05 19:39:10 UTC

acpi: sleep: Don't offer s2idle on AMD platforms without LPS0

On some OEM platforms a BIOS option is offered that will set the
sleep mode between S3 and S2idle. This option will change certain HW
behaviors. When in S2idle mode, Linux works properly. However when S3 mode
is picked but the user chooses S2idle in Linux the platform may not be
properly resumed.

To avoid users getting into this situation, don't offer s2idle on AMD
systems missing the LPS0 device either by a BIOS option or by using the
acpi "no_sleep_lps0" module parameter.

Reported-by: Bjoren Dasse <bjoern.daase@gmail.com>
BugLink: https://gitlab.freedesktop.org/drm/amd/-/issues/1824
BugLink: https://bugzilla.kernel.org/show_bug.cgi?id=215387
Reviewed-by: Basavaraj Natikar <Basavaraj.Natikar@amd.com>
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
(cherry picked from
https://lore.kernel.org/linux-acpi/20220105193910.25678-4-mario.limonciello@amd.com/)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Mario Limonciello
Author Date: 2022-01-05 18:48:16 UTC

drm/amd/display: explicitly set is_dsc_supported to false before use

When UBSAN is enabled a case is shown on unplugging the display that
this variable hasn't been initialized by `update_dsc_caps`, presumably
when the display was unplugged it wasn't copied from the DPCD.

BugLink: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1956497
Signed-off-by: Mario Limonciello <mario.limonciello@amd.com>
Change-Id: Ia4f292509bcccfbf2d0e239c52164cd4c885289b
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2021-12-27 07:20:29 UTC

Bug 1955383: Support MIPI camera through Intel IPU6

Author: You-Sheng Yang
Author Date: 2021-12-16 06:47:13 UTC

Bug 1954998: Add s0i3 support to AMD Sensor Fusion Hub (SFH) on Yellow Carp

Author: Richard Gong
Author Date: 2021-09-22 13:31:16 UTC

ACPI: processor idle: Allow playing dead in C3 state

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

When some cores are disabled on AMD platforms, the system will no longer
be able to enter suspend-to-idle s0ix.

Update to allow playing dead in C3 state so that the CPUs can enter the
deepest state on AMD platforms.

BugLink: https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Suggested-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Richard Gong <richard.gong@amd.com>
[ rjw: Fixed coding style ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
(cherry picked from commit d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Richard Gong
Author Date: 2021-09-22 13:31:16 UTC

ACPI: processor idle: Allow playing dead in C3 state

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

When some cores are disabled on AMD platforms, the system will no longer
be able to enter suspend-to-idle s0ix.

Update to allow playing dead in C3 state so that the CPUs can enter the
deepest state on AMD platforms.

BugLink: https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Suggested-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Richard Gong <richard.gong@amd.com>
[ rjw: Fixed coding style ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
(cherry picked from commit d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Richard Gong
Author Date: 2021-09-22 13:31:16 UTC

ACPI: processor idle: Allow playing dead in C3 state

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

When some cores are disabled on AMD platforms, the system will no longer
be able to enter suspend-to-idle s0ix.

Update to allow playing dead in C3 state so that the CPUs can enter the
deepest state on AMD platforms.

BugLink: https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Suggested-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Richard Gong <richard.gong@amd.com>
[ rjw: Fixed coding style ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
(cherry picked from commit d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Richard Gong
Author Date: 2021-09-22 13:31:16 UTC

ACPI: processor idle: Allow playing dead in C3 state

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

When some cores are disabled on AMD platforms, the system will no longer
be able to enter suspend-to-idle s0ix.

Update to allow playing dead in C3 state so that the CPUs can enter the
deepest state on AMD platforms.

BugLink: https://gitlab.freedesktop.org/drm/amd/-/issues/1708
Suggested-by: Mario Limonciello <mario.limonciello@amd.com>
Signed-off-by: Richard Gong <richard.gong@amd.com>
[ rjw: Fixed coding style ]
Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
(cherry picked from commit d6b88ce2eb9d2698eb24451eb92c0a1649b17bb1)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2021-12-14 13:51:50 UTC

Bug 1953008: Support USB4 DP alt mode for AMD Yellow Carp graphics card

Author: You-Sheng Yang
Author Date: 2021-12-14 12:44:37 UTC

Bug 1953008: Support USB4 DP alt mode for AMD Yellow Carp graphics card

Author: Nicholas Kazlauskas
Author Date: 2021-11-04 20:52:07 UTC

drm/amd/display: Add callbacks for DMUB HPD IRQ notifications

[Why]
We need HPD IRQ notifications (RX, short pulse) to properly handle
DP MST for DPIA connections.

[How]
A null pointer exception currently occurs when these are received
so add a check to validate that we have a handler installed for
the notification.

Extend the HPD handler to also handle HPD IRQ (RX) since the logic is
the same.

Fixes: 00be4268d32c ("drm/amd/display: Support for DMUB HPD interrupt handling")

Reviewed-by: Wayne Lin <Wayne.Lin@amd.com>
Reviewed-by: Jude Shih <shenshih@amd.com>
Acked-by: Anson Jacob <Anson.Jacob@amd.com>
Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Nicholas Kazlauskas
Author Date: 2021-11-04 20:52:07 UTC

drm/amd/display: Add callbacks for DMUB HPD IRQ notifications

[Why]
We need HPD IRQ notifications (RX, short pulse) to properly handle
DP MST for DPIA connections.

[How]
A null pointer exception currently occurs when these are received
so add a check to validate that we have a handler installed for
the notification.

Extend the HPD handler to also handle HPD IRQ (RX) since the logic is
the same.

Fixes: 00be4268d32c ("drm/amd/display: Support for DMUB HPD interrupt handling")

Reviewed-by: Wayne Lin <Wayne.Lin@amd.com>
Reviewed-by: Jude Shih <shenshih@amd.com>
Acked-by: Anson Jacob <Anson.Jacob@amd.com>
Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Nicholas Kazlauskas
Author Date: 2021-11-04 20:52:07 UTC

drm/amd/display: Add callbacks for DMUB HPD IRQ notifications

[Why]
We need HPD IRQ notifications (RX, short pulse) to properly handle
DP MST for DPIA connections.

[How]
A null pointer exception currently occurs when these are received
so add a check to validate that we have a handler installed for
the notification.

Extend the HPD handler to also handle HPD IRQ (RX) since the logic is
the same.

Fixes: 00be4268d32c ("drm/amd/display: Support for DMUB HPD interrupt handling")

Reviewed-by: Wayne Lin <Wayne.Lin@amd.com>
Reviewed-by: Jude Shih <shenshih@amd.com>
Acked-by: Anson Jacob <Anson.Jacob@amd.com>
Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: aaron.liu
Author Date: 2021-10-19 03:13:25 UTC

drm/amdgpu: support B0&B1 external revision id for yellow carp

B0 internal rev_id is 0x01, B1 internal rev_id is 0x02.
The external rev_id for B0 and B1 is 0x20.
The original expression is not suitable for B1.

Signed-off-by: Aaron Liu <aaron.liu@amd.com>
Reviewed-by: Huang Rui <ray.huang@amd.com>
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Nicholas Kazlauskas
Author Date: 2021-11-04 20:52:07 UTC

drm/amd/display: Add callbacks for DMUB HPD IRQ notifications

[Why]
We need HPD IRQ notifications (RX, short pulse) to properly handle
DP MST for DPIA connections.

[How]
A null pointer exception currently occurs when these are received
so add a check to validate that we have a handler installed for
the notification.

Extend the HPD handler to also handle HPD IRQ (RX) since the logic is
the same.

Fixes: 00be4268d32c ("drm/amd/display: Support for DMUB HPD interrupt handling")

Reviewed-by: Wayne Lin <Wayne.Lin@amd.com>
Reviewed-by: Jude Shih <shenshih@amd.com>
Acked-by: Anson Jacob <Anson.Jacob@amd.com>
Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Nicholas Kazlauskas
Author Date: 2021-11-04 20:52:07 UTC

drm/amd/display: Add callbacks for DMUB HPD IRQ notifications

[Why]
We need HPD IRQ notifications (RX, short pulse) to properly handle
DP MST for DPIA connections.

[How]
A null pointer exception currently occurs when these are received
so add a check to validate that we have a handler installed for
the notification.

Extend the HPD handler to also handle HPD IRQ (RX) since the logic is
the same.

Fixes: 00be4268d32c ("drm/amd/display: Support for DMUB HPD interrupt handling")

Reviewed-by: Wayne Lin <Wayne.Lin@amd.com>
Reviewed-by: Jude Shih <shenshih@amd.com>
Acked-by: Anson Jacob <Anson.Jacob@amd.com>
Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Nicholas Kazlauskas
Author Date: 2021-11-04 20:52:07 UTC

drm/amd/display: Add callbacks for DMUB HPD IRQ notifications

[Why]
We need HPD IRQ notifications (RX, short pulse) to properly handle
DP MST for DPIA connections.

[How]
A null pointer exception currently occurs when these are received
so add a check to validate that we have a handler installed for
the notification.

Extend the HPD handler to also handle HPD IRQ (RX) since the logic is
the same.

Fixes: 00be4268d32c ("drm/amd/display: Support for DMUB HPD interrupt handling")

Reviewed-by: Wayne Lin <Wayne.Lin@amd.com>
Reviewed-by: Jude Shih <shenshih@amd.com>
Acked-by: Anson Jacob <Anson.Jacob@amd.com>
Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Nicholas Kazlauskas
Author Date: 2021-11-04 20:52:07 UTC

drm/amd/display: Add callbacks for DMUB HPD IRQ notifications

[Why]
We need HPD IRQ notifications (RX, short pulse) to properly handle
DP MST for DPIA connections.

[How]
A null pointer exception currently occurs when these are received
so add a check to validate that we have a handler installed for
the notification.

Extend the HPD handler to also handle HPD IRQ (RX) since the logic is
the same.

Fixes: 00be4268d32c ("drm/amd/display: Support for DMUB HPD interrupt handling")

Reviewed-by: Wayne Lin <Wayne.Lin@amd.com>
Reviewed-by: Jude Shih <shenshih@amd.com>
Acked-by: Anson Jacob <Anson.Jacob@amd.com>
Signed-off-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Mark-YW.Chen
Author Date: 2021-12-06 17:33:43 UTC

UBUNTU: SAUCE: Bluetooth: btusb: Return error code when getting patch status failed

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

If there are failure cases in getting patch status, it should return the
error code (-EIO).

Fixes: fc342c4dc4087 ("Bluetooth: btusb: Add protocol support for MediaTek MT7921U USB devices")
Co-developed-by: Sean Wang <sean.wang@mediatek.com>
Signed-off-by: Sean Wang <sean.wang@mediatek.com>
Signed-off-by: Mark Chen <mark-yw.chen@mediatek.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
(backported from
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2021-12-13 06:08:10 UTC

Bug 1952714: platform/x86: amd-pmc: Fix s2idle failures on certain AMD laptops

Author: Mark-YW.Chen
Author Date: 2021-12-06 17:33:43 UTC

UBUNTU: SAUCE: Bluetooth: btusb: Return error code when getting patch status failed

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

If there are failure cases in getting patch status, it should return the
error code (-EIO).

Fixes: fc342c4dc4087 ("Bluetooth: btusb: Add protocol support for MediaTek MT7921U USB devices")
Co-developed-by: Sean Wang <sean.wang@mediatek.com>
Signed-off-by: Sean Wang <sean.wang@mediatek.com>
Signed-off-by: Mark Chen <mark-yw.chen@mediatek.com>
Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
(backported from
https://git.kernel.org/pub/scm/linux/kernel/git/bluetooth/bluetooth-next.git/commit/?id=995d948cf2e45834275f07afc1c9881a9902e73c)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Jude Shih
Author Date: 2021-09-16 02:38:01 UTC

drm/amd/display: Fix USB4 Aux via DMUB terminate unexpectedly

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

[Why]
Condition variable sometimes terminated unexpectedly

[How]
Use wait_for_completion_timeout to avoid unexpected termination of CV

Reviewed-by: Nicholas Kazlauskas <nicholas.kazlauskas@amd.com>
Acked-by: Wayne Lin <Wayne.Lin@amd.com>
Acked-by: Harry Wentland <harry.wentland@amd.com>
Signed-off-by: Jude Shih <shenshih@amd.com>
Backport-of: 9e3a50d23e31 ("drm/amd/display: Fix USB4 Aux via DMUB terminate unexpectedly")
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2021-11-18 09:25:45 UTC

focal

Author: You-Sheng Yang
Author Date: 2021-11-17 09:16:30 UTC

Bug 1951215: Revert patches for bug 1942043, 1948767, and 1943935

Author: You-Sheng Yang
Author Date: 2021-11-02 10:23:57 UTC

Bug 1949435: Support Intel CVF-based MIPI camera

Author: You-Sheng Yang
Author Date: 2021-11-02 10:23:57 UTC

Bug 1949435: Support Intel CVF-based MIPI camera

Author: You-Sheng Yang
Author Date: 2021-10-27 06:10:40 UTC

Bug 1948898: Bluetooth HCI reset fail during airplane mode switch stress tests

Author: You-Sheng Yang
Author Date: 2021-10-27 04:27:41 UTC

Bug 1940428: Revert "Bluetooth: Shutdown controller after workqueues are flushed or cancelled"

Author: You-Sheng Yang
Author Date: 2021-10-19 10:29:32 UTC

Bug 1939528: support Qualcomm WCN6856

Author: You-Sheng Yang
Author Date: 2021-10-12 07:32:20 UTC

Bug 1940028: AMD platforms hang at resuming from s2idle with SATA installed

Author: Anusha Srivatsa
Author Date: 2021-09-14 21:57:32 UTC

drm/i915/dmc: Update to DMC v2.12

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

The release notes mentions that this version-
1. Fix for unblock indication to punit.
2. Robustness fix for DC6/6v abort scenarios.

Cc: Imre Deak <Imre Deak <imre.deak@intel.com>>
Signed-off-by: Anusha Srivatsa <anusha.srivatsa@intel.com>
Reviewed-by: Imre Deak <imre.deak@intel.com>
Signed-off-by: Imre Deak <imre.deak@intel.com>
Link: https://patchwork.freedesktop.org/patch/msgid/20210914215732.67135-2-anusha.srivatsa@intel.com
(cherry picked from commit 259d71992e57c637aa0a5d3f4f7b9f689c186191)
Signed-off-by: Timo Aaltonen <timo.aaltonen@canonical.com>

Author: Kiran K
Author Date: 2021-07-13 03:27:55 UTC

UBUNTU: SAUCE: Bluetooth: btintel: Support Digital(N) + RF(N-1) combination

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

New generation Intel controllers(N) need to support RF from (N-1)
generation. Since PID comes from OTP present in RF module,
*setup* function gets mapped to BTUSB_INTEL_NEW instead of
BTUSB_INTEL_NEWGEN. This patch converges INTEL_NEW and INTEL_NEWGEN
mappings and defines a new generic *setup* function. All the
required information to load the correct driver is read from controller
in generic *setup* and branchs out appropriately.

Signed-off-by: Kiran K <kiran.k@intel.com>
Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
(backported from
https://lore.kernel.org/linux-bluetooth/20210713032755.19351-1-kiran.k@intel.com/T/#u)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Kiran K
Author Date: 2021-07-13 03:27:55 UTC

UBUNTU: SAUCE: Bluetooth: btintel: Support Digital(N) + RF(N-1) combination

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

New generation Intel controllers(N) need to support RF from (N-1)
generation. Since PID comes from OTP present in RF module,
*setup* function gets mapped to BTUSB_INTEL_NEW instead of
BTUSB_INTEL_NEWGEN. This patch converges INTEL_NEW and INTEL_NEWGEN
mappings and defines a new generic *setup* function. All the
required information to load the correct driver is read from controller
in generic *setup* and branchs out appropriately.

Signed-off-by: Kiran K <kiran.k@intel.com>
Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
(backported from
https://lore.kernel.org/linux-bluetooth/20210713032755.19351-1-kiran.k@intel.com/T/#u)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Kiran K
Author Date: 2021-07-13 03:27:55 UTC

UBUNTU: SAUCE: Bluetooth: btintel: Support Digital(N) + RF(N-1) combination

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

New generation Intel controllers(N) need to support RF from (N-1)
generation. Since PID comes from OTP present in RF module,
*setup* function gets mapped to BTUSB_INTEL_NEW instead of
BTUSB_INTEL_NEWGEN. This patch converges INTEL_NEW and INTEL_NEWGEN
mappings and defines a new generic *setup* function. All the
required information to load the correct driver is read from controller
in generic *setup* and branchs out appropriately.

Signed-off-by: Kiran K <kiran.k@intel.com>
Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
(backported from
https://lore.kernel.org/linux-bluetooth/20210713032755.19351-1-kiran.k@intel.com/T/#u)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2021-06-04 12:50:44 UTC

Bug XXX: add WWAN drivers

Author: You-Sheng Yang
Author Date: 2021-09-30 08:54:04 UTC

Bug 1945576: Intel I225-IT device probe failure

Author: You-Sheng Yang
Author Date: 2021-09-30 08:54:04 UTC

Bug 1945576: Intel I225-IT device probe failure

Author: You-Sheng Yang
Author Date: 2021-09-30 08:54:04 UTC

Bug 1945576: Intel I225-IT device probe failure

Author: You-Sheng Yang
Author Date: 2021-09-30 08:54:04 UTC

Bug 1945576: Intel I225-IT device probe failure

Author: Gongjun Song
Author Date: 2021-09-23 08:46:43 UTC

UBUNTU: SAUCE: ASoC: Intel: soc-acpi: add SKU 0B29 SoundWire configuration

BugLink: https://bugs.launchpad.net/bug/1943794

Product audio hardware configuration is rt711 on link2, two rt1319s
on link0 and link1, rt714 on link 3.

Signed-off-by: Gongjun Song <gongjun.song@intel.com>
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2021-09-27 09:23:33 UTC

Bug 1942835: test ADL-P i915 has_psr flag

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

Author: You-Sheng Yang
Author Date: 2021-08-19 16:10:36 UTC

Bug 1939937: ath10k: don't fail if IRAM write fails

Author: You-Sheng Yang
Author Date: 2021-08-19 16:10:36 UTC

Bug 1939937: ath10k: don't fail if IRAM write fails

Author: You-Sheng Yang
Author Date: 2021-08-19 16:10:36 UTC

Bug 1939937: ath10k: don't fail if IRAM write fails

Author: You-Sheng Yang
Author Date: 2021-07-19 05:29:45 UTC

Bump Debian version

Author: You-Sheng Yang
Author Date: 2021-09-23 07:49:33 UTC

Bug 1943353: Hang at resuming from s2idle on AMD Barcelo

Author: You-Sheng Yang
Author Date: 2021-09-23 07:49:33 UTC

Bug 1943353: Hang at resuming from s2idle on AMD Barcelo

Author: Takashi Iwai
Author Date: 2021-08-26 15:47:52 UTC

ALSA: hda: Disable runtime resume at shutdown

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

Although we modified the codec shutdown callback to perform
runtime-suspend, it's still not fully effective, as this may be
resumed again at any time later.

For fixing such an unwanted resume, this patch replaces
pm_runtime_suspend() with pm_runtime_force_suspend(), and call
pm_runtime_disable() afterward. It assures to keep the device
suspended.

Also for code simplification, we apply the code unconditionally; when
it's been already suspended, nothing would happen by calls of
snd_pcm_suspend_all() and pm_runtime_force_suspend(), just proceed to
pm_runtime_disable().

Fixes: b98444ed597d ("ALSA: hda: Suspend codec at shutdown")
Reported-and-tested-by: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
Link: https://lore.kernel.org/r/20210826154752.25674-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
(cherry picked from commit 2eaf1635f9d62a2774c1c8114db24456dfd00721)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Takashi Iwai
Author Date: 2021-08-26 15:47:52 UTC

ALSA: hda: Disable runtime resume at shutdown

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

Although we modified the codec shutdown callback to perform
runtime-suspend, it's still not fully effective, as this may be
resumed again at any time later.

For fixing such an unwanted resume, this patch replaces
pm_runtime_suspend() with pm_runtime_force_suspend(), and call
pm_runtime_disable() afterward. It assures to keep the device
suspended.

Also for code simplification, we apply the code unconditionally; when
it's been already suspended, nothing would happen by calls of
snd_pcm_suspend_all() and pm_runtime_force_suspend(), just proceed to
pm_runtime_disable().

Fixes: b98444ed597d ("ALSA: hda: Suspend codec at shutdown")
Reported-and-tested-by: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
Link: https://lore.kernel.org/r/20210826154752.25674-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
(cherry picked from commit 2eaf1635f9d62a2774c1c8114db24456dfd00721)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Takashi Iwai
Author Date: 2021-08-26 15:47:52 UTC

ALSA: hda: Disable runtime resume at shutdown

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

Although we modified the codec shutdown callback to perform
runtime-suspend, it's still not fully effective, as this may be
resumed again at any time later.

For fixing such an unwanted resume, this patch replaces
pm_runtime_suspend() with pm_runtime_force_suspend(), and call
pm_runtime_disable() afterward. It assures to keep the device
suspended.

Also for code simplification, we apply the code unconditionally; when
it's been already suspended, nothing would happen by calls of
snd_pcm_suspend_all() and pm_runtime_force_suspend(), just proceed to
pm_runtime_disable().

Fixes: b98444ed597d ("ALSA: hda: Suspend codec at shutdown")
Reported-and-tested-by: Vitaly Rodionov <vitalyr@opensource.cirrus.com>
Link: https://lore.kernel.org/r/20210826154752.25674-1-tiwai@suse.de
Signed-off-by: Takashi Iwai <tiwai@suse.de>
(cherry picked from commit 2eaf1635f9d62a2774c1c8114db24456dfd00721)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2021-08-12 06:52:02 UTC

UBUNTU: [Config] Enable Cirrus Logic HDA bridge support

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

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

Author: You-Sheng Yang
Author Date: 2021-06-04 12:50:44 UTC

Bug XXX: add WWAN drivers

Author: Abhishek Naik
Author Date: 2021-06-17 07:08:52 UTC

iwlwifi: mvm: Read acpi dsm to get unii4 enable/disable bitmap.

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

Read the UNII4 setting from the ACPI table and use it in the
LARI_CONFIG_CHANGE_CMD accordingly.

This setting allows OEMs to enable or disable UNII4, bypassing the FW
defaults.

Signed-off-by: Abhishek Naik <abhishek.naik@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Link: https://lore.kernel.org/r/iwlwifi.20210617100544.223090c509c4.If03cb5393607ae494041b6187bcec134d6a1e06d@changeid
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
(cherry picked from commit 54b4fda5a761f97b8918607dbb4cd3b9e711aab6)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Abhishek Naik
Author Date: 2021-06-17 07:08:52 UTC

iwlwifi: mvm: Read acpi dsm to get unii4 enable/disable bitmap.

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

Read the UNII4 setting from the ACPI table and use it in the
LARI_CONFIG_CHANGE_CMD accordingly.

This setting allows OEMs to enable or disable UNII4, bypassing the FW
defaults.

Signed-off-by: Abhishek Naik <abhishek.naik@intel.com>
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
Link: https://lore.kernel.org/r/iwlwifi.20210617100544.223090c509c4.If03cb5393607ae494041b6187bcec134d6a1e06d@changeid
Signed-off-by: Luca Coelho <luciano.coelho@intel.com>
(cherry picked from commit 54b4fda5a761f97b8918607dbb4cd3b9e711aab6)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: Kiran K
Author Date: 2021-07-13 03:27:55 UTC

UBUNTU: SAUCE: Bluetooth: btintel: Support Digital(N) + RF(N-1) combination

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

New generation Intel controllers(N) need to support RF from (N-1)
generation. Since PID comes from OTP present in RF module,
*setup* function gets mapped to BTUSB_INTEL_NEW instead of
BTUSB_INTEL_NEWGEN. This patch converges INTEL_NEW and INTEL_NEWGEN
mappings and defines a new generic *setup* function. All the
required information to load the correct driver is read from controller
in generic *setup* and branchs out appropriately.

Signed-off-by: Kiran K <kiran.k@intel.com>
Reviewed-by: Chethan T N <chethan.tumkur.narayan@intel.com>
Reviewed-by: Srivatsa Ravishankar <ravishankar.srivatsa@intel.com>
(cherry picked from
https://lore.kernel.org/linux-bluetooth/20210713032755.19351-1-kiran.k@intel.com/T/#u)
Signed-off-by: You-Sheng Yang <vicamo.yang@canonical.com>

Author: You-Sheng Yang
Author Date: 2021-08-20 09:12:00 UTC

UBUNTU: [Config] enable CONFIG_IWLWIFI_DEBUG