lkml.org 
[lkml]   [1997]   [Oct]   [31]   [last100]   RSS Feed
Views: [wrap][no wrap]   [headers]  [forward] 
 
Messages in this thread
/
Date
From
SubjectRe: irq2dev
C. Scott Ananian writes:
> Could someone summarize concisely for me the original purpose of irq2dev?

In the old days, irq2dev mapped an irq # to a device structure. At the
time, the interrupt service routines would tell you the irq, and then
you could get the device it pertained to from the irq2dev array. Now,
you can give a parameter to request_irq() that gets passed back to the
interrupt service routine. It should be pretty easy to get rid of: just
have calls to request_irq() to pass the device. If the interrupt service
routine gets the device from the irq2dev array, get it instead from the
argument that gets passed in. Remove all other references to irq2dev,
and you should be set.

- Gordon

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