linux-kernel - Re: call request_irq before or after hardware initialization?

lists.openwall.net		lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-Id: <1183148587.2642.5.camel@laptopd505.fenrus.org>
Date:	Fri, 29 Jun 2007 13:23:07 -0700
From:	Arjan van de Ven <arjan@...radead.org>
To:	Li Juen Hwang <lwen@...ex.com>
Cc:	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: 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 majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/