aboutsummaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorKiran K <kiran.k@intel.com>2021-11-23 10:29:10 +0530
committerJosh Boyer <jwboyer@kernel.org>2021-11-23 12:31:44 -0500
commit625e4549faf9a7c1ac7bf3670470e0b33d2b6bd9 (patch)
tree6e96111354c0790e4751972ab2b8e77eaac52e2c
parent0c353e11922827a1056f125b57d7f7394803b533 (diff)
downloadlinux-firmware-625e4549faf9a7c1ac7bf3670470e0b33d2b6bd9.tar.gz
linux-firmware: Update firmware file for Intel Bluetooth 9560
This patch updates the firmware file for Intel Bluetooth 9560 Also it is known as Intel JeffersonPeak (JfP2). FW Build: REL34345 Release Version: 22.100.0.2 Signed-off-by: Kiran K <kiran.k@intel.com> Signed-off-by: Josh Boyer <jwboyer@kernel.org>
-rw-r--r--WHENCE4
-rw-r--r--intel/ibt-0040-2120.sfibin734140 -> 727264 bytes
2 files changed, 2 insertions, 2 deletions
diff --git a/WHENCE b/WHENCE
index 53bfd6ea..9c250dd5 100644
--- a/WHENCE
+++ b/WHENCE
@@ -3860,9 +3860,9 @@ File:intel/ibt-1040-1020.ddc
Version: BT_SolarF_JfP1_REL31878
File:intel/ibt-0040-2120.sfi
-Version: BT_Solar_JfP2_REL31878
+Version: BT_Solar_JfP2_REL34345
File:intel/ibt-0040-2120.ddc
-Version: BT_Solar_JfP2_REL31878
+Version: BT_Solar_JfP2_REL34345
File:intel/ibt-1040-2120.sfi
Version: BT_SolarF_JfP2_REL31878
File:intel/ibt-1040-2120.ddc
diff --git a/intel/ibt-0040-2120.sfi b/intel/ibt-0040-2120.sfi
index b6488c29..a55fffa0 100644
--- a/intel/ibt-0040-2120.sfi
+++ b/intel/ibt-0040-2120.sfi
Binary files differ
alue='0' selected='selected'>unified
authorJohan Hovold <johan+linaro@kernel.org>2024-01-30 11:02:43 +0100
committerGreg Kroah-Hartman <gregkh@linuxfoundation.org>2024-02-16 19:14:30 +0100
commitef90508574d7af48420bdc5f7b9a4f1cdd26bc70 (patch)
treed73913b111806dc1a91d12cf1a3d41a76faf3921
parent01960f151efbd8bed0c8b7cbbad1e8ac33d5daeb (diff)
downloadlinux-ef90508574d7af48420bdc5f7b9a4f1cdd26bc70.tar.gz
PCI/ASPM: Fix deadlock when enabling ASPM
commit 1e560864159d002b453da42bd2c13a1805515a20 upstream. A last minute revert in 6.7-final introduced a potential deadlock when enabling ASPM during probe of Qualcomm PCIe controllers as reported by lockdep: ============================================ WARNING: possible recursive locking detected 6.7.0 #40 Not tainted -------------------------------------------- kworker/u16:5/90 is trying to acquire lock: ffffacfa78ced000 (pci_bus_sem){++++}-{3:3}, at: pcie_aspm_pm_state_change+0x58/0xdc but task is already holding lock: ffffacfa78ced000 (pci_bus_sem){++++}-{3:3}, at: pci_walk_bus+0x34/0xbc other info that might help us debug this: Possible unsafe locking scenario: CPU0 ---- lock(pci_bus_sem); lock(pci_bus_sem); *** DEADLOCK *** Call trace: print_deadlock_bug+0x25c/0x348 __lock_acquire+0x10a4/0x2064 lock_acquire+0x1e8/0x318 down_read+0x60/0x184 pcie_aspm_pm_state_change+0x58/0xdc pci_set_full_power_state+0xa8/0x114 pci_set_power_state+0xc4/0x120 qcom_pcie_enable_aspm+0x1c/0x3c [pcie_qcom] pci_walk_bus+0x64/0xbc qcom_pcie_host_post_init_2_7_0+0x28/0x34 [pcie_qcom] The deadlock can easily be reproduced on machines like the Lenovo ThinkPad X13s by adding a delay to increase the race window during asynchronous probe where another thread can take a write lock. Add a new pci_set_power_state_locked() and associated helper functions that can be called with the PCI bus semaphore held to avoid taking the read lock twice. Link: https://lore.kernel.org/r/ZZu0qx2cmn7IwTyQ@hovoldconsulting.com Link: https://lore.kernel.org/r/20240130100243.11011-1-johan+linaro@kernel.org Fixes: f93e71aea6c6 ("Revert "PCI/ASPM: Remove pcie_aspm_pm_state_change()"") Signed-off-by: Johan Hovold <johan+linaro@kernel.org> Signed-off-by: Bjorn Helgaas <bhelgaas@google.com> Cc: <stable@vger.kernel.org> # 6.7 Signed-off-by: Greg Kroah-Hartman <gregkh@linuxfoundation.org>