Re: call request_irq before or after hardware initialization?

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()

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.

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.

Re: call request_irq before or after hardware initialization?

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