From: Mike Frysinger <vapier.adi@gmail.com>
To: David Brownell <david-b@pacbell.net>
Cc: Andrew Morton <akpm@linux-foundation.org>, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] gpio sysfs: add a "toggle" value
Date: Thu, 4 Jun 2009 06:06:48 -0400 [thread overview]
Message-ID: <8bd0f97a0906040306j4c06c4efhbfa5ab47de590527@mail.gmail.com> (raw)
In-Reply-To: <200906040248.07922.david-b@pacbell.net>
On Thu, Jun 4, 2009 at 05:48, David Brownell wrote:
> On Thursday 04 June 2009, Mike Frysinger wrote:
>> > I don't like the idea of embedding any kind of interpreter
>> > in the sysfs interface, but that's the direction you seem
>> > to be heading ...
>>
>> i dont view the userspace GPIO interface as a simple "i want to wiggle
>> pins for fun and testing". i see it as a dynamic method for building
>> userspace drivers for simple devices.
>
> I don't. I see it as an adjunct to real drivers. Or maybe
> we just differ on what "simple" means here.
>
>> as such, having a very simple
>> "command language" for optimizing the interaction provides a pretty
>> good trade off between kernel complexity and lowering overhead imo.
>
> If that's what you want, why don't you write a custom driver
> that provides the kind of command interpreter you want?
i had "simple-gpio" but it was rejected as it duplicated too much with
the gpio sysfs interface
does vectored writes (writve) work with sysfs ? if so, then that
should work for back-to-back commands rather than having sysfs do
stream parsing.
-mike
next prev parent reply other threads:[~2009-06-04 10:07 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-06-03 8:16 Mike Frysinger
2009-06-04 7:54 ` Andrew Morton
2009-06-04 8:16 ` Mike Frysinger
2009-06-04 8:27 ` David Brownell
2009-06-04 8:52 ` Mike Frysinger
2009-06-04 9:05 ` Andrew Morton
2009-06-04 9:06 ` David Brownell
2009-06-04 9:09 ` Mike Frysinger
2009-06-04 9:15 ` David Brownell
2009-06-04 9:20 ` Mike Frysinger
2009-06-04 9:48 ` David Brownell
2009-06-04 10:06 ` Mike Frysinger [this message]
2009-06-04 8:36 ` Andrew Morton
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=8bd0f97a0906040306j4c06c4efhbfa5ab47de590527@mail.gmail.com \
--to=vapier.adi@gmail.com \
--cc=akpm@linux-foundation.org \
--cc=david-b@pacbell.net \
--cc=linux-kernel@vger.kernel.org \
/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®