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: <200805171514.07619.david-b@pacbell.net>
Date:	Sat, 17 May 2008 15:14:06 -0700
From:	David Brownell <david-b@...bell.net>
To:	Pavel Machek <pavel@....cz>
Cc:	Andrew Morton <akpm@...ux-foundation.org>,
	lkml <linux-kernel@...r.kernel.org>,
	Trent Piepho <tpiepho@...escale.com>,
	hartleys <hartleys@...ionengravers.com>,
	Ben Nizette <bn@...sdigital.com>,
	Mike Frysinger <vapier.adi@...il.com>,
	Bryan Wu <cooloney@...nel.org>
Subject: Re: [patch/rfc 2.6.25-git] gpio: sysfs interface

On Friday 02 May 2008, Pavel Machek wrote:
> 
> > >   echo "export 23" > /sys/class/gpio/control
> > >     ... will gpio_request(23, "sysfs") and gpio_export(23); use
> > >     /sys/class/gpio/gpio-23/direction to configure it.
> > >   echo "unexport 23" > /sys/class/gpio/control
> > >     ... will gpio_free(23)
> > 
> > hm, does ths sysfs one-value-per-file rule apply to writes?
> 
> Having seen ibm acpi interface... yes, that rule should be aplied for
> writes, too.

The latest version of this patch, which I'll post soonish,
follows the suggestion to have one file for the "export"
operation and another for "unexport".


> What about mkdir gpio-N to export it?

Ugh.  That would create way more complication than I want
to see here.  I thought about that early on, and decided
that was Not The Way To Go.

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

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ