| 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
| ||
|
Date: Thu, 4 Sep 2014 19:15:13 +0200 From: Linus Walleij <linus.walleij@...aro.org> To: Dmitry Eremin-Solenikov <dmitry_eremin@...tor.com> Cc: Mark Brown <broonie@...nel.org>, Dirk Behme <dirk.behme@...bosch.com>, "linux-kernel@...r.kernel.org" <linux-kernel@...r.kernel.org>, Liam Girdwood <lgirdwood@...il.com>, Gokulkrishnan Nagarajan <Gokulkrishnan.Nagarajan@...bosch.com>, Grant Likely <grant.likely@...retlab.ca> Subject: Re: [PATCH] regulator: core: GPIO #0 is a valid GPIO On Mon, Sep 1, 2014 at 1:59 PM, Dmitry Eremin-Solenikov <dmitry_eremin@...tor.com> wrote: > Back in the time before DTS conversion started, the 0 was a correct GPIO > number. If somebody wanted to specify that no gpio is provided, he provided > -1 as an invalid number. I have the feeling that allowing users to use 0 as > 'no gpio' is a mistake. Or the API should be changed > to disallow GPIO 0 to exist at all. The API change that is going on is to switch platforms and subsystems to only deal with GPIO descriptors, which are pointer cookies such as is regulators and clocks. See Documentation/gpio/* Fixing the old global GPIO numberspace API is a waste of time IMO, it is just restricted by design and we want to get rid of it. Yours, Linus Walleij -- 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/
Powered by blists - more mailing lists