linux-kernel - Re: [patch/rfc 2.6.25-git] gpio: sysfs 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: Windows password security audit tool. GUI, reports in PDF.

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

Message-Id: <200804291804.19518.david-b@pacbell.net>
Date:	Tue, 29 Apr 2008 18:04:19 -0700
From:	David Brownell <david-b@...bell.net>
To:	Ben Nizette <bn@...sdigital.com>
Cc:	Trent Piepho <tpiepho@...escale.com>,
	lkml <linux-kernel@...r.kernel.org>,
	hartleys <hartleys@...ionengravers.com>,
	Mike Frysinger <vapier.adi@...il.com>,
	Bryan Wu <cooloney@...nel.org>
Subject: Re: [patch/rfc 2.6.25-git] gpio: sysfs interface

On Tuesday 29 April 2008, Ben Nizette wrote:
> I guess one last option (which is made hard by chip label non-uniqueness
> but I'll throw out anyway) would be
> 
> /sys/class/gpio
>         /chipa
>                 /gpio-n
>                         /value
>                         /direction
>                 /control
>         /chipb
>                 :
>                 :
> 

Or maybe:

  /sys/class/gpio
	/gpiochip-X			<-- range X..(X+ngpio)
		/device			<-- symlink, if it's known
		/ngpio
		/label
		/start			<-- maybe; start == X

with the gpio-N links probably going where you showed.  That'd be
best in terms of Purity Of Essence.

- Dave

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