From: Robert Schwebel <r.schwebel@pengutronix.de>
To: Lennart Sorensen <lsorense@csclub.uwaterloo.ca>
Cc: Jim Cromie <jim.cromie@gmail.com>,
Robert Schwebel <r.schwebel@pengutronix.de>,
Chris Boot <bootc@bootc.net>,
kernel list <linux-kernel@vger.kernel.org>
Subject: Re: [RFC] Proposal: common kernel-wide GPIO interface
Date: Thu, 3 Aug 2006 17:42:43 +0200 [thread overview]
Message-ID: <20060803154243.GH10495@pengutronix.de> (raw)
In-Reply-To: <20060803135558.GO13639@csclub.uwaterloo.ca>
On Thu, Aug 03, 2006 at 09:55:58AM -0400, Lennart Sorensen wrote:
> > I'll rephrase my Q here.
> >
> > /sys/class/gpio/gpio63/
> >
> > this suggests that either - only 1 GPIO device can register (bad)
>
> Unacceptably bad. I currently use anywhere from 2 to 4 different
> devices with GPIOs.
Sure, it would probably be nice to have GPIO devices in sysfs dirs of
their respective parent. The variant I've sent was just a quick-n-dirty
framework we hacked for a project.
Robert
--
Dipl.-Ing. Robert Schwebel | http://www.pengutronix.de
Pengutronix - Linux Solutions for Science and Industry
Handelsregister: Amtsgericht Hildesheim, HRA 2686
Hannoversche Str. 2, 31134 Hildesheim, Germany
Phone: +49-5121-206917-0 | Fax: +49-5121-206917-9
next prev parent reply other threads:[~2006-08-03 15:43 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-07-28 20:44 [RFC] Proposal: common kernel-wide GPIO interface Chris Boot
2006-07-29 19:41 ` Bill Davidsen
2006-07-30 13:08 ` Robert Schwebel
2006-07-30 22:02 ` Ben Dooks
2006-07-31 16:10 ` Chris Boot
2006-07-31 20:17 ` Robert Schwebel
2006-07-31 21:23 ` Chris Boot
2006-08-01 7:40 ` Juergen Beisert
2006-08-01 15:53 ` Jim Cromie
2006-08-01 21:25 ` Jim Cromie
2006-08-02 7:28 ` Robert Schwebel
2006-08-02 17:58 ` Lennart Sorensen
2006-08-02 20:48 ` Jim Cromie
2006-08-03 13:55 ` Lennart Sorensen
2006-08-03 15:42 ` Robert Schwebel [this message]
2006-08-08 23:01 ` [RFC - patch] add a gpio-sysfs interface - was: " Jim Cromie
2006-08-09 17:12 ` Jim Cromie
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060803154243.GH10495@pengutronix.de \
--to=r.schwebel@pengutronix.de \
--cc=bootc@bootc.net \
--cc=jim.cromie@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=lsorense@csclub.uwaterloo.ca \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.