All of lore.kernel.org
 help / color / mirror / Atom feed
From: David Brownell <david-b@pacbell.net>
To: Mike Frysinger <vapier.adi@gmail.com>
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 02:48:07 -0700	[thread overview]
Message-ID: <200906040248.07922.david-b@pacbell.net> (raw)
In-Reply-To: <8bd0f97a0906040220k6f56b944n733a2b3469faaccb@mail.gmail.com>

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?


  reply	other threads:[~2009-06-04  9:54 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-03  8:16 [PATCH] gpio sysfs: add a "toggle" value 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 [this message]
2009-06-04 10:06                   ` Mike Frysinger
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=200906040248.07922.david-b@pacbell.net \
    --to=david-b@pacbell.net \
    --cc=akpm@linux-foundation.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=vapier.adi@gmail.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 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.