You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Moves host calls in discovery manager callbacks to be scheduled in
either a GATT DM-specific work queue or the system work queue depending
on a new Kconfig option `BT_GATT_DM_WORKQ_CHOICE`. This is done to
improve robustness and avoid possible concurrency issues.
Using the system work queue will not increase the memory footprint, but
is marked as experimental as the callbacks can potentially block, which
is not recommended in the syswq.
Signed-off-by: Håvard Reierstad <[email protected]>
Copy file name to clipboardExpand all lines: doc/nrf/releases_and_maturity/releases/release-notes-changelog.rst
+4Lines changed: 4 additions & 0 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -191,6 +191,10 @@ Bluetooth® LE
191
191
The SoftDevice Controller driver uses a devicetree node named ``bt_hci_sdc`` with a devicetree binding compatible with ``nordic,bt-hci-sdc``.
192
192
The Zephyr Bluetooth LE Controller uses a devicetree node named ``bt_hci_controller`` with a devicetree binding compatible with ``zephyr,bt-hci-ll-sw-split``.
193
193
Applications using the Zephyr Bluetooth Controller need to be updated (see the :ref:`migration guide <migration_2.8>`).
194
+
* Host calls in GATT Discovery Manager (DM) callbacks are now scheduled in a workqueue.
195
+
The :kconfig:option:`BT_GATT_DM_WORKQ_CHOICE` Kconfig option allows you to select the workqueue implementation.
196
+
You can select either a workqueue specific to GATT DM (default) or the system workqueue.
197
+
You can use the system workqueue if creating a new thread is not viable due to memory constraints, but it is not recommended to have potential blocking calls in the system workqueue.
0 commit comments