Lines Matching full:sources

327 | doc      | Sources for BTstack documentation                    |
349 The run loop handles events from two different types of sources: data
350 sources and timers. Data sources represent communication interfaces like
354 of the data sources from interrupt context, or, execute a function from a different
357 Data sources and timers are represented by the *btstack_data_source_t* and
360 and data sources are kept in link lists. While the list of data sources
362 processing. Data sources need to be configured upon what event they are called back.
384 Depending on the platform, data sources are either polled (embedded, FreeRTOS), or the platform pro…
391 data sources as well as timers, e.g., for periodical sampling of sensors, or
401 If the run loop allows to trigger polling of data sources from interrupt context,
412 In the embedded run loop implementation, data sources are constantly polled and
413 the system is put to sleep if no IRQ happens during the poll of all data sources.
416 function of all registered data sources are called in a round robin way.
442 - all data sources are polled
452 The data sources are standard File Descriptors. In the run loop execute implementation,
484 The data sources are Event objects. In the run loop implementation WaitForMultipleObjects() call
493 …e peripherals to become ready. Therefore, BTstack does not provide direct support for data sources.