zephyr/subsys/bluetooth/controller
Vinayak Kariappa Chettimada 5f2099fb63 Bluetooth: controller: Workaround for Unknown Rsp during Enc Setup
Some old peer central controllers respond with Unknown
Response PDU to our local Slave Initiated Feature Request
after the peer initiated the Encryption Setup Procedure.

The peer has voilated the Bluetooth Specification by sending
the Unknown Response during the Encryption Setup Procedure,
but as a workaround to IOP with such controller our local
implementation is updated to not disconnect the connection
but accept the voilating Unknown Response PDU.

Relates to #12362.

Signed-off-by: Vinayak Kariappa Chettimada <vich@nordicsemi.no>
2019-03-01 14:23:50 +01:00
..
crypto Bluetooth: Switch from SYS_LOG to logger-based logging 2018-10-19 14:50:22 +02:00
hal Bluetooth: controller: Prepare to introduce LL split architecture 2019-01-07 13:42:01 +01:00
hci bluetooth: controller: Document RX path flow from mayfly to HCI 2019-02-18 15:13:45 -05:00
include Bluetooth: controller: Preliminary work in progress mesh ext. 2019-01-23 09:45:06 +01:00
ll_sw Bluetooth: controller: Workaround for Unknown Rsp during Enc Setup 2019-03-01 14:23:50 +01:00
ticker bluetooth: controller: Add a few ticker comments 2019-02-15 09:52:14 -05:00
util bluetooth: controller: Document more of memq, mfifo 2019-02-15 09:49:45 -05:00
CMakeLists.txt Bluetooth: controller: Remove redundant tmp role implementation 2019-02-05 15:00:08 +01:00
Kconfig doc: fix docs, include, and Kconfig misspellings 2019-02-28 09:32:12 +01:00