linux-kernel - Re: [GIT PULL] GPIO changes for v3.6

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, 31 Jul 2012 14:35:28 +0100
From:	Mark Brown <broonie@...nsource.wolfsonmicro.com>
To:	NeilBrown <neilb@...e.de>
Cc:	Linus Walleij <linus.walleij@...aro.org>,
	linux-kernel@...r.kernel.org,
	Grant Likely <grant.likely@...retlab.ca>
Subject: Re: [GIT PULL] GPIO changes for v3.6

On Tue, Jul 31, 2012 at 02:47:24PM +1000, NeilBrown wrote:

> ... though it occurs to me that it is possible that the GPIO number might not
> be allocated until something else has been probed, so a -ve gpio number could
> mean "there is no such gpio" or it could mean "gpio has not been allocated
> yet".  I wonder if that should be allowed and where it should be handled.

If there's logic to do things like that I'd 

> I'd really like to see gpios be requested by name ... anyone know if there
> are any plans along that line?

I've not noticed anyone doing much substantial work on GPIO recently.
--
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/