disable_irq(9) [suse man page]

DISABLE_IRQ(9)							Hardware Interfaces						    DISABLE_IRQ(9)

NAME

       disable_irq - disable an irq and wait for completion

SYNOPSIS

       void disable_irq(unsigned int irq);

ARGUMENTS

       irq
	   Interrupt to disable

DESCRIPTION

       Disable the selected interrupt line. Enables and Disables are nested. This function waits for any pending IRQ handlers for this interrupt
       to complete before returning. If you use this function while holding a resource the IRQ handler may need you will deadlock.

       This function may be called - with care - from IRQ context.

COPYRIGHT

Kernel Hackers Manual 2.6.					     July 2010							    DISABLE_IRQ(9)

REQUEST_THREADED_IRQ(9) 				     Public Functions Provided					   REQUEST_THREADED_IRQ(9)

NAME

       request_threaded_irq - allocate an interrupt line

SYNOPSIS

       int request_threaded_irq(unsigned int irq, irq_handler_t handler, irq_handler_t thread_fn, unsigned long irqflags, const char * devname,
				void * dev_id);

ARGUMENTS

       irq
	   Interrupt line to allocate

       handler
	   Function to be called when the IRQ occurs. Primary handler for threaded interrupts If NULL and thread_fn != NULL the default primary
	   handler is installed

       thread_fn
	   Function called from the irq handler thread If NULL, no irq thread is created

       irqflags
	   Interrupt type flags

       devname
	   An ascii name for the claiming device

       dev_id
	   A cookie passed back to the handler function

DESCRIPTION

       This call allocates interrupt resources and enables the interrupt line and IRQ handling. From the point this call is made your handler
       function may be invoked. Since your handler function must clear any interrupt the board raises, you must take care both to initialise your
       hardware and to set up the interrupt handler in the right order.

       If you want to set up a threaded irq handler for your device then you need to supply handler and thread_fn.  handler is still called in
       hard interrupt context and has to check whether the interrupt originates from the device. If yes it needs to disable the interrupt on the
       device and return IRQ_WAKE_THREAD which will wake up the handler thread and run thread_fn. This split handler design is necessary to
       support shared interrupts.

       Dev_id must be globally unique. Normally the address of the device data structure is used as the cookie. Since the handler receives this
       value it makes sense to use it.

       If your interrupt is shared you must pass a non NULL dev_id as this is required when freeing the interrupt.

FLAGS

       IRQF_SHARED Interrupt is shared IRQF_TRIGGER_* Specify active edge(s) or level

AUTHORS

       Thomas Gleixner <tglx@linutronix.de>
	   Author.

       Ingo Molnar <mingo@elte.hu>
	   Author.

COPYRIGHT

Kernel Hackers Manual 3.10					     June 2014						   REQUEST_THREADED_IRQ(9)