zephyr/subsys/bluetooth
Johan Hedberg 0a925bdf9c Bluetooth: L2CAP: Process fixed channels in the RX thread
Now that the TX path and TX context (bt_conn_tx) has been redesigned
to free the contexts always in the system workqueue, it means the
system workqueue is the only context where their allocation may also
fail. This is particularly problematic with us having all L2CAP
channels (fixed & CoC alike) deferred to the system workqueue. It is
especially bad for fixed channels where being able to send responses
for SM, L2CAP signaling and ATT is critical to avoid timeouts for the
connection.

This patch moves the processing of all fixed L2CAP channels back to
the RX thread, thereby making it possible (and safe) to block while
waiting for a TX context to become available.

Signed-off-by: Johan Hedberg <johan.hedberg@intel.com>
2019-11-27 17:44:59 +02:00
..
common Bluetooth: Fix BT log level config won't take effect 2019-11-26 09:11:06 +02:00
controller Bluetooth: controller: split: Fix aborting of connection req PDU 2019-11-22 08:40:41 +01:00
host Bluetooth: L2CAP: Process fixed channels in the RX thread 2019-11-27 17:44:59 +02:00
mesh Bluetooth: Mesh: Fixes wrong return value 2019-11-27 11:22:20 +02:00
services kconfig: Clean up header comments and make them consistent 2019-11-04 17:31:27 -05:00
shell Bluetooth: shell: Fix missing return statement for name command 2019-11-17 21:03:24 +02:00
CMakeLists.txt cmake: don't link interface libraries with zephyr_interface 2019-09-26 05:50:46 -07:00
Kconfig Bluetooth: hci_raw: Add support for specifying buffer headroom 2019-11-20 19:29:06 +01:00