linux-kernel - Re: 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 for Android: free password hash cracker in your pocket

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

Date:	Tue, 17 Apr 2007 09:04:30 +0200
From:	"Francis Moreau" <francis.moro@...il.com>
To:	"David Brownell" <david-b@...bell.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Re: question on generic gpio interface

On 4/16/07, David Brownell <david-b@...bell.net> wrote:
> No, all of those need to be done.  (Plus maybe a few more things,
> I wasn't trying to be exhaustive.)  That last point is what makes
> the other ones take effect ... without it, the top level IRQ will
> never get dispatched to the GPIO-specific IRQ.
>
> Look at the examples I referenced.
>

I took a deeper look at the examples you mentioned and I understand
what you mean now...

I'm going to implement this since it all makes sense to me now. I'll
give you any feedbacks and try to post questions related to gpio only
if any.

BTW, are there any plan to make gpio usable from userspace ? I don't
know if it makes sense but I saw some patches on LKML that did that.

Thanks again.
-- 
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/