Lines Matching full:dedicated

38  * for still to be registered events are instead kept in the dedicated common
42  * and is served by its own dedicated notification chain; information contained
54  * pushes the event-data itself on a protocol-dedicated kfifo queue for further
57  * Each protocol has it own dedicated work_struct and worker which, once kicked
58  * by the ISR, takes care to empty its own dedicated queue, deliverying the
234  * @kfifo: A dedicated Kernel kfifo descriptor
238  * Each protocol has its own dedicated events_queue descriptor.
349  * @chain: The notification chain dedicated to this specific event tuple
415  * Read an event header from the protocol queue into the dedicated scratch
454  * Read an event payload from the protocol queue into the dedicated scratch
513  * @work: The work item to use, which is associated to a dedicated events_queue
524  * * a dedicated per-protocol kfifo queue is used: in this way an anomalous
528  *   + all protocols can process their dedicated queues concurrently
988  * Valid pending incomplete bindings will be periodically retried by a dedicated
1322  * by the tuple (proto_id, evt_id, src_id) on a dedicated notification chain