[lkml]   [1999]   [Jul]   [11]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
Messages in this thread
SubjectRe: interrupt handling w/o handler?
Jes Sorensen wrote:
> >>>>> "Jeff" == Jeff Garzik <> writes:
> Jeff> Is there a function available to drivers that allows something
> Jeff> like: ... interruptible_sleep_on_irq (9); /* wait on IRQ 9 */
> You have to register a handler for thaat, otherwise how are you
> guaranteed that the interrupt is handled and the hardware doesn't keep
> reasserting the same interrupt over and over again.

I think Jeff might be looking for a function such as:

-- allocate unused irq(n), bind in generic_irqhandler(n)
-- save PID in wakeuptable(n)
-- unmask irq(n)
-- sleep until woken up by generic_irqhandler(n)
-- deallocate irq(n)
-- exit

-- permanently mask irq(n)
-- wakeup(wakeuptable(n))
-- exit

Those two functions could then be made available to user-level
either through /proc or a newsyscall, thereby permitting *user-level*
interrupt handling ("virtual device drivers" from userland).


To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to
Please read the FAQ at

 \ /
  Last update: 2005-03-22 13:52    [W:0.045 / U:1.500 seconds]
©2003-2018 Jasper Spaans|hosted at Digital Ocean and TransIP|Read the blog|Advertise on this site