linux-kernel - gpio_keys: request_irq with level triggered flags

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: <5d5443650901120338h5cfbb102k6459938d1a6f110@mail.gmail.com>
Date:	Mon, 12 Jan 2009 17:08:44 +0530
From:	Trilok Soni <soni.trilok@...il.com>
To:	dtor@...l.ru
Cc:	David Brownell <david-b@...bell.net>, linux-kernel@...r.kernel.org
Subject: gpio_keys: request_irq with level triggered flags

Hi Dmitry,

>From the gpio_keys.c, I can see that request_irq is assuming all the
gpio line interrupts to be edge triggered one, but what if we have
level triggered interrupts? Doesn't this flags need to come from
platform data hooks too? So, that we can specify either
(IRQF_TRIGGER_RISING |  IRQF_TRIGGER_FALLING ) or (IRQF_TRIGGER_HIGH |
IRQF_TRIGGER_LOW) based on the platform data?


-- 
---Trilok Soni
http://triloksoni.wordpress.com
http://www.linkedin.com/in/triloksoni
--
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/