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 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 [email protected]
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/

---

• References:
  • [RFC patch] firewire: add Kconfig help on building both stacks
    • From: Stefan Richter <[email protected]>
  • call request_irq before or after hardware initialization?
    • From: Li Juen Hwang <[email protected]>

• Prev by Date: Re: [patch 0/4] MAP_NOZERO v2 - VM_NOZERO/MAP_NOZERO early summer madness
• Next by Date: Re: 2.6.21-rt9 problem : xruns
• Previous by thread: call request_irq before or after hardware initialization?
• Next by thread: [PATCH] mtrr/cyrix: fix sections
• Index(es):
  • Date
  • Thread

[Index of Archives]     [Kernel Newbies]     [Netfilter]     [Bugtraq]     [Photo]     [Stuff]     [Gimp]     [Yosemite News]     [MIPS Linux]     [ARM Linux]     [Linux Security]     [Linux RAID]     [Video 4 Linux]     [Linux for the blind]     [Linux Resources]