[riot-notifications] [RIOT-OS/RIOT] cpu/stm32_common: prevent uart write stuck (#11107)

Vincent Dupont notifications at github.com
Tue Mar 5 16:44:39 CET 2019


@MrKevinWeiss @jcarrano I understand your point of view, but it seems to me there is a problem we cannot solve with the current API.

Indefinitely blocking a thread is not a solution IMO.

For instance, if your cpu is connected to a remote device with a UART, but if this device can be disconnected, you could leave your whole app stuck for no reason.
I guess a change in the periph uart API would be the easiest way of solving this (returning -ETIMEDOUT) but then the question of the timeout definition will be raised...

-- 
You are receiving this because you are subscribed to this thread.
Reply to this email directly or view it on GitHub:
https://github.com/RIOT-OS/RIOT/pull/11107#issuecomment-469729960
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.riot-os.org/pipermail/notifications/attachments/20190305/2ea79d58/attachment.html>


More information about the notifications mailing list