linux-kernel - question on generic gpio interface

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: <38b2ab8a0704131351la5085vf0ab58e85cf49879@mail.gmail.com>
Date:	Fri, 13 Apr 2007 22:51:27 +0200
From:	"Francis Moreau" <francis.moro@...il.com>
To:	dbrownell@...rs.sourceforge.net
Cc:	linux-kernel@...r.kernel.org
Subject: question on generic gpio interface

Hi,

I'm trying to port my old gpio code to the generic one to see if it
can fit my needs.

The gpio controller is a home made one and has a really weird
interface. It has several registers to read the gpio status, to
configure gpio directions, or to configure if a gpio can trigger an
interrupt and on which event (level or edge). All gpios use the same
IRQ and a gpio controller register allows to read which gpio has
triggered the interrupt.

Now the question is how should irq_to_gpio()  work ? Is it supposed to
be called only when a gpio interrupt occure ?

Another question is how can I specify if a gpio interrupt trigger on
level or on edge ?

thanks
-- 
Francis
-
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/