Andrei Emeltchenko 712689c9a3 drivers/nble: Use semaphore to control notification rate ... At the moment firmware reads everything we send to it over UART and when an application tries to send too much notifications we are stuck. The proper approach would be forcing firmware to read from UART only when there is available memory. In this case we would block on UART FIFO and everything handles gracefully. This workaround mimics solution used by firmware project by allowing to send next notification only after previous was sent correctly. Change-Id: I56dd5abc4d13735d285415da04db75e7bb8bc459 Signed-off-by: Andrei Emeltchenko <andrei.emeltchenko@intel.com>		2016-07-22 19:03:43 +00:00
..
nble	drivers/nble: Use semaphore to control notification rate	2016-07-22 19:03:43 +00:00
Kconfig	Bluetooth: H5: Use delayed work API	2016-07-08 12:05:34 +00:00
Makefile	drivers/nble: Refactor PM code to make it reusable	2016-04-06 14:00:56 +03:00
h4.c	Bluetooth: Add priority buffer for handling critical HCI events	2016-06-29 14:51:51 +00:00
h5.c	Bluetooth: H5: Use delayed work API	2016-07-08 12:05:34 +00:00
nrf51_pm.c	Bluetooth: Fix draining nRF51 FIFO during init	2016-05-04 15:05:13 +03:00
nrf51_pm.h	Bluetooth: Fix draining nRF51 FIFO during init	2016-05-04 15:05:13 +03:00
util.h	Bluetooth: Make UART draining logic consistent across drivers	2016-05-04 13:37:44 +00:00