linux-kernel - 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] [thread-next>] [day] [month] [year] [list]

Date:	Fri, 29 Jun 2007 12:35:53 -0700
From:	Li Juen Hwang <lwen@...ex.com>
To:	linux1394-devel@...ts.sourceforge.net, linux-kernel@...r.kernel.org
Subject: 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@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/