linux-kernel - Re: [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib

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-prev] [thread-next>] [day] [month] [year] [list]

Message-Id: <4083C8C3-920B-4CE1-B393-D8BA0E7BFB13@niasdigital.com>
Date:	Sat, 23 Apr 2011 18:35:34 +1000
From:	Ben Nizette <bn@...sdigital.com>
To:	Linus Walleij <linus.walleij@...aro.org>
Cc:	Stijn Devriendt <highguy@...il.com>,
	Grant Likely <grant.likely@...retlab.ca>,
	Lee Jones <lee.jones@...aro.org>, linux-kernel@...r.kernel.org,
	linux-arm-kernel@...ts.infradead.org
Subject: Re: [PATCH 1/2] gpio: add pin biasing and drive mode to gpiolib


On 22/04/2011, at 9:36 PM, Linus Walleij wrote:

> 2011/4/21 Stijn Devriendt <highguy@...il.com>:
> 
> 
>> I'd also like to add (if not already mentioned by others) that in
>> general drivers that use GPIOs are unaware of their physical
>> connection on the board. Having this information
>> in device-tree or platform-data equivalent solves this.
> 
> Yes, this has been mentioned a few times, and a few times I have
> replied that there is not one word in the patch set that says anything
> about whether drivers or board code or whatever shall make use of
> the mechanism, it's just an interface...
> 
> I don't understand why this keeps popping up, have I written
> *anything* unclear about this?

You haven't, no!  Just that the use case for gpiolib was always to expose
gpio functionality to drivers/ in a generic way.  The fact that it's
now been picked up extensively throughout arch/ is a (very) happy
side-effect.

	--Ben.

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