Nordic zephyr implementation of bt_gatt_notify() appears to block; then at some point later from system workqueue thread seems to unblock.
My code currently calls notify from a thread that is not allowed to block.
Mainline zephyr includes changes (CONFIG_BT_ATT_TX_COUNT) that allow notifications to be queued; ncs does not include these changes.
I suspect this issue has existed for a long time. See this old ticket....
bt_gatt_notify from thread
I could create a queue and farm my notifications out to another lower priority task; but would the underlying issue still be there if bluetooth subsystem does not flush out the notifications quickly? Is the mainline CONFIG_BT_ATT_TX_COUNT from mainline zephyr not necessary?
Do you have any suggestions?
Connect
