From: Grant Likely <grant.likely@secretlab.ca>
To: Linus Walleij <linus.ml.walleij@gmail.com>
Cc: Stephen Warren <swarren@nvidia.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Barry Song <21cnbao@gmail.com>,
linux-kernel@vger.kernel.org, Joe Perches <joe@perches.com>,
Russell King <linux@arm.linux.org.uk>,
Linaro Dev <linaro-dev@lists.linaro.org>,
Lee Jones <lee.jones@linaro.org>,
David Brown <davidb@codeaurora.org>,
linux-arm-kernel@lists.infradead.org,
Stijn Devriendt <highguy@gmail.com>
Subject: Re: [PATCH] drivers: create a pin control subsystem v8
Date: Tue, 4 Oct 2011 14:35:20 -0600 [thread overview]
Message-ID: <20111004203520.GK2870@ponder.secretlab.ca> (raw)
In-Reply-To: <CAKnu2MpQ8Wvd4TF8Ge=o8ACyEoaEY8TcvOSdT1w6zfYiSKFUiw@mail.gmail.com>
On Sat, Oct 01, 2011 at 12:39:21PM +0200, Linus Walleij wrote:
> 2011/9/30 Grant Likely <grant.likely@secretlab.ca>:
>
> > I'm not convinced that the sysfs approach is
> > actually the right interface here (I'm certainly not a fan of the gpio
> > sysfs i/f), and I'd rather not be putting in unneeded stuff until the
> > userspace i/f is hammered out.
>
> Actually, thinking about it I cannot see what would be wrong
> with /dev/gpio0 & friends in the first place.
>
> Using sysfs as swiss army knife for custom I/O does not
> seem like it would be long-term viable so thanks for this
> observation, and I think we need /dev/gpio* put on some
> mental roadmap somewhere.
Agreed. I don't want to be in the situation we are now with GPIO,
where every time I look at the sysfs interface I shudder.
g.
next prev parent reply other threads:[~2011-10-04 20:40 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-09-28 12:03 Linus Walleij
2011-09-30 2:07 ` Grant Likely
2011-09-30 15:05 ` Linus Walleij
2011-09-30 17:07 ` Grant Likely
2011-09-30 17:20 ` Linus Walleij
2011-10-01 10:39 ` Linus Walleij
2011-10-04 20:35 ` Grant Likely [this message]
2011-10-22 17:44 ` Mike Frysinger
2011-10-24 7:26 ` Linus Walleij
2011-10-24 7:36 ` Grant Likely
2011-10-24 7:48 ` Linus Walleij
2011-10-24 9:20 ` Mike Frysinger
2011-10-24 12:28 ` Linus Walleij
2011-10-24 11:05 ` Grant Likely
2011-10-25 8:05 ` Tony Lindgren
2011-10-25 8:17 ` Grant Likely
2011-10-25 8:23 ` Mark Brown
2011-10-24 9:14 ` Mike Frysinger
2011-09-30 18:08 ` Stephen Warren
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=20111004203520.GK2870@ponder.secretlab.ca \
--to=grant.likely@secretlab.ca \
--cc=21cnbao@gmail.com \
--cc=davidb@codeaurora.org \
--cc=highguy@gmail.com \
--cc=joe@perches.com \
--cc=lee.jones@linaro.org \
--cc=linaro-dev@lists.linaro.org \
--cc=linus.ml.walleij@gmail.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@arm.linux.org.uk \
--cc=s.hauer@pengutronix.de \
--cc=swarren@nvidia.com \
/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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
all inboxes | Powered by JetHome®