]> git.ipfire.org Git - thirdparty/kernel/stable-queue.git/commitdiff
5.16-stable patches
authorGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 24 Jan 2022 11:19:30 +0000 (12:19 +0100)
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>
Mon, 24 Jan 2022 11:19:30 +0000 (12:19 +0100)
added patches:
bluetooth-btusb-return-error-code-when-getting-patch-status-failed.patch
bluetooth-hci_sync-fix-not-setting-adv-set-duration.patch
can-mcp251xfd-mcp251xfd_tef_obj_read-fix-typo-in-error-message.patch
dmaengine-idxd-fix-wq-settings-post-wq-disable.patch
dmaengine-stm32-mdma-fix-stm32_mdma_ctbr_tsel_mask.patch
dmaengine-uniphier-xdmac-fix-type-of-address-variables.patch
documentation-acpi-fix-data-node-reference-documentation.patch
documentation-arch-remove-leftovers-from-cifs_weak_pw_hash.patch
documentation-arch-remove-leftovers-from-raw-device.patch
documentation-coresight-fix-documentation-issue.patch
documentation-dmaengine-correctly-describe-dmatest-with-channel-unset.patch
documentation-fix-firewire.rst-abi-file-path-error.patch
documentation-refer-to-config-randomize_base-for-kernel-address-space-randomization.patch
drm-vc4-hdmi-make-sure-the-device-is-powered-with-cec.patch
firmware-update-kconfig-help-text-for-google-firmware.patch
lib-kconfig.debug-make-test_kmod-depend-on-page_size_less_than_256kb.patch
media-correct-media_test_support-help-text.patch
media-rcar-csi2-optimize-the-selection-phtw-register.patch
net-usb-correct-reset-handling-of-smsc95xx.patch
rdma-hns-modify-the-mapping-attribute-of-doorbell-to-device.patch
rdma-rxe-fix-a-typo-in-opcode-name.patch
revert-net-mlx5-add-retry-mechanism-to-the-command-entry-index-allocation.patch
scsi-core-show-scmd_last-in-text-form.patch
scsi-ufs-ufs-mediatek-fix-error-checking-in-ufs_mtk_init_va09_pwr_ctrl.patch

25 files changed:
queue-5.16/bluetooth-btusb-return-error-code-when-getting-patch-status-failed.patch [new file with mode: 0644]
queue-5.16/bluetooth-hci_sync-fix-not-setting-adv-set-duration.patch [new file with mode: 0644]
queue-5.16/can-mcp251xfd-mcp251xfd_tef_obj_read-fix-typo-in-error-message.patch [new file with mode: 0644]
queue-5.16/dmaengine-idxd-fix-wq-settings-post-wq-disable.patch [new file with mode: 0644]
queue-5.16/dmaengine-stm32-mdma-fix-stm32_mdma_ctbr_tsel_mask.patch [new file with mode: 0644]
queue-5.16/dmaengine-uniphier-xdmac-fix-type-of-address-variables.patch [new file with mode: 0644]
queue-5.16/documentation-acpi-fix-data-node-reference-documentation.patch [new file with mode: 0644]
queue-5.16/documentation-arch-remove-leftovers-from-cifs_weak_pw_hash.patch [new file with mode: 0644]
queue-5.16/documentation-arch-remove-leftovers-from-raw-device.patch [new file with mode: 0644]
queue-5.16/documentation-coresight-fix-documentation-issue.patch [new file with mode: 0644]
queue-5.16/documentation-dmaengine-correctly-describe-dmatest-with-channel-unset.patch [new file with mode: 0644]
queue-5.16/documentation-fix-firewire.rst-abi-file-path-error.patch [new file with mode: 0644]
queue-5.16/documentation-refer-to-config-randomize_base-for-kernel-address-space-randomization.patch [new file with mode: 0644]
queue-5.16/drm-vc4-hdmi-make-sure-the-device-is-powered-with-cec.patch [new file with mode: 0644]
queue-5.16/firmware-update-kconfig-help-text-for-google-firmware.patch [new file with mode: 0644]
queue-5.16/lib-kconfig.debug-make-test_kmod-depend-on-page_size_less_than_256kb.patch [new file with mode: 0644]
queue-5.16/media-correct-media_test_support-help-text.patch [new file with mode: 0644]
queue-5.16/media-rcar-csi2-optimize-the-selection-phtw-register.patch [new file with mode: 0644]
queue-5.16/net-usb-correct-reset-handling-of-smsc95xx.patch [new file with mode: 0644]
queue-5.16/rdma-hns-modify-the-mapping-attribute-of-doorbell-to-device.patch [new file with mode: 0644]
queue-5.16/rdma-rxe-fix-a-typo-in-opcode-name.patch [new file with mode: 0644]
queue-5.16/revert-net-mlx5-add-retry-mechanism-to-the-command-entry-index-allocation.patch [new file with mode: 0644]
queue-5.16/scsi-core-show-scmd_last-in-text-form.patch [new file with mode: 0644]
queue-5.16/scsi-ufs-ufs-mediatek-fix-error-checking-in-ufs_mtk_init_va09_pwr_ctrl.patch [new file with mode: 0644]
queue-5.16/series

diff --git a/queue-5.16/bluetooth-btusb-return-error-code-when-getting-patch-status-failed.patch b/queue-5.16/bluetooth-btusb-return-error-code-when-getting-patch-status-failed.patch
new file mode 100644 (file)
index 0000000..bd212b8
--- /dev/null
@@ -0,0 +1,32 @@
+From 995d948cf2e45834275f07afc1c9881a9902e73c Mon Sep 17 00:00:00 2001
+From: Mark Chen <mark-yw.chen@mediatek.com>
+Date: Tue, 7 Dec 2021 01:33:43 +0800
+Subject: Bluetooth: btusb: Return error code when getting patch status failed
+
+From: Mark Chen <mark-yw.chen@mediatek.com>
+
+commit 995d948cf2e45834275f07afc1c9881a9902e73c upstream.
+
+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>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/bluetooth/btusb.c |    1 +
+ 1 file changed, 1 insertion(+)
+
+--- a/drivers/bluetooth/btusb.c
++++ b/drivers/bluetooth/btusb.c
+@@ -2600,6 +2600,7 @@ static int btusb_mtk_setup_firmware_79xx
+                               } else {
+                                       bt_dev_err(hdev, "Failed wmt patch dwnld status (%d)",
+                                                  status);
++                                      err = -EIO;
+                                       goto err_release_fw;
+                               }
+                       }
diff --git a/queue-5.16/bluetooth-hci_sync-fix-not-setting-adv-set-duration.patch b/queue-5.16/bluetooth-hci_sync-fix-not-setting-adv-set-duration.patch
new file mode 100644 (file)
index 0000000..43827eb
--- /dev/null
@@ -0,0 +1,32 @@
+From f16a491c65d9eb19398b25aefc10c2d3313d17b3 Mon Sep 17 00:00:00 2001
+From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
+Date: Mon, 1 Nov 2021 15:14:41 -0700
+Subject: Bluetooth: hci_sync: Fix not setting adv set duration
+
+From: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
+
+commit f16a491c65d9eb19398b25aefc10c2d3313d17b3 upstream.
+
+10bbffa3e88e attempted to fix the use of rotation duration as
+advertising duration but it didn't change the if condition which still
+uses the duration instead of the timeout.
+
+Fixes: 10bbffa3e88e ("Bluetooth: Fix using advertising instance duration as timeout")
+Signed-off-by: Luiz Augusto von Dentz <luiz.von.dentz@intel.com>
+Signed-off-by: Marcel Holtmann <marcel@holtmann.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ net/bluetooth/hci_request.c |    2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/net/bluetooth/hci_request.c
++++ b/net/bluetooth/hci_request.c
+@@ -1935,7 +1935,7 @@ int __hci_req_enable_ext_advertising(str
+       /* Set duration per instance since controller is responsible for
+        * scheduling it.
+        */
+-      if (adv_instance && adv_instance->duration) {
++      if (adv_instance && adv_instance->timeout) {
+               u16 duration = adv_instance->timeout * MSEC_PER_SEC;
+               /* Time = N * 10 ms */
diff --git a/queue-5.16/can-mcp251xfd-mcp251xfd_tef_obj_read-fix-typo-in-error-message.patch b/queue-5.16/can-mcp251xfd-mcp251xfd_tef_obj_read-fix-typo-in-error-message.patch
new file mode 100644 (file)
index 0000000..80e3296
--- /dev/null
@@ -0,0 +1,31 @@
+From 99e7cc3b3f85d9a583ab83f386315c59443509ae Mon Sep 17 00:00:00 2001
+From: Marc Kleine-Budde <mkl@pengutronix.de>
+Date: Fri, 23 Apr 2021 11:26:56 +0200
+Subject: can: mcp251xfd: mcp251xfd_tef_obj_read(): fix typo in error message
+
+From: Marc Kleine-Budde <mkl@pengutronix.de>
+
+commit 99e7cc3b3f85d9a583ab83f386315c59443509ae upstream.
+
+This patch fixes a typo in the error message in
+mcp251xfd_tef_obj_read(), if trying to read too many objects.
+
+Link: https://lore.kernel.org/all/20220105154300.1258636-3-mkl@pengutronix.de
+Fixes: 55e5b97f003e ("can: mcp25xxfd: add driver for Microchip MCP25xxFD SPI CAN")
+Signed-off-by: Marc Kleine-Budde <mkl@pengutronix.de>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/net/can/spi/mcp251xfd/mcp251xfd-core.c |    2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/drivers/net/can/spi/mcp251xfd/mcp251xfd-core.c
++++ b/drivers/net/can/spi/mcp251xfd/mcp251xfd-core.c
+@@ -1336,7 +1336,7 @@ mcp251xfd_tef_obj_read(const struct mcp2
+            len > tx_ring->obj_num ||
+            offset + len > tx_ring->obj_num)) {
+               netdev_err(priv->ndev,
+-                         "Trying to read to many TEF objects (max=%d, offset=%d, len=%d).\n",
++                         "Trying to read too many TEF objects (max=%d, offset=%d, len=%d).\n",
+                          tx_ring->obj_num, offset, len);
+               return -ERANGE;
+       }
diff --git a/queue-5.16/dmaengine-idxd-fix-wq-settings-post-wq-disable.patch b/queue-5.16/dmaengine-idxd-fix-wq-settings-post-wq-disable.patch
new file mode 100644 (file)
index 0000000..b0f49ab
--- /dev/null
@@ -0,0 +1,62 @@
+From 0f225705cf6536826318180831e18a74595efc8d Mon Sep 17 00:00:00 2001
+From: Dave Jiang <dave.jiang@intel.com>
+Date: Tue, 14 Dec 2021 13:15:17 -0700
+Subject: dmaengine: idxd: fix wq settings post wq disable
+
+From: Dave Jiang <dave.jiang@intel.com>
+
+commit 0f225705cf6536826318180831e18a74595efc8d upstream.
+
+By the spec, wq size and group association is not changeable unless device
+is disabled. Exclude clearing the shadow copy on wq disable/reset. This
+allows wq type to be changed after disable to be re-enabled.
+
+Move the size and group association to its own cleanup and only call it
+during device disable.
+
+Fixes: 0dcfe41e9a4c ("dmanegine: idxd: cleanup all device related bits after disabling device")
+Reported-by: Lucas Van <lucas.van@intel.com>
+Tested-by: Lucas Van <lucas.van@intel.com>
+Signed-off-by: Dave Jiang <dave.jiang@intel.com>
+Link: https://lore.kernel.org/r/163951291732.2987775.13576571320501115257.stgit@djiang5-desk3.ch.intel.com
+Signed-off-by: Vinod Koul <vkoul@kernel.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/dma/idxd/device.c |   12 ++++++++++--
+ 1 file changed, 10 insertions(+), 2 deletions(-)
+
+--- a/drivers/dma/idxd/device.c
++++ b/drivers/dma/idxd/device.c
+@@ -382,8 +382,6 @@ static void idxd_wq_disable_cleanup(stru
+       lockdep_assert_held(&wq->wq_lock);
+       memset(wq->wqcfg, 0, idxd->wqcfg_size);
+       wq->type = IDXD_WQT_NONE;
+-      wq->size = 0;
+-      wq->group = NULL;
+       wq->threshold = 0;
+       wq->priority = 0;
+       wq->ats_dis = 0;
+@@ -392,6 +390,15 @@ static void idxd_wq_disable_cleanup(stru
+       memset(wq->name, 0, WQ_NAME_SIZE);
+ }
++static void idxd_wq_device_reset_cleanup(struct idxd_wq *wq)
++{
++      lockdep_assert_held(&wq->wq_lock);
++
++      idxd_wq_disable_cleanup(wq);
++      wq->size = 0;
++      wq->group = NULL;
++}
++
+ static void idxd_wq_ref_release(struct percpu_ref *ref)
+ {
+       struct idxd_wq *wq = container_of(ref, struct idxd_wq, wq_active);
+@@ -699,6 +706,7 @@ static void idxd_device_wqs_clear_state(
+               if (wq->state == IDXD_WQ_ENABLED) {
+                       idxd_wq_disable_cleanup(wq);
++                      idxd_wq_device_reset_cleanup(wq);
+                       wq->state = IDXD_WQ_DISABLED;
+               }
+       }
diff --git a/queue-5.16/dmaengine-stm32-mdma-fix-stm32_mdma_ctbr_tsel_mask.patch b/queue-5.16/dmaengine-stm32-mdma-fix-stm32_mdma_ctbr_tsel_mask.patch
new file mode 100644 (file)
index 0000000..71cabf1
--- /dev/null
@@ -0,0 +1,31 @@
+From e7f110889a87307fb0fed408a5dee1707796ca04 Mon Sep 17 00:00:00 2001
+From: Amelie Delaunay <amelie.delaunay@foss.st.com>
+Date: Mon, 20 Dec 2021 17:58:27 +0100
+Subject: dmaengine: stm32-mdma: fix STM32_MDMA_CTBR_TSEL_MASK
+
+From: Amelie Delaunay <amelie.delaunay@foss.st.com>
+
+commit e7f110889a87307fb0fed408a5dee1707796ca04 upstream.
+
+This patch fixes STM32_MDMA_CTBR_TSEL_MASK, which is [5:0], not [7:0].
+
+Fixes: a4ffb13c8946 ("dmaengine: Add STM32 MDMA driver")
+Signed-off-by: Amelie Delaunay <amelie.delaunay@foss.st.com>
+Link: https://lore.kernel.org/r/20211220165827.1238097-1-amelie.delaunay@foss.st.com
+Signed-off-by: Vinod Koul <vkoul@kernel.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/dma/stm32-mdma.c |    2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/drivers/dma/stm32-mdma.c
++++ b/drivers/dma/stm32-mdma.c
+@@ -184,7 +184,7 @@
+ #define STM32_MDMA_CTBR(x)            (0x68 + 0x40 * (x))
+ #define STM32_MDMA_CTBR_DBUS          BIT(17)
+ #define STM32_MDMA_CTBR_SBUS          BIT(16)
+-#define STM32_MDMA_CTBR_TSEL_MASK     GENMASK(7, 0)
++#define STM32_MDMA_CTBR_TSEL_MASK     GENMASK(5, 0)
+ #define STM32_MDMA_CTBR_TSEL(n)               STM32_MDMA_SET(n, \
+                                                     STM32_MDMA_CTBR_TSEL_MASK)
diff --git a/queue-5.16/dmaengine-uniphier-xdmac-fix-type-of-address-variables.patch b/queue-5.16/dmaengine-uniphier-xdmac-fix-type-of-address-variables.patch
new file mode 100644 (file)
index 0000000..5e4cf69
--- /dev/null
@@ -0,0 +1,35 @@
+From 105a8c525675bb7d4d64871f9b2edf39460de881 Mon Sep 17 00:00:00 2001
+From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
+Date: Tue, 14 Dec 2021 13:42:43 +0900
+Subject: dmaengine: uniphier-xdmac: Fix type of address variables
+
+From: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
+
+commit 105a8c525675bb7d4d64871f9b2edf39460de881 upstream.
+
+The variables src_addr and dst_addr handle DMA addresses, so these should
+be declared as dma_addr_t.
+
+Fixes: 667b9251440b ("dmaengine: uniphier-xdmac: Add UniPhier external DMA controller driver")
+Signed-off-by: Kunihiko Hayashi <hayashi.kunihiko@socionext.com>
+Link: https://lore.kernel.org/r/1639456963-10232-1-git-send-email-hayashi.kunihiko@socionext.com
+Signed-off-by: Vinod Koul <vkoul@kernel.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/dma/uniphier-xdmac.c |    5 +++--
+ 1 file changed, 3 insertions(+), 2 deletions(-)
+
+--- a/drivers/dma/uniphier-xdmac.c
++++ b/drivers/dma/uniphier-xdmac.c
+@@ -131,8 +131,9 @@ uniphier_xdmac_next_desc(struct uniphier
+ static void uniphier_xdmac_chan_start(struct uniphier_xdmac_chan *xc,
+                                     struct uniphier_xdmac_desc *xd)
+ {
+-      u32 src_mode, src_addr, src_width;
+-      u32 dst_mode, dst_addr, dst_width;
++      u32 src_mode, src_width;
++      u32 dst_mode, dst_width;
++      dma_addr_t src_addr, dst_addr;
+       u32 val, its, tnum;
+       enum dma_slave_buswidth buswidth;
diff --git a/queue-5.16/documentation-acpi-fix-data-node-reference-documentation.patch b/queue-5.16/documentation-acpi-fix-data-node-reference-documentation.patch
new file mode 100644 (file)
index 0000000..3a34a4f
--- /dev/null
@@ -0,0 +1,66 @@
+From a11174952205d082f1658fab4314f0caf706e0a8 Mon Sep 17 00:00:00 2001
+From: Sakari Ailus <sakari.ailus@linux.intel.com>
+Date: Wed, 1 Dec 2021 14:59:31 +0200
+Subject: Documentation: ACPI: Fix data node reference documentation
+
+From: Sakari Ailus <sakari.ailus@linux.intel.com>
+
+commit a11174952205d082f1658fab4314f0caf706e0a8 upstream.
+
+The data node reference documentation was missing a package that must
+contain the property values, instead property name and multiple values
+being present in a single package. This is not aligned with the _DSD
+spec.
+
+Fix it by adding the package for the values.
+
+Also add the missing "reg" properties to two numbered nodes.
+
+Fixes: b10134a3643d ("ACPI: property: Document hierarchical data extension references")
+Signed-off-by: Sakari Ailus <sakari.ailus@linux.intel.com>
+Reviewed-by: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
+Signed-off-by: Rafael J. Wysocki <rafael.j.wysocki@intel.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ Documentation/firmware-guide/acpi/dsd/data-node-references.rst |   10 ++++++++--
+ 1 file changed, 8 insertions(+), 2 deletions(-)
+
+--- a/Documentation/firmware-guide/acpi/dsd/data-node-references.rst
++++ b/Documentation/firmware-guide/acpi/dsd/data-node-references.rst
+@@ -5,7 +5,7 @@
+ Referencing hierarchical data nodes
+ ===================================
+-:Copyright: |copy| 2018 Intel Corporation
++:Copyright: |copy| 2018, 2021 Intel Corporation
+ :Author: Sakari Ailus <sakari.ailus@linux.intel.com>
+ ACPI in general allows referring to device objects in the tree only.
+@@ -52,12 +52,14 @@ the ANOD object which is also the final
+           Name (NOD0, Package() {
+               ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
+               Package () {
++                  Package () { "reg", 0 },
+                   Package () { "random-property", 3 },
+               }
+           })
+           Name (NOD1, Package() {
+               ToUUID("dbb8e3e6-5886-4ba6-8795-1319f52a966b"),
+               Package () {
++                  Package () { "reg", 1 },
+                   Package () { "anothernode", "ANOD" },
+               }
+           })
+@@ -74,7 +76,11 @@ the ANOD object which is also the final
+           Name (_DSD, Package () {
+               ToUUID("daffd814-6eba-4d8c-8a91-bc9bbf4aa301"),
+               Package () {
+-                  Package () { "reference", ^DEV0, "node@1", "anothernode" },
++                  Package () {
++                      "reference", Package () {
++                          ^DEV0, "node@1", "anothernode"
++                      }
++                  },
+               }
+           })
+       }
diff --git a/queue-5.16/documentation-arch-remove-leftovers-from-cifs_weak_pw_hash.patch b/queue-5.16/documentation-arch-remove-leftovers-from-cifs_weak_pw_hash.patch
new file mode 100644 (file)
index 0000000..ddf12d5
--- /dev/null
@@ -0,0 +1,181 @@
+From 2ac7069ad7647cd1d9ca5b08765a1e116e13cdc4 Mon Sep 17 00:00:00 2001
+From: Alexandre Ghiti <alexandre.ghiti@canonical.com>
+Date: Thu, 16 Dec 2021 10:44:23 +0100
+Subject: Documentation, arch: Remove leftovers from CIFS_WEAK_PW_HASH
+
+From: Alexandre Ghiti <alexandre.ghiti@canonical.com>
+
+commit 2ac7069ad7647cd1d9ca5b08765a1e116e13cdc4 upstream.
+
+This config was removed so remove all references to it.
+
+Fixes: 76a3c92ec9e0 ("cifs: remove support for NTLM and weaker authentication algorithms")
+Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
+Reviewed-by: Steve French <smfrench@gmail.com>
+Acked-by: Arnd Bergmann <arnd@arndb.de> [arch/arm/configs]
+Acked-by: Thomas Bogendoerfer <tsbogend@alpha.franken.de>
+Signed-off-by: Arnd Bergmann <arnd@arndb.de>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ Documentation/admin-guide/cifs/usage.rst    |    7 +++----
+ arch/arm/configs/cm_x300_defconfig          |    1 -
+ arch/arm/configs/ezx_defconfig              |    1 -
+ arch/arm/configs/imote2_defconfig           |    1 -
+ arch/arm/configs/nhk8815_defconfig          |    1 -
+ arch/arm/configs/pxa_defconfig              |    1 -
+ arch/mips/configs/fuloong2e_defconfig       |    1 -
+ arch/mips/configs/malta_qemu_32r6_defconfig |    1 -
+ arch/mips/configs/maltaaprp_defconfig       |    1 -
+ arch/mips/configs/maltasmvp_defconfig       |    1 -
+ arch/mips/configs/maltasmvp_eva_defconfig   |    1 -
+ arch/mips/configs/maltaup_defconfig         |    1 -
+ arch/powerpc/configs/ppc6xx_defconfig       |    1 -
+ arch/sh/configs/titan_defconfig             |    1 -
+ 14 files changed, 3 insertions(+), 17 deletions(-)
+
+--- a/Documentation/admin-guide/cifs/usage.rst
++++ b/Documentation/admin-guide/cifs/usage.rst
+@@ -734,10 +734,9 @@ SecurityFlags             Flags which control secur
+                       using weaker password hashes is 0x37037 (lanman,
+                       plaintext, ntlm, ntlmv2, signing allowed).  Some
+                       SecurityFlags require the corresponding menuconfig
+-                      options to be enabled (lanman and plaintext require
+-                      CONFIG_CIFS_WEAK_PW_HASH for example).  Enabling
+-                      plaintext authentication currently requires also
+-                      enabling lanman authentication in the security flags
++                      options to be enabled.  Enabling plaintext
++                      authentication currently requires also enabling
++                      lanman authentication in the security flags
+                       because the cifs module only supports sending
+                       laintext passwords using the older lanman dialect
+                       form of the session setup SMB.  (e.g. for authentication
+--- a/arch/arm/configs/cm_x300_defconfig
++++ b/arch/arm/configs/cm_x300_defconfig
+@@ -146,7 +146,6 @@ CONFIG_NFS_V3_ACL=y
+ CONFIG_NFS_V4=y
+ CONFIG_ROOT_NFS=y
+ CONFIG_CIFS=m
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_PARTITION_ADVANCED=y
+ CONFIG_NLS_CODEPAGE_437=m
+ CONFIG_NLS_ISO8859_1=m
+--- a/arch/arm/configs/ezx_defconfig
++++ b/arch/arm/configs/ezx_defconfig
+@@ -314,7 +314,6 @@ CONFIG_NFSD_V3_ACL=y
+ CONFIG_SMB_FS=m
+ CONFIG_CIFS=m
+ CONFIG_CIFS_STATS=y
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+ CONFIG_NLS_CODEPAGE_437=m
+--- a/arch/arm/configs/imote2_defconfig
++++ b/arch/arm/configs/imote2_defconfig
+@@ -288,7 +288,6 @@ CONFIG_NFSD_V3_ACL=y
+ CONFIG_SMB_FS=m
+ CONFIG_CIFS=m
+ CONFIG_CIFS_STATS=y
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+ CONFIG_NLS_CODEPAGE_437=m
+--- a/arch/arm/configs/nhk8815_defconfig
++++ b/arch/arm/configs/nhk8815_defconfig
+@@ -127,7 +127,6 @@ CONFIG_NFS_FS=y
+ CONFIG_NFS_V3_ACL=y
+ CONFIG_ROOT_NFS=y
+ CONFIG_CIFS=m
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_NLS_CODEPAGE_437=y
+ CONFIG_NLS_ASCII=y
+ CONFIG_NLS_ISO8859_1=y
+--- a/arch/arm/configs/pxa_defconfig
++++ b/arch/arm/configs/pxa_defconfig
+@@ -699,7 +699,6 @@ CONFIG_NFSD_V3_ACL=y
+ CONFIG_NFSD_V4=y
+ CONFIG_CIFS=m
+ CONFIG_CIFS_STATS=y
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+ CONFIG_NLS_DEFAULT="utf8"
+--- a/arch/mips/configs/fuloong2e_defconfig
++++ b/arch/mips/configs/fuloong2e_defconfig
+@@ -206,7 +206,6 @@ CONFIG_NFSD_V3_ACL=y
+ CONFIG_NFSD_V4=y
+ CONFIG_CIFS=m
+ CONFIG_CIFS_STATS2=y
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+ CONFIG_CIFS_DEBUG2=y
+--- a/arch/mips/configs/malta_qemu_32r6_defconfig
++++ b/arch/mips/configs/malta_qemu_32r6_defconfig
+@@ -165,7 +165,6 @@ CONFIG_TMPFS=y
+ CONFIG_NFS_FS=y
+ CONFIG_ROOT_NFS=y
+ CONFIG_CIFS=m
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+ CONFIG_NLS_CODEPAGE_437=m
+--- a/arch/mips/configs/maltaaprp_defconfig
++++ b/arch/mips/configs/maltaaprp_defconfig
+@@ -166,7 +166,6 @@ CONFIG_TMPFS=y
+ CONFIG_NFS_FS=y
+ CONFIG_ROOT_NFS=y
+ CONFIG_CIFS=m
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+ CONFIG_NLS_CODEPAGE_437=m
+--- a/arch/mips/configs/maltasmvp_defconfig
++++ b/arch/mips/configs/maltasmvp_defconfig
+@@ -167,7 +167,6 @@ CONFIG_TMPFS=y
+ CONFIG_NFS_FS=y
+ CONFIG_ROOT_NFS=y
+ CONFIG_CIFS=m
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+ CONFIG_NLS_CODEPAGE_437=m
+--- a/arch/mips/configs/maltasmvp_eva_defconfig
++++ b/arch/mips/configs/maltasmvp_eva_defconfig
+@@ -169,7 +169,6 @@ CONFIG_TMPFS=y
+ CONFIG_NFS_FS=y
+ CONFIG_ROOT_NFS=y
+ CONFIG_CIFS=m
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+ CONFIG_NLS_CODEPAGE_437=m
+--- a/arch/mips/configs/maltaup_defconfig
++++ b/arch/mips/configs/maltaup_defconfig
+@@ -165,7 +165,6 @@ CONFIG_TMPFS=y
+ CONFIG_NFS_FS=y
+ CONFIG_ROOT_NFS=y
+ CONFIG_CIFS=m
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+ CONFIG_NLS_CODEPAGE_437=m
+--- a/arch/powerpc/configs/ppc6xx_defconfig
++++ b/arch/powerpc/configs/ppc6xx_defconfig
+@@ -1022,7 +1022,6 @@ CONFIG_NFSD=m
+ CONFIG_NFSD_V3_ACL=y
+ CONFIG_NFSD_V4=y
+ CONFIG_CIFS=m
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_CIFS_UPCALL=y
+ CONFIG_CIFS_XATTR=y
+ CONFIG_CIFS_POSIX=y
+--- a/arch/sh/configs/titan_defconfig
++++ b/arch/sh/configs/titan_defconfig
+@@ -242,7 +242,6 @@ CONFIG_NFSD=y
+ CONFIG_NFSD_V3=y
+ CONFIG_SMB_FS=m
+ CONFIG_CIFS=m
+-CONFIG_CIFS_WEAK_PW_HASH=y
+ CONFIG_PARTITION_ADVANCED=y
+ CONFIG_NLS_CODEPAGE_437=m
+ CONFIG_NLS_ASCII=m
diff --git a/queue-5.16/documentation-arch-remove-leftovers-from-raw-device.patch b/queue-5.16/documentation-arch-remove-leftovers-from-raw-device.patch
new file mode 100644 (file)
index 0000000..1f3d456
--- /dev/null
@@ -0,0 +1,82 @@
+From 473dcf0ffc31ce1135cd10578e7e06698cf51f4a Mon Sep 17 00:00:00 2001
+From: Alexandre Ghiti <alexandre.ghiti@canonical.com>
+Date: Thu, 16 Dec 2021 10:44:22 +0100
+Subject: Documentation, arch: Remove leftovers from raw device
+
+From: Alexandre Ghiti <alexandre.ghiti@canonical.com>
+
+commit 473dcf0ffc31ce1135cd10578e7e06698cf51f4a upstream.
+
+Raw device interface was removed so remove all references to configs
+related to it.
+
+Fixes: 603e4922f1c8 ("remove the raw driver")
+Signed-off-by: Alexandre Ghiti <alexandre.ghiti@canonical.com>
+Acked-by: Arnd Bergmann <arnd@arndb.de> [arch/arm/configs]
+Signed-off-by: Arnd Bergmann <arnd@arndb.de>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ Documentation/admin-guide/devices.txt  |    8 +-------
+ arch/arm/configs/spear13xx_defconfig   |    1 -
+ arch/arm/configs/spear3xx_defconfig    |    1 -
+ arch/arm/configs/spear6xx_defconfig    |    1 -
+ arch/powerpc/configs/pseries_defconfig |    1 -
+ 5 files changed, 1 insertion(+), 11 deletions(-)
+
+--- a/Documentation/admin-guide/devices.txt
++++ b/Documentation/admin-guide/devices.txt
+@@ -2339,13 +2339,7 @@
+               disks (see major number 3) except that the limit on
+               partitions is 31.
+- 162 char     Raw block device interface
+-                0 = /dev/rawctl       Raw I/O control device
+-                1 = /dev/raw/raw1     First raw I/O device
+-                2 = /dev/raw/raw2     Second raw I/O device
+-                  ...
+-               max minor number of raw device is set by kernel config
+-               MAX_RAW_DEVS or raw module parameter 'max_raw_devs'
++ 162 char     Used for (now removed) raw block device interface
+  163 char
+--- a/arch/arm/configs/spear13xx_defconfig
++++ b/arch/arm/configs/spear13xx_defconfig
+@@ -61,7 +61,6 @@ CONFIG_SERIAL_AMBA_PL011=y
+ CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
+ # CONFIG_HW_RANDOM is not set
+ CONFIG_RAW_DRIVER=y
+-CONFIG_MAX_RAW_DEVS=8192
+ CONFIG_I2C=y
+ CONFIG_I2C_DESIGNWARE_PLATFORM=y
+ CONFIG_SPI=y
+--- a/arch/arm/configs/spear3xx_defconfig
++++ b/arch/arm/configs/spear3xx_defconfig
+@@ -41,7 +41,6 @@ CONFIG_SERIAL_AMBA_PL011=y
+ CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
+ # CONFIG_HW_RANDOM is not set
+ CONFIG_RAW_DRIVER=y
+-CONFIG_MAX_RAW_DEVS=8192
+ CONFIG_I2C=y
+ CONFIG_I2C_DESIGNWARE_PLATFORM=y
+ CONFIG_SPI=y
+--- a/arch/arm/configs/spear6xx_defconfig
++++ b/arch/arm/configs/spear6xx_defconfig
+@@ -36,7 +36,6 @@ CONFIG_INPUT_FF_MEMLESS=y
+ CONFIG_SERIAL_AMBA_PL011=y
+ CONFIG_SERIAL_AMBA_PL011_CONSOLE=y
+ CONFIG_RAW_DRIVER=y
+-CONFIG_MAX_RAW_DEVS=8192
+ CONFIG_I2C=y
+ CONFIG_I2C_DESIGNWARE_PLATFORM=y
+ CONFIG_SPI=y
+--- a/arch/powerpc/configs/pseries_defconfig
++++ b/arch/powerpc/configs/pseries_defconfig
+@@ -189,7 +189,6 @@ CONFIG_HVCS=m
+ CONFIG_VIRTIO_CONSOLE=m
+ CONFIG_IBM_BSR=m
+ CONFIG_RAW_DRIVER=y
+-CONFIG_MAX_RAW_DEVS=1024
+ CONFIG_I2C_CHARDEV=y
+ CONFIG_FB=y
+ CONFIG_FIRMWARE_EDID=y
diff --git a/queue-5.16/documentation-coresight-fix-documentation-issue.patch b/queue-5.16/documentation-coresight-fix-documentation-issue.patch
new file mode 100644 (file)
index 0000000..520bb40
--- /dev/null
@@ -0,0 +1,52 @@
+From 66bd1333abd7fa191f13b929c9119d6cd3df27b0 Mon Sep 17 00:00:00 2001
+From: Mike Leach <mike.leach@linaro.org>
+Date: Wed, 17 Nov 2021 16:42:20 +0000
+Subject: Documentation: coresight: Fix documentation issue
+
+From: Mike Leach <mike.leach@linaro.org>
+
+commit 66bd1333abd7fa191f13b929c9119d6cd3df27b0 upstream.
+
+Fix the description of the directories and attributes used
+in cs_etm as used by perf.
+
+Drop the references to the 'configurations' sub-directory which
+had been removed in an earlier version of the patchset.
+
+Fixes: f71cd93d5ea4 ("Documentation: coresight: Add documentation for CoreSight config")
+Reported-by: German Gomex <german.gomez@arm.com>
+Signed-off-by: Mike Leach <mike.leach@linaro.org>
+Link: https://lore.kernel.org/r/20211117164220.14883-1-mike.leach@linaro.org
+Signed-off-by: Mathieu Poirier <mathieu.poirier@linaro.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ Documentation/trace/coresight/coresight-config.rst |   16 +++++-----------
+ 1 file changed, 5 insertions(+), 11 deletions(-)
+
+--- a/Documentation/trace/coresight/coresight-config.rst
++++ b/Documentation/trace/coresight/coresight-config.rst
+@@ -211,19 +211,13 @@ also declared in the perf 'cs_etm' event
+ be selected when running trace under perf::
+     $ ls /sys/devices/cs_etm
+-    configurations  format  perf_event_mux_interval_ms  sinks  type
+-    events  nr_addr_filters  power
++    cpu0  cpu2  events  nr_addr_filters               power  subsystem  uevent
++    cpu1  cpu3  format  perf_event_mux_interval_ms    sinks  type
+-Key directories here are 'configurations' - which lists the loaded
+-configurations, and 'events' - a generic perf directory which allows
+-selection on the perf command line.::
++The key directory here is 'events' - a generic perf directory which allows
++selection on the perf command line. As with the sinks entries, this provides
++a hash of the configuration name.
+-    $ ls configurations/
+-    autofdo
+-    $ cat configurations/autofdo
+-    0xa7c3dddd
+-
+-As with the sinks entries, this provides a hash of the configuration name.
+ The entry in the 'events' directory uses perfs built in syntax generator
+ to substitute the syntax for the name when evaluating the command::
diff --git a/queue-5.16/documentation-dmaengine-correctly-describe-dmatest-with-channel-unset.patch b/queue-5.16/documentation-dmaengine-correctly-describe-dmatest-with-channel-unset.patch
new file mode 100644 (file)
index 0000000..ae56250
--- /dev/null
@@ -0,0 +1,42 @@
+From c61d7b2ef141abf81140756b45860a2306f395a2 Mon Sep 17 00:00:00 2001
+From: Daniel Thompson <daniel.thompson@linaro.org>
+Date: Thu, 18 Nov 2021 10:09:52 +0000
+Subject: Documentation: dmaengine: Correctly describe dmatest with channel unset
+
+From: Daniel Thompson <daniel.thompson@linaro.org>
+
+commit c61d7b2ef141abf81140756b45860a2306f395a2 upstream.
+
+Currently the documentation states that channels must be configured before
+running the dmatest. This has not been true since commit 6b41030fdc79
+("dmaengine: dmatest: Restore default for channel"). Fix accordingly.
+
+Fixes: 6b41030fdc79 ("dmaengine: dmatest: Restore default for channel")
+Signed-off-by: Daniel Thompson <daniel.thompson@linaro.org>
+Link: https://lore.kernel.org/r/20211118100952.27268-3-daniel.thompson@linaro.org
+Signed-off-by: Vinod Koul <vkoul@kernel.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ Documentation/driver-api/dmaengine/dmatest.rst |    7 ++++---
+ 1 file changed, 4 insertions(+), 3 deletions(-)
+
+--- a/Documentation/driver-api/dmaengine/dmatest.rst
++++ b/Documentation/driver-api/dmaengine/dmatest.rst
+@@ -143,13 +143,14 @@ Part 5 - Handling channel allocation
+ Allocating Channels
+ -------------------
+-Channels are required to be configured prior to starting the test run.
+-Attempting to run the test without configuring the channels will fail.
++Channels do not need to be configured prior to starting a test run. Attempting
++to run the test without configuring the channels will result in testing any
++channels that are available.
+ Example::
+     % echo 1 > /sys/module/dmatest/parameters/run
+-    dmatest: Could not start test, no channels configured
++    dmatest: No channels configured, continue with any
+ Channels are registered using the "channel" parameter. Channels can be requested by their
+ name, once requested, the channel is registered and a pending thread is added to the test list.
diff --git a/queue-5.16/documentation-fix-firewire.rst-abi-file-path-error.patch b/queue-5.16/documentation-fix-firewire.rst-abi-file-path-error.patch
new file mode 100644 (file)
index 0000000..0bb0972
--- /dev/null
@@ -0,0 +1,46 @@
+From b0ac702f3329cdc8a06dcaac73183d4b5a2b942d Mon Sep 17 00:00:00 2001
+From: Randy Dunlap <rdunlap@infradead.org>
+Date: Tue, 18 Jan 2022 19:39:05 -0800
+Subject: Documentation: fix firewire.rst ABI file path error
+
+From: Randy Dunlap <rdunlap@infradead.org>
+
+commit b0ac702f3329cdc8a06dcaac73183d4b5a2b942d upstream.
+
+Adjust the path of the ABI files for firewire.rst to prevent a
+documentation build error. Prevents this problem:
+
+Sphinx parallel build error:
+docutils.utils.SystemMessage: Documentation/driver-api/firewire.rst:22: (SEVERE/4) Problems with "include" directive path:
+InputError: [Errno 2] No such file or directory: '../Documentation/driver-api/ABI/stable/firewire-cdev'.
+
+Fixes: 2f4830ef96d2 ("FireWire: add driver-api Introduction section")
+Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
+Tested-by: Akira Yokosawa <akiyks@gmail.com>
+Link: https://lore.kernel.org/r/20220119033905.4779-1-rdunlap@infradead.org
+Signed-off-by: Jonathan Corbet <corbet@lwn.net>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ Documentation/driver-api/firewire.rst |    4 ++--
+ 1 file changed, 2 insertions(+), 2 deletions(-)
+
+--- a/Documentation/driver-api/firewire.rst
++++ b/Documentation/driver-api/firewire.rst
+@@ -19,7 +19,7 @@ of kernel interfaces is available via ex
+ Firewire char device data structures
+ ====================================
+-.. include:: /ABI/stable/firewire-cdev
++.. include:: ../ABI/stable/firewire-cdev
+     :literal:
+ .. kernel-doc:: include/uapi/linux/firewire-cdev.h
+@@ -28,7 +28,7 @@ Firewire char device data structures
+ Firewire device probing and sysfs interfaces
+ ============================================
+-.. include:: /ABI/stable/sysfs-bus-firewire
++.. include:: ../ABI/stable/sysfs-bus-firewire
+     :literal:
+ .. kernel-doc:: drivers/firewire/core-device.c
diff --git a/queue-5.16/documentation-refer-to-config-randomize_base-for-kernel-address-space-randomization.patch b/queue-5.16/documentation-refer-to-config-randomize_base-for-kernel-address-space-randomization.patch
new file mode 100644 (file)
index 0000000..9e98301
--- /dev/null
@@ -0,0 +1,39 @@
+From 82ca67321f55a8d1da6ac3ed611da3c32818bb37 Mon Sep 17 00:00:00 2001
+From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
+Date: Thu, 30 Dec 2021 18:19:40 +0100
+Subject: Documentation: refer to config RANDOMIZE_BASE for kernel address-space randomization
+
+From: Lukas Bulwahn <lukas.bulwahn@gmail.com>
+
+commit 82ca67321f55a8d1da6ac3ed611da3c32818bb37 upstream.
+
+The config RANDOMIZE_SLAB does not exist, the authors probably intended to
+refer to the config RANDOMIZE_BASE, which provides kernel address-space
+randomization. They probably just confused SLAB with BASE (these two
+four-letter words coincidentally share three common letters), as they also
+point out the config SLAB_FREELIST_RANDOM as further randomization within
+the same sentence.
+
+Fix the reference of the config for kernel address-space randomization to
+the config that provides that.
+
+Fixes: 6e88559470f5 ("Documentation: Add section about CPU vulnerabilities for Spectre")
+Signed-off-by: Lukas Bulwahn <lukas.bulwahn@gmail.com>
+Link: https://lore.kernel.org/r/20211230171940.27558-1-lukas.bulwahn@gmail.com
+Signed-off-by: Jonathan Corbet <corbet@lwn.net>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ Documentation/admin-guide/hw-vuln/spectre.rst |    2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/Documentation/admin-guide/hw-vuln/spectre.rst
++++ b/Documentation/admin-guide/hw-vuln/spectre.rst
+@@ -468,7 +468,7 @@ Spectre variant 2
+    before invoking any firmware code to prevent Spectre variant 2 exploits
+    using the firmware.
+-   Using kernel address space randomization (CONFIG_RANDOMIZE_SLAB=y
++   Using kernel address space randomization (CONFIG_RANDOMIZE_BASE=y
+    and CONFIG_SLAB_FREELIST_RANDOM=y in the kernel configuration) makes
+    attacks on the kernel generally more difficult.
diff --git a/queue-5.16/drm-vc4-hdmi-make-sure-the-device-is-powered-with-cec.patch b/queue-5.16/drm-vc4-hdmi-make-sure-the-device-is-powered-with-cec.patch
new file mode 100644 (file)
index 0000000..3bd8a21
--- /dev/null
@@ -0,0 +1,55 @@
+From 20b0dfa86bef0e80b41b0e5ac38b92f23b6f27f9 Mon Sep 17 00:00:00 2001
+From: Maxime Ripard <maxime@cerno.tech>
+Date: Thu, 19 Aug 2021 15:59:30 +0200
+Subject: drm/vc4: hdmi: Make sure the device is powered with CEC
+
+From: Maxime Ripard <maxime@cerno.tech>
+
+commit 20b0dfa86bef0e80b41b0e5ac38b92f23b6f27f9 upstream.
+
+Similarly to what we encountered with the detect hook with DRM, nothing
+actually prevents any of the CEC callback from being run while the HDMI
+output is disabled.
+
+However, this is an issue since any register access to the controller
+when it's powered down will result in a silent hang.
+
+Let's make sure we run the runtime_pm hooks when the CEC adapter is
+opened and closed by the userspace to avoid that issue.
+
+Fixes: 15b4511a4af6 ("drm/vc4: add HDMI CEC support")
+Reviewed-by: Dave Stevenson <dave.stevenson@raspberrypi.com>
+Signed-off-by: Maxime Ripard <maxime@cerno.tech>
+Link: https://patchwork.freedesktop.org/patch/msgid/20210819135931.895976-6-maxime@cerno.tech
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/gpu/drm/vc4/vc4_hdmi.c |   10 +++++++++-
+ 1 file changed, 9 insertions(+), 1 deletion(-)
+
+--- a/drivers/gpu/drm/vc4/vc4_hdmi.c
++++ b/drivers/gpu/drm/vc4/vc4_hdmi.c
+@@ -1736,8 +1736,14 @@ static int vc4_hdmi_cec_adap_enable(stru
+       struct vc4_hdmi *vc4_hdmi = cec_get_drvdata(adap);
+       /* clock period in microseconds */
+       const u32 usecs = 1000000 / CEC_CLOCK_FREQ;
+-      u32 val = HDMI_READ(HDMI_CEC_CNTRL_5);
++      u32 val;
++      int ret;
++      ret = pm_runtime_resume_and_get(&vc4_hdmi->pdev->dev);
++      if (ret)
++              return ret;
++
++      val = HDMI_READ(HDMI_CEC_CNTRL_5);
+       val &= ~(VC4_HDMI_CEC_TX_SW_RESET | VC4_HDMI_CEC_RX_SW_RESET |
+                VC4_HDMI_CEC_CNT_TO_4700_US_MASK |
+                VC4_HDMI_CEC_CNT_TO_4500_US_MASK);
+@@ -1883,6 +1889,8 @@ static int vc4_hdmi_cec_init(struct vc4_
+       if (ret < 0)
+               goto err_remove_handlers;
++      pm_runtime_put(&vc4_hdmi->pdev->dev);
++
+       return 0;
+ err_remove_handlers:
diff --git a/queue-5.16/firmware-update-kconfig-help-text-for-google-firmware.patch b/queue-5.16/firmware-update-kconfig-help-text-for-google-firmware.patch
new file mode 100644 (file)
index 0000000..2b60044
--- /dev/null
@@ -0,0 +1,40 @@
+From d185a3466f0cd5af8f1c5c782c53bc0e6f2e7136 Mon Sep 17 00:00:00 2001
+From: Ben Hutchings <ben@decadent.org.uk>
+Date: Mon, 18 Jun 2018 23:55:40 +0100
+Subject: firmware: Update Kconfig help text for Google firmware
+
+From: Ben Hutchings <ben@decadent.org.uk>
+
+commit d185a3466f0cd5af8f1c5c782c53bc0e6f2e7136 upstream.
+
+The help text for GOOGLE_FIRMWARE states that it should only be
+enabled when building a kernel for Google's own servers.  However,
+many of the drivers dependent on it are also useful on Chromebooks or
+on any platform using coreboot.
+
+Update the help text to reflect this double duty.
+
+Fixes: d384d6f43d1e ("firmware: google memconsole: Add coreboot support")
+Reviewed-by: Julius Werner <jwerner@chromium.org>
+Signed-off-by: Ben Hutchings <ben@decadent.org.uk>
+Link: https://lore.kernel.org/r/20180618225540.GD14131@decadent.org.uk
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/firmware/google/Kconfig |    6 +++---
+ 1 file changed, 3 insertions(+), 3 deletions(-)
+
+--- a/drivers/firmware/google/Kconfig
++++ b/drivers/firmware/google/Kconfig
+@@ -3,9 +3,9 @@ menuconfig GOOGLE_FIRMWARE
+       bool "Google Firmware Drivers"
+       default n
+       help
+-        These firmware drivers are used by Google's servers.  They are
+-        only useful if you are working directly on one of their
+-        proprietary servers.  If in doubt, say "N".
++        These firmware drivers are used by Google servers,
++        Chromebooks and other devices using coreboot firmware.
++        If in doubt, say "N".
+ if GOOGLE_FIRMWARE
diff --git a/queue-5.16/lib-kconfig.debug-make-test_kmod-depend-on-page_size_less_than_256kb.patch b/queue-5.16/lib-kconfig.debug-make-test_kmod-depend-on-page_size_less_than_256kb.patch
new file mode 100644 (file)
index 0000000..331440b
--- /dev/null
@@ -0,0 +1,51 @@
+From bbd2e05fad3e692ff2495895975bd0fce02bdbae Mon Sep 17 00:00:00 2001
+From: Nathan Chancellor <nathan@kernel.org>
+Date: Wed, 19 Jan 2022 18:10:28 -0800
+Subject: lib/Kconfig.debug: make TEST_KMOD depend on PAGE_SIZE_LESS_THAN_256KB
+
+From: Nathan Chancellor <nathan@kernel.org>
+
+commit bbd2e05fad3e692ff2495895975bd0fce02bdbae upstream.
+
+Commit b05fbcc36be1 ("btrfs: disable build on platforms having page size
+256K") disabled btrfs for configurations that used a 256kB page size.
+However, it did not fully solve the problem because CONFIG_TEST_KMOD
+selects CONFIG_BTRFS, which does not account for the dependency.  This
+results in a Kconfig warning and the failed BUILD_BUG_ON error
+returning.
+
+  WARNING: unmet direct dependencies detected for BTRFS_FS
+    Depends on [n]: BLOCK [=y] && !PPC_256K_PAGES && !PAGE_SIZE_256KB [=y]
+    Selected by [m]:
+    - TEST_KMOD [=m] && RUNTIME_TESTING_MENU [=y] && m && MODULES [=y] && NETDEVICES [=y] && NET_CORE [=y] && INET [=y] && BLOCK [=y]
+
+To resolve this, add CONFIG_PAGE_SIZE_LESS_THAN_256KB as a dependency of
+CONFIG_TEST_KMOD so there is no more invalid configuration or build
+errors.
+
+Link: https://lkml.kernel.org/r/20211129230141.228085-4-nathan@kernel.org
+Fixes: b05fbcc36be1 ("btrfs: disable build on platforms having page size 256K")
+Signed-off-by: Nathan Chancellor <nathan@kernel.org>
+Reported-by: kernel test robot <lkp@intel.com>
+Cc: Chris Mason <clm@fb.com>
+Cc: David Sterba <dsterba@suse.com>
+Cc: Josef Bacik <josef@toxicpanda.com>
+Cc: Luis Chamberlain <mcgrof@kernel.org>
+Cc: Nick Desaulniers <ndesaulniers@google.com>
+Signed-off-by: Andrew Morton <akpm@linux-foundation.org>
+Signed-off-by: Linus Torvalds <torvalds@linux-foundation.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ lib/Kconfig.debug |    1 +
+ 1 file changed, 1 insertion(+)
+
+--- a/lib/Kconfig.debug
++++ b/lib/Kconfig.debug
+@@ -2487,6 +2487,7 @@ config TEST_KMOD
+       depends on m
+       depends on NETDEVICES && NET_CORE && INET # for TUN
+       depends on BLOCK
++      depends on PAGE_SIZE_LESS_THAN_256KB # for BTRFS
+       select TEST_LKM
+       select XFS_FS
+       select TUN
diff --git a/queue-5.16/media-correct-media_test_support-help-text.patch b/queue-5.16/media-correct-media_test_support-help-text.patch
new file mode 100644 (file)
index 0000000..8fc7888
--- /dev/null
@@ -0,0 +1,37 @@
+From 09f4d1513267d0ab712f5d29e7bd136535748709 Mon Sep 17 00:00:00 2001
+From: Randy Dunlap <rdunlap@infradead.org>
+Date: Sun, 7 Nov 2021 18:19:23 +0000
+Subject: media: correct MEDIA_TEST_SUPPORT help text
+
+From: Randy Dunlap <rdunlap@infradead.org>
+
+commit 09f4d1513267d0ab712f5d29e7bd136535748709 upstream.
+
+Fix grammar/wording in the help text for MEDIA_TEST_SUPPORT.
+
+Fixes: 4b32216adb01 ("media: split test drivers from platform directory")
+Signed-off-by: Randy Dunlap <rdunlap@infradead.org>
+Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
+Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/media/Kconfig |    8 ++++----
+ 1 file changed, 4 insertions(+), 4 deletions(-)
+
+--- a/drivers/media/Kconfig
++++ b/drivers/media/Kconfig
+@@ -141,10 +141,10 @@ config MEDIA_TEST_SUPPORT
+       prompt "Test drivers" if MEDIA_SUPPORT_FILTER
+       default y if !MEDIA_SUPPORT_FILTER
+       help
+-        Those drivers should not be used on production Kernels, but
+-        can be useful on debug ones. It enables several dummy drivers
+-        that simulate a real hardware. Very useful to test userspace
+-        applications and to validate if the subsystem core is doesn't
++        These drivers should not be used on production kernels, but
++        can be useful on debug ones. This option enables several dummy drivers
++        that simulate real hardware. Very useful to test userspace
++        applications and to validate if the subsystem core doesn't
+         have regressions.
+         Say Y if you want to use some virtual test driver.
diff --git a/queue-5.16/media-rcar-csi2-optimize-the-selection-phtw-register.patch b/queue-5.16/media-rcar-csi2-optimize-the-selection-phtw-register.patch
new file mode 100644 (file)
index 0000000..7cf2eca
--- /dev/null
@@ -0,0 +1,53 @@
+From 549cc89cd09a85aaa16dc07ef3db811d5cf9bcb1 Mon Sep 17 00:00:00 2001
+From: Suresh Udipi <sudipi@jp.adit-jv.com>
+Date: Fri, 13 Aug 2021 17:07:56 +0200
+Subject: media: rcar-csi2: Optimize the selection PHTW register
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+From: Suresh Udipi <sudipi@jp.adit-jv.com>
+
+commit 549cc89cd09a85aaa16dc07ef3db811d5cf9bcb1 upstream.
+
+PHTW register is selected based on default bit rate from Table[1].
+for the bit rates less than or equal to 250. Currently first
+value of default bit rate which is greater than or equal to
+the caculated mbps is selected. This selection can be further
+improved by selecting the default bit rate which is nearest to
+the calculated value.
+
+[1] specs r19uh0105ej0200-r-car-3rd-generation.pdf [Table 25.12]
+
+Fixes: 769afd212b16 ("media: rcar-csi2: add Renesas R-Car MIPI CSI-2 receiver driver")
+Signed-off-by: Suresh Udipi <sudipi@jp.adit-jv.com>
+Signed-off-by: Michael Rodin <mrodin@de.adit-jv.com>
+Reviewed-by: Niklas Söderlund <niklas.soderlund+renesas@ragnatech.se>
+Signed-off-by: Hans Verkuil <hverkuil-cisco@xs4all.nl>
+Signed-off-by: Mauro Carvalho Chehab <mchehab+huawei@kernel.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/media/platform/rcar-vin/rcar-csi2.c |    9 ++++++++-
+ 1 file changed, 8 insertions(+), 1 deletion(-)
+
+--- a/drivers/media/platform/rcar-vin/rcar-csi2.c
++++ b/drivers/media/platform/rcar-vin/rcar-csi2.c
+@@ -1104,10 +1104,17 @@ static int rcsi2_phtw_write_mbps(struct
+                                const struct rcsi2_mbps_reg *values, u16 code)
+ {
+       const struct rcsi2_mbps_reg *value;
++      const struct rcsi2_mbps_reg *prev_value = NULL;
+-      for (value = values; value->mbps; value++)
++      for (value = values; value->mbps; value++) {
+               if (value->mbps >= mbps)
+                       break;
++              prev_value = value;
++      }
++
++      if (prev_value &&
++          ((mbps - prev_value->mbps) <= (value->mbps - mbps)))
++              value = prev_value;
+       if (!value->mbps) {
+               dev_err(priv->dev, "Unsupported PHY speed (%u Mbps)", mbps);
diff --git a/queue-5.16/net-usb-correct-reset-handling-of-smsc95xx.patch b/queue-5.16/net-usb-correct-reset-handling-of-smsc95xx.patch
new file mode 100644 (file)
index 0000000..326b1b2
--- /dev/null
@@ -0,0 +1,40 @@
+From 0bf3885324a8599e3af4c7379b8d4f621c9bbffa Mon Sep 17 00:00:00 2001
+From: Markus Reichl <m.reichl@fivetechno.de>
+Date: Thu, 13 Jan 2022 21:01:11 +0100
+Subject: net: usb: Correct reset handling of smsc95xx
+
+From: Markus Reichl <m.reichl@fivetechno.de>
+
+commit 0bf3885324a8599e3af4c7379b8d4f621c9bbffa upstream.
+
+On boards with LAN9514 and no preconfigured MAC address we don't get an
+ip address from DHCP after commit a049a30fc27c ("net: usb: Correct PHY handling
+of smsc95xx") anymore. Adding an explicit reset before starting the phy
+fixes the issue.
+
+[1]
+https://lore.kernel.org/netdev/199eebbd6b97f52b9119c9fa4fd8504f8a34de18.camel@collabora.com/
+
+From: Gabriel Hojda <ghojda@yo2urs.ro>
+Fixes: a049a30fc27c ("net: usb: Correct PHY handling of smsc95xx")
+Signed-off-by: Gabriel Hojda <ghojda@yo2urs.ro>
+Signed-off-by: Markus Reichl <m.reichl@fivetechno.de>
+Tested-by: Alexander Stein <alexander.stein@ew.tq-group.com>
+Signed-off-by: David S. Miller <davem@davemloft.net>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/net/usb/smsc95xx.c |    3 ++-
+ 1 file changed, 2 insertions(+), 1 deletion(-)
+
+--- a/drivers/net/usb/smsc95xx.c
++++ b/drivers/net/usb/smsc95xx.c
+@@ -1962,7 +1962,8 @@ static const struct driver_info smsc95xx
+       .bind           = smsc95xx_bind,
+       .unbind         = smsc95xx_unbind,
+       .link_reset     = smsc95xx_link_reset,
+-      .reset          = smsc95xx_start_phy,
++      .reset          = smsc95xx_reset,
++      .check_connect  = smsc95xx_start_phy,
+       .stop           = smsc95xx_stop,
+       .rx_fixup       = smsc95xx_rx_fixup,
+       .tx_fixup       = smsc95xx_tx_fixup,
diff --git a/queue-5.16/rdma-hns-modify-the-mapping-attribute-of-doorbell-to-device.patch b/queue-5.16/rdma-hns-modify-the-mapping-attribute-of-doorbell-to-device.patch
new file mode 100644 (file)
index 0000000..6c3d01a
--- /dev/null
@@ -0,0 +1,33 @@
+From 39d5534b1302189c809e90641ffae8cbdc42a8fc Mon Sep 17 00:00:00 2001
+From: Yixing Liu <liuyixing1@huawei.com>
+Date: Mon, 6 Dec 2021 21:36:52 +0800
+Subject: RDMA/hns: Modify the mapping attribute of doorbell to device
+
+From: Yixing Liu <liuyixing1@huawei.com>
+
+commit 39d5534b1302189c809e90641ffae8cbdc42a8fc upstream.
+
+It is more general for ARM device drivers to use the device attribute to
+map PCI BAR spaces.
+
+Fixes: 9a4435375cd1 ("IB/hns: Add driver files for hns RoCE driver")
+Link: https://lore.kernel.org/r/20211206133652.27476-1-liangwenpeng@huawei.com
+Signed-off-by: Yixing Liu <liuyixing1@huawei.com>
+Signed-off-by: Wenpeng Liang <liangwenpeng@huawei.com>
+Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/infiniband/hw/hns/hns_roce_main.c |    2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/drivers/infiniband/hw/hns/hns_roce_main.c
++++ b/drivers/infiniband/hw/hns/hns_roce_main.c
+@@ -442,7 +442,7 @@ static int hns_roce_mmap(struct ib_ucont
+       prot = vma->vm_page_prot;
+       if (entry->mmap_type != HNS_ROCE_MMAP_TYPE_TPTR)
+-              prot = pgprot_noncached(prot);
++              prot = pgprot_device(prot);
+       ret = rdma_user_mmap_io(uctx, vma, pfn, rdma_entry->npages * PAGE_SIZE,
+                               prot, rdma_entry);
diff --git a/queue-5.16/rdma-rxe-fix-a-typo-in-opcode-name.patch b/queue-5.16/rdma-rxe-fix-a-typo-in-opcode-name.patch
new file mode 100644 (file)
index 0000000..7e93562
--- /dev/null
@@ -0,0 +1,34 @@
+From 8d1cfb884e881efd69a3be4ef10772c71cb22216 Mon Sep 17 00:00:00 2001
+From: Chengguang Xu <cgxu519@mykernel.net>
+Date: Sat, 18 Dec 2021 19:23:20 +0800
+Subject: RDMA/rxe: Fix a typo in opcode name
+
+From: Chengguang Xu <cgxu519@mykernel.net>
+
+commit 8d1cfb884e881efd69a3be4ef10772c71cb22216 upstream.
+
+There is a redundant ']' in the name of opcode IB_OPCODE_RC_SEND_MIDDLE,
+so just fix it.
+
+Fixes: 8700e3e7c485 ("Soft RoCE driver")
+Link: https://lore.kernel.org/r/20211218112320.3558770-1-cgxu519@mykernel.net
+Signed-off-by: Chengguang Xu <cgxu519@mykernel.net>
+Acked-by: Zhu Yanjun <zyjzyj2000@gmail.com>
+Reviewed-by: Bob Pearson <rpearsonhpe@gmail.com>
+Signed-off-by: Jason Gunthorpe <jgg@nvidia.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/infiniband/sw/rxe/rxe_opcode.c |    2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/drivers/infiniband/sw/rxe/rxe_opcode.c
++++ b/drivers/infiniband/sw/rxe/rxe_opcode.c
+@@ -117,7 +117,7 @@ struct rxe_opcode_info rxe_opcode[RXE_NU
+               }
+       },
+       [IB_OPCODE_RC_SEND_MIDDLE]              = {
+-              .name   = "IB_OPCODE_RC_SEND_MIDDLE]",
++              .name   = "IB_OPCODE_RC_SEND_MIDDLE",
+               .mask   = RXE_PAYLOAD_MASK | RXE_REQ_MASK | RXE_SEND_MASK
+                               | RXE_MIDDLE_MASK,
+               .length = RXE_BTH_BYTES,
diff --git a/queue-5.16/revert-net-mlx5-add-retry-mechanism-to-the-command-entry-index-allocation.patch b/queue-5.16/revert-net-mlx5-add-retry-mechanism-to-the-command-entry-index-allocation.patch
new file mode 100644 (file)
index 0000000..d4211f4
--- /dev/null
@@ -0,0 +1,62 @@
+From 4f6626b0e140867fd6d5a2e9d4ceaef97f10f46a Mon Sep 17 00:00:00 2001
+From: Moshe Shemesh <moshe@nvidia.com>
+Date: Sun, 5 Dec 2021 11:20:59 +0200
+Subject: Revert "net/mlx5: Add retry mechanism to the command entry index allocation"
+
+From: Moshe Shemesh <moshe@nvidia.com>
+
+commit 4f6626b0e140867fd6d5a2e9d4ceaef97f10f46a upstream.
+
+This reverts commit 410bd754cd73c4a2ac3856d9a03d7b08f9c906bf.
+
+The reverted commit had added a retry mechanism to the command entry
+index allocation. The previous patch ensures that there is a free
+command entry index once the command work handler holds the command
+semaphore. Thus the retry mechanism is not needed.
+
+Fixes: 410bd754cd73 ("net/mlx5: Add retry mechanism to the command entry index allocation")
+Signed-off-by: Moshe Shemesh <moshe@nvidia.com>
+Reviewed-by: Eran Ben Elisha <eranbe@nvidia.com>
+Signed-off-by: Saeed Mahameed <saeedm@nvidia.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/net/ethernet/mellanox/mlx5/core/cmd.c |   21 +--------------------
+ 1 file changed, 1 insertion(+), 20 deletions(-)
+
+--- a/drivers/net/ethernet/mellanox/mlx5/core/cmd.c
++++ b/drivers/net/ethernet/mellanox/mlx5/core/cmd.c
+@@ -904,25 +904,6 @@ static bool opcode_allowed(struct mlx5_c
+       return cmd->allowed_opcode == opcode;
+ }
+-static int cmd_alloc_index_retry(struct mlx5_cmd *cmd)
+-{
+-      unsigned long alloc_end = jiffies + msecs_to_jiffies(1000);
+-      int idx;
+-
+-retry:
+-      idx = cmd_alloc_index(cmd);
+-      if (idx < 0 && time_before(jiffies, alloc_end)) {
+-              /* Index allocation can fail on heavy load of commands. This is a temporary
+-               * situation as the current command already holds the semaphore, meaning that
+-               * another command completion is being handled and it is expected to release
+-               * the entry index soon.
+-               */
+-              cpu_relax();
+-              goto retry;
+-      }
+-      return idx;
+-}
+-
+ bool mlx5_cmd_is_down(struct mlx5_core_dev *dev)
+ {
+       return pci_channel_offline(dev->pdev) ||
+@@ -950,7 +931,7 @@ static void cmd_work_handler(struct work
+       sem = ent->page_queue ? &cmd->pages_sem : &cmd->sem;
+       down(sem);
+       if (!ent->page_queue) {
+-              alloc_ret = cmd_alloc_index_retry(cmd);
++              alloc_ret = cmd_alloc_index(cmd);
+               if (alloc_ret < 0) {
+                       mlx5_core_err_rl(dev, "failed to allocate command entry\n");
+                       if (ent->callback) {
diff --git a/queue-5.16/scsi-core-show-scmd_last-in-text-form.patch b/queue-5.16/scsi-core-show-scmd_last-in-text-form.patch
new file mode 100644 (file)
index 0000000..f06ae76
--- /dev/null
@@ -0,0 +1,32 @@
+From 3369046e54ca8f82e0cb17740643da2d80d3cfa8 Mon Sep 17 00:00:00 2001
+From: Bart Van Assche <bvanassche@acm.org>
+Date: Mon, 29 Nov 2021 11:46:00 -0800
+Subject: scsi: core: Show SCMD_LAST in text form
+
+From: Bart Van Assche <bvanassche@acm.org>
+
+commit 3369046e54ca8f82e0cb17740643da2d80d3cfa8 upstream.
+
+The SCSI debugfs code supports showing information about pending commands,
+including translating SCSI command flags from numeric into text format.
+Also convert the SCMD_LAST flag from numeric into text form.
+
+Link: https://lore.kernel.org/r/20211129194609.3466071-4-bvanassche@acm.org
+Fixes: 8930a6c20791 ("scsi: core: add support for request batching")
+Signed-off-by: Bart Van Assche <bvanassche@acm.org>
+Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/scsi/scsi_debugfs.c |    1 +
+ 1 file changed, 1 insertion(+)
+
+--- a/drivers/scsi/scsi_debugfs.c
++++ b/drivers/scsi/scsi_debugfs.c
+@@ -9,6 +9,7 @@
+ static const char *const scsi_cmd_flags[] = {
+       SCSI_CMD_FLAG_NAME(TAGGED),
+       SCSI_CMD_FLAG_NAME(INITIALIZED),
++      SCSI_CMD_FLAG_NAME(LAST),
+ };
+ #undef SCSI_CMD_FLAG_NAME
diff --git a/queue-5.16/scsi-ufs-ufs-mediatek-fix-error-checking-in-ufs_mtk_init_va09_pwr_ctrl.patch b/queue-5.16/scsi-ufs-ufs-mediatek-fix-error-checking-in-ufs_mtk_init_va09_pwr_ctrl.patch
new file mode 100644 (file)
index 0000000..6e546f5
--- /dev/null
@@ -0,0 +1,32 @@
+From 3ba880a12df5aa4488c18281701b5b1bc3d4531a Mon Sep 17 00:00:00 2001
+From: Miaoqian Lin <linmq006@gmail.com>
+Date: Wed, 22 Dec 2021 07:09:30 +0000
+Subject: scsi: ufs: ufs-mediatek: Fix error checking in ufs_mtk_init_va09_pwr_ctrl()
+
+From: Miaoqian Lin <linmq006@gmail.com>
+
+commit 3ba880a12df5aa4488c18281701b5b1bc3d4531a upstream.
+
+The function regulator_get() returns an error pointer. Use IS_ERR() to
+validate the return value.
+
+Link: https://lore.kernel.org/r/20211222070930.9449-1-linmq006@gmail.com
+Fixes: cf137b3ea49a ("scsi: ufs-mediatek: Support VA09 regulator operations")
+Signed-off-by: Miaoqian Lin <linmq006@gmail.com>
+Signed-off-by: Martin K. Petersen <martin.petersen@oracle.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/scsi/ufs/ufs-mediatek.c |    2 +-
+ 1 file changed, 1 insertion(+), 1 deletion(-)
+
+--- a/drivers/scsi/ufs/ufs-mediatek.c
++++ b/drivers/scsi/ufs/ufs-mediatek.c
+@@ -557,7 +557,7 @@ static void ufs_mtk_init_va09_pwr_ctrl(s
+       struct ufs_mtk_host *host = ufshcd_get_variant(hba);
+       host->reg_va09 = regulator_get(hba->dev, "va09");
+-      if (!host->reg_va09)
++      if (IS_ERR(host->reg_va09))
+               dev_info(hba->dev, "failed to get va09");
+       else
+               host->caps |= UFS_MTK_CAP_VA09_PWR_CTRL;
index 98f05df29c4f80994a8c11febcfa721a15f2e10b..7d08a22c0dc1e30e082aa851c73b069f19a52031 100644 (file)
@@ -902,4 +902,28 @@ ext4-don-t-use-the-orphan-list-when-migrating-an-inode.patch
 revert-drm-amdgpu-don-t-inherit-gem-object-vmas-in-child-process.patch
 drm-radeon-fix-error-handling-in-radeon_driver_open_kms.patch
 drm-amdgpu-display-only-set-vblank_disable_immediate-when-psr-is-not-enabled.patch
+firmware-update-kconfig-help-text-for-google-firmware.patch
+can-mcp251xfd-mcp251xfd_tef_obj_read-fix-typo-in-error-message.patch
+media-rcar-csi2-optimize-the-selection-phtw-register.patch
+drm-vc4-hdmi-make-sure-the-device-is-powered-with-cec.patch
+lib-kconfig.debug-make-test_kmod-depend-on-page_size_less_than_256kb.patch
+media-correct-media_test_support-help-text.patch
+documentation-coresight-fix-documentation-issue.patch
+documentation-dmaengine-correctly-describe-dmatest-with-channel-unset.patch
+documentation-acpi-fix-data-node-reference-documentation.patch
+documentation-arch-remove-leftovers-from-raw-device.patch
+documentation-arch-remove-leftovers-from-cifs_weak_pw_hash.patch
+documentation-refer-to-config-randomize_base-for-kernel-address-space-randomization.patch
+documentation-fix-firewire.rst-abi-file-path-error.patch
+bluetooth-btusb-return-error-code-when-getting-patch-status-failed.patch
+net-usb-correct-reset-handling-of-smsc95xx.patch
+bluetooth-hci_sync-fix-not-setting-adv-set-duration.patch
+scsi-core-show-scmd_last-in-text-form.patch
 of-base-improve-argument-length-mismatch-error.patch
+scsi-ufs-ufs-mediatek-fix-error-checking-in-ufs_mtk_init_va09_pwr_ctrl.patch
+dmaengine-uniphier-xdmac-fix-type-of-address-variables.patch
+dmaengine-idxd-fix-wq-settings-post-wq-disable.patch
+rdma-hns-modify-the-mapping-attribute-of-doorbell-to-device.patch
+rdma-rxe-fix-a-typo-in-opcode-name.patch
+dmaengine-stm32-mdma-fix-stm32_mdma_ctbr_tsel_mask.patch
+revert-net-mlx5-add-retry-mechanism-to-the-command-entry-index-allocation.patch