Lines Matching refs:thread

54 Currently, the goals of thread optimization in the Bluetooth stack are:
59     methods to interact with it on main thread
61     alarm thread
63     stopped individually without terminating the main thread
70 **Main thread**
71 :   The main workhorse in the Bluetooth stack. The thread's execution context is
73     [`Modules`](#module). This thread can be divided further into smaller ones
78 **JNI thread**
79 :   In the native thread, we treat the Java layer as a separate application as
80     its threading module is completely different. Therefore, we put a thread
83 **HCI thread (or other HW I/O thread)**
84 :   This thread is responsible for deadling with hardware I/O and can be
85     potentially blocking. Hence it has its separate thread to avoid blocking the
86     main thread.
88 **Audio worker thread**
90     precision execution timing. Such worker has its separate thread to avoid
91     being affected by the main thread.
93 **Socket I/O thread**
96     interface. It has its sepearate thread due to potential I/O delay.
108     will return immediately. All queueing within a thread must be non-blocking,
113     will block, until other thread makes the queue to be writable/readable. It
115     thread.
147 provides a sequential execution context while hiding the concept of thread from
155 *   Separation from thread gives system deployer more freedom to tweak the
156     underlying thread allocation. For example, for real time OS without full
157     thread implementation, a `Handler` can be used to provide a near-thread
163 WARNING: Although multiple `Handler` could bind to the same thread, `Handler`
165 when the are on the same thread.
167 WARNING: Locking among `Handlers` that were bound to the same thread may result