Morten Priess 8682e47eb0 Bluetooth: controller: Prevent incorrect lazy_current increment ... Prevent redundant collision resolves and potential incorrect and harmful increment of lazy_current. During collision scenarios with high CPU load, the ticker_worker may be called a second time before the ticker_job gets to run. This will cause ticker operations on the previosly expired node (expected), and in some cases increment lazy_current, even though the node was not sceduled to execute via the req/ack mechanism. By moving the request check before collision resolve, CPU time is saved, and lazy_current will not incorrectly be incremented if node is in collision. The problem may be seen as a connection suddenly not receiving packets, or MIC error on master, because the event counter goes out of sync. Signed-off-by: Morten Priess <mtpr@oticon.com>		2020-09-04 14:14:23 +02:00
..
ticker.c	Bluetooth: controller: Prevent incorrect lazy_current increment	2020-09-04 14:14:23 +02:00
ticker.h	zephyr: replace zephyr integer types with C99 types	2020-06-08 08:23:57 -05:00