aboutsummaryrefslogtreecommitdiffstats
path: root/net/bluetooth/hci_event.c
diff options
context:
space:
mode:
authorKiran K <[email protected]>2025-07-21 09:44:36 +0000
committerLuiz Augusto von Dentz <[email protected]>2025-07-23 14:34:14 +0000
commit69b3d3acf3dba21e2abad863c80c7114eb110b3d (patch)
treecc2c4b7ceebfb422646ecf0d15ea679c9ed7de76 /net/bluetooth/hci_event.c
parentBluetooth: hci_devcd_dump: fix out-of-bounds via dev_coredumpv (diff)
downloadkernel-69b3d3acf3dba21e2abad863c80c7114eb110b3d.tar.gz
kernel-69b3d3acf3dba21e2abad863c80c7114eb110b3d.zip
Bluetooth: btintel_pcie: Make driver wait for alive interrupt
The firmware raises an alive interrupt upon receiving the HCI_RESET or BTINTEL_HCI_OP_RESET (Intel reset - 0xfc01) command. This change fixes the driver to properly wait for the alive interrupt to avoid driver sending commands to firmware before it is ready to process. For details on the handshake between the driver and firmware, refer to commit 05c200c8f029 ("Bluetooth: btintel_pcie: Add handshake between driver and firmware"). As the driver needs to handle two interrupts for HCI_OP_RESET and BTINTEL_HCI_OP_RESET, the firmware ensures that the TX completion interrupt is always followed by the alive interrupt. Fixes: 05c200c8f029 ("Bluetooth: btintel_pcie: Add handshake between driver and firmware") Signed-off-by: Sai Teja Aluvala <[email protected]> Signed-off-by: Kiran K <[email protected]> Signed-off-by: Luiz Augusto von Dentz <[email protected]>
Diffstat (limited to 'net/bluetooth/hci_event.c')
0 files changed, 0 insertions, 0 deletions