Piotr Pryga b53657a058 Bluetooth: Controller: hci: Wrong opcode when handling CTE req failed ... HCI_LE_CTE_Request_Failed may be generated in case received LL_CTE_RSP PDU didn't contain CTE or if peer rejected the request. HCI function encode_data_ctrl responsible for dispatching received control PDUs should not expect a PDU with PDU_DATA_LLCTRL_TYPE_CTE_REQ opcode. It should never happen. The correct opcode here is PDU_DATA_LLCTRL_TYPE- _CTE_RSP. Result of this issue is an assert when LL_CTE_RSP PDU is received but it does not include CTE. The commit fixes the problem. Signed-off-by: Piotr Pryga <piotr.pryga@nordicsemi.no>		2022-04-13 13:40:59 -07:00
..
audio	Bluetooth: has: Satisfy profile security requirement	2022-04-11 10:23:13 +02:00
common	Bluetooth: Host: Add choice select whether BT RX	2022-04-11 10:58:09 +02:00
controller	Bluetooth: Controller: hci: Wrong opcode when handling CTE req failed	2022-04-13 13:40:59 -07:00
host	Bluetooth: Host: Fix assert in L2CAP ECRED connection response	2022-04-13 13:40:00 -07:00
mesh	Bluetooth: Mesh: Remove argc check in mesh shell commands	2022-04-11 10:16:28 +02:00
services	Bluetooth: Immediate Alert Service	2022-04-12 09:59:34 +02:00
shell	Bluetooth: host: Optimize L2CAP resource usage	2022-04-07 09:37:12 +02:00
CMakeLists.txt
Kconfig	Bluetooth: Increase supported maximum simultaneous connection to 250	2022-04-04 10:24:34 +02:00
Kconfig.adv	Bluetooth: Kconfig: Move BT_LIM_ADV_TIMEOUT to host config	2022-03-17 11:12:47 +01:00
Kconfig.iso	everywhere: fix typos	2022-03-18 13:24:08 -04:00