Lines Matching defs:handler
26 * holding a resource the IRQ handler may need you will deadlock.
57 * We made sure that no hardirq handler is running. Now verify
237 * instances of the IRQ handler have completed before returning.
265 * holding a resource the IRQ handler may need you will deadlock.
424 * the flow handler then zap the default. This
468 * Default primary interrupt handler for threaded interrupts. Is
469 * assigned as primary handler when request_threaded_irq is called
470 * with handler == NULL. Useful for oneshot interrupts.
478 * Primary handler for nested threaded interrupts. Should never be
483 WARN(1, "Primary handler called for nested irq %d\n", irq);
504 * handler finished. unmask if the interrupt has not been disabled and
517 * The thread is faster done than the hard interrupt handler
571 * Interrupt handler thread
639 * soon to be gone threaded handler.
673 * installing a new handler, but is this really a problem,
692 * Replace the primary handler which was provided from
696 new->handler = irq_nested_primary_handler;
700 * Create a handler thread when a thread function is supplied
797 /* hope the handler works with the actual trigger mode... */
806 /* Reset broken irq detection when installing new handler */
811 * Check whether we disabled the irq via the spurious handler
837 printk(KERN_ERR "IRQ handler type mismatch for IRQ %d\n", irq);
839 printk(KERN_ERR "current handler: %s\n", old_name);
919 /* If this was the last handler, shut down the IRQ line: */
945 * is so by doing an extra call to the handler ....
952 action->handler(irq, dev_id);
984 * Remove an interrupt handler. The handler is removed and if the
1009 * @handler: Function to be called when the IRQ occurs.
1010 * Primary handler for threaded interrupts
1012 * primary handler is installed
1013 * @thread_fn: Function called from the irq handler thread
1017 * @dev_id: A cookie passed back to the handler function
1021 * call is made your handler function may be invoked. Since
1022 * your handler function must clear any interrupt the board
1024 * and to set up the interrupt handler in the right order.
1026 * If you want to set up a threaded irq handler for your device
1027 * then you need to supply @handler and @thread_fn. @handler ist
1031 * IRQ_WAKE_THREAD which will wake up the handler thread and run
1032 * @thread_fn. This split handler design is necessary to support
1036 * device data structure is used as the cookie. Since the handler
1049 int request_threaded_irq(unsigned int irq, irq_handler_t handler,
1073 if (!handler) {
1076 handler = irq_default_primary_handler;
1083 action->handler = handler;
1109 handler(irq, dev_id);
1122 * @handler: Function to be called when the IRQ occurs.
1123 * Threaded handler for threaded interrupts.
1126 * @dev_id: A cookie passed back to the handler function
1136 int request_any_context_irq(unsigned int irq, irq_handler_t handler,
1146 ret = request_threaded_irq(irq, NULL, handler,
1151 ret = request_irq(irq, handler, flags, name, dev_id);