--- /dev/null
+From aeb078cebc40d421f61a8f07b0e7919aeb44d751 Mon Sep 17 00:00:00 2001
+From: Gregor Herburger <gregor.herburger@linutronix.de>
+Date: Thu, 26 Feb 2026 09:55:58 +0100
+Subject: arm64: dts: broadcom: bcm2712-d-rpi-5-b: add fixes for pinctrl/pinctrl_aon
+
+From: Gregor Herburger <gregor.herburger@linutronix.de>
+
+commit aeb078cebc40d421f61a8f07b0e7919aeb44d751 upstream.
+
+On the -d revision of the bcm2712 the pinctrl differs from the c0
+revision. The driver already supports both and distinguishes the two
+with the compatible string.
+
+Update the compatible string and reg length to reflect the different
+pinctrl.
+
+Signed-off-by: Gregor Herburger <gregor.herburger@linutronix.de>
+Link: https://lore.kernel.org/r/20260226-raspi-dts-updates-v1-5-60832d20ff04@linutronix.de
+Signed-off-by: Florian Fainelli <florian.fainelli@broadcom.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ arch/arm64/boot/dts/broadcom/bcm2712-d-rpi-5-b.dts | 10 ++++++++++
+ 1 file changed, 10 insertions(+)
+
+--- a/arch/arm64/boot/dts/broadcom/bcm2712-d-rpi-5-b.dts
++++ b/arch/arm64/boot/dts/broadcom/bcm2712-d-rpi-5-b.dts
+@@ -35,3 +35,13 @@
+ "PMIC_SCL", // AON_SGPIO_04
+ "PMIC_SDA"; // AON_SGPIO_05
+ };
++
++&pinctrl {
++ compatible = "brcm,bcm2712d0-pinctrl";
++ reg = <0x7d504100 0x20>;
++};
++
++&pinctrl_aon {
++ compatible = "brcm,bcm2712d0-aon-pinctrl";
++ reg = <0x7d510700 0x1c>;
++};
--- /dev/null
+From e8c597368b8500a824c639bfb5ed0044068c6870 Mon Sep 17 00:00:00 2001
+From: Krishna Chomal <krishna.chomal108@gmail.com>
+Date: Fri, 3 Apr 2026 13:31:55 +0530
+Subject: platform/x86: hp-wmi: Ignore backlight and FnLock events
+MIME-Version: 1.0
+Content-Type: text/plain; charset=UTF-8
+Content-Transfer-Encoding: 8bit
+
+From: Krishna Chomal <krishna.chomal108@gmail.com>
+
+commit e8c597368b8500a824c639bfb5ed0044068c6870 upstream.
+
+On HP OmniBook 7 the keyboard backlight and FnLock keys are handled
+directly by the firmware. However, they still trigger WMI events which
+results in "Unknown key code" warnings in dmesg.
+
+Add these key codes to the keymap with KE_IGNORE to silence the warnings
+since no software action is needed.
+
+Tested-by: Artem S. Tashkinov <aros@gmx.com>
+Reported-by: Artem S. Tashkinov <aros@gmx.com>
+Closes: https://bugzilla.kernel.org/show_bug.cgi?id=221181
+Signed-off-by: Krishna Chomal <krishna.chomal108@gmail.com>
+Link: https://patch.msgid.link/20260403080155.169653-1-krishna.chomal108@gmail.com
+Reviewed-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
+Signed-off-by: Ilpo Järvinen <ilpo.jarvinen@linux.intel.com>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ drivers/platform/x86/hp/hp-wmi.c | 5 +++++
+ 1 file changed, 5 insertions(+)
+
+--- a/drivers/platform/x86/hp/hp-wmi.c
++++ b/drivers/platform/x86/hp/hp-wmi.c
+@@ -399,6 +399,11 @@ static const struct key_entry hp_wmi_key
+ { KE_KEY, 0x21a9, { KEY_TOUCHPAD_OFF } },
+ { KE_KEY, 0x121a9, { KEY_TOUCHPAD_ON } },
+ { KE_KEY, 0x231b, { KEY_HELP } },
++ { KE_IGNORE, 0x21ab, }, /* FnLock on */
++ { KE_IGNORE, 0x121ab, }, /* FnLock off */
++ { KE_IGNORE, 0x30021aa, }, /* kbd backlight: level 2 -> off */
++ { KE_IGNORE, 0x33221aa, }, /* kbd backlight: off -> level 1 */
++ { KE_IGNORE, 0x36421aa, }, /* kbd backlight: level 1 -> level 2*/
+ { KE_END, 0 }
+ };
+
spi-aspeed-smc-fix-controller-deregistration.patch
drm-colorop-preserve-bypass-value-in-duplicate_state.patch
drm-atomic-add-affected-colorops-with-affected-planes.patch
+platform-x86-hp-wmi-ignore-backlight-and-fnlock-events.patch
+vsock-virtio-fix-msg_peek-ignoring-skb-offset-when-calculating-bytes-to-copy.patch
+arm64-dts-broadcom-bcm2712-d-rpi-5-b-add-fixes-for-pinctrl-pinctrl_aon.patch
--- /dev/null
+From 080f22f5d30233faf3d83be3098f35b8be9b7a00 Mon Sep 17 00:00:00 2001
+From: Luigi Leonardi <leonardi@redhat.com>
+Date: Wed, 15 Apr 2026 17:09:28 +0200
+Subject: vsock/virtio: fix MSG_PEEK ignoring skb offset when calculating bytes to copy
+
+From: Luigi Leonardi <leonardi@redhat.com>
+
+commit 080f22f5d30233faf3d83be3098f35b8be9b7a00 upstream.
+
+`virtio_transport_stream_do_peek()` does not account for the skb offset
+when computing the number of bytes to copy.
+
+This means that, after a partial recv() that advances the offset, a peek
+requesting more bytes than are available in the sk_buff causes
+`skb_copy_datagram_iter()` to go past the valid payload, resulting in
+a -EFAULT.
+
+The dequeue path already handles this correctly.
+Apply the same logic to the peek path.
+
+Fixes: 0df7cd3c13e4 ("vsock/virtio/vhost: read data from non-linear skb")
+Reviewed-by: Stefano Garzarella <sgarzare@redhat.com>
+Acked-by: Arseniy Krasnov <avkrasnov@salutedevices.com>
+Signed-off-by: Luigi Leonardi <leonardi@redhat.com>
+Link: https://patch.msgid.link/20260415-fix_peek-v4-1-8207e872759e@redhat.com
+Signed-off-by: Jakub Kicinski <kuba@kernel.org>
+Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
+---
+ net/vmw_vsock/virtio_transport_common.c | 5 ++---
+ 1 file changed, 2 insertions(+), 3 deletions(-)
+
+--- a/net/vmw_vsock/virtio_transport_common.c
++++ b/net/vmw_vsock/virtio_transport_common.c
+@@ -547,9 +547,8 @@ virtio_transport_stream_do_peek(struct v
+ skb_queue_walk(&vvs->rx_queue, skb) {
+ size_t bytes;
+
+- bytes = len - total;
+- if (bytes > skb->len)
+- bytes = skb->len;
++ bytes = min_t(size_t, len - total,
++ skb->len - VIRTIO_VSOCK_SKB_CB(skb)->offset);
+
+ spin_unlock_bh(&vvs->rx_lock);
+
projects / thirdparty / kernel / stable-queue.git / commitdiff
