linux-kernel - Re: GPIO: Performance sensitive applications, gpiochip-level locking

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]

Message-ID: <20131004150910.GP27287@sirena.org.uk>
Date:	Fri, 4 Oct 2013 16:09:10 +0100
From:	Mark Brown <broonie@...nel.org>
To:	Darren Hart <dvhart@...ux.intel.com>
Cc:	LKML <linux-kernel@...r.kernel.org>,
	Grant Likely <grant.likely@...aro.org>,
	Linus Walleij <linus.walleij@...aro.org>
Subject: Re: GPIO: Performance sensitive applications, gpiochip-level locking

On Mon, Sep 30, 2013 at 10:29:26AM -0700, Darren Hart wrote:

> Is there a best practice for dealing with this kind of configuration?

> If not, would it make sense to add optional gpiochip-level lock/unlock
> and lockless direction and value operations to the gpiochip function
> block?

Another thing people keep suggesting for this is a block GPIO set
operation - something that will let you configure multiple GPIOs with a
single call.  That maps nicely onto hardware which has a single register
for multiple GPIOs but there's been abstraction problems implementing
it.

Download attachment "signature.asc" of type "application/pgp-signature" (837 bytes)