Lines Matching full:handler

40 .Nd "kernel interrupt handler and thread API"
50 .Fa "driver_intr_t handler"
89 invoked before and after the handler functions themselves.
91 An interrupt handler contains two distinct handler functions:
95 .Em handler .
101 .Em handler .
102 Both functions are optional; each interrupt handler may choose to register a
103 filter, a thread handler, or both.
104 Each interrupt handler also consists of a name,
109 .Em handler
111 .Ss Handler Constraints
122 .Em handler
126 Thus, threaded handler functions may obtain non-sleepable locks, as described
179 .Sx Handler Callbacks
208 function adds a new handler to an existing interrupt event specified by
212 argument specifies a name for this handler.
217 .Fa handler
218 argument provides the handler function to be executed from the
225 .Fa handler
229 argument specifies the priority of this handler,
232 It determines the order this handler is called relative to the other handlers
236 argument can be used to specify properties of this handler as defined in
243 handler.
264 function removes an interrupt handler from the interrupt event specified by
270 identifies the handler to remove.
284 flag specifies that this handler cannot share an interrupt thread with
285 another handler.
288 flag specifies that this handler is MP safe in that it does not need the
292 flag specifies that the interrupt source this handler is tied to is a good
294 from the handler's source triggers.
306 .Ss Handler Callbacks
326 This handler should acknowledge the interrupt, but it should also ensure that
359 swi_add(struct intr_event **eventp, const char *name, driver_intr_t handler,
381 	if (handler != NULL) {
382 		error = intr_event_add_handler(ie, name, NULL, handler, arg,
402 .Fa handler
412 already has at least one handler, or the interrupt thread
414 already has an exclusive handler.
441 has at least one handler which has not been removed with
459 handler.