Mailing List Archive

call request_irq before or after hardware initialization?
Hi,

Most 1394 drivers on Linux, ohci1394 for instance, calls
request_irq() before
initializing/enabling hardware chip. I'd like to reverse the order
so that driver
can exit the kernel without calling free_irq() if hardware failed.
Is that ok?
will it cause side effect? Thanks.


Li-Juen

-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/
Re: call request_irq before or after hardware initialization? [ In reply to ]
On Fri, 2007-06-29 at 12:35 -0700, Li Juen Hwang wrote:
>
> Hi,
>
> Most 1394 drivers on Linux, ohci1394 for instance, calls
> request_irq() before
> initializing/enabling hardware chip. I'd like to reverse the order
> so that driver
> can exit the kernel without calling free_irq() if hardware failed.
> Is that ok?
> will it cause side effect? Thanks.

well you have to be able to handle interrupts the moment the hardware
will generate them... so the request_irq has to happen before that
point.


-
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
Please read the FAQ at http://www.tux.org/lkml/