linux-kernel - Ok to call disable_irq before request

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

Message-ID: <BANLkTikQk0OAS+41g=pk9BaqAWaVhQB9rg@mail.gmail.com>
Date:	Mon, 4 Apr 2011 19:53:50 -0500
From:	Timur Tabi <timur@...escale.com>
To:	linux-kernel@...r.kernel.org
Subject: Ok to call disable_irq before request_irq?

Is it okay to call disable_irq() before calling request_irq()?  My
device creates lots of spurious interrupts, and so I want the
interrupt enable only when I expect a real interrupt to occur.  It
seems to work, but I just want to make sure it's a proper technique.

-- 
Timur Tabi
Linux kernel developer at Freescale
--
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/