All of lore.kernel.org
 help / color / mirror / Atom feed
From: Ben Nizette <bn@niasdigital.com>
To: H Hartley Sweeten <hartleys@visionengravers.com>
Cc: David Brownell <david-b@pacbell.net>,
	Linux Kernel <linux-kernel@vger.kernel.org>,
	Jaya Kumar <jayakumar.lkml@gmail.com>
Subject: RE: [PATCH] gpiolib: introduce for_each_gpio_in_chip macro
Date: Thu, 06 Aug 2009 13:31:20 +1000	[thread overview]
Message-ID: <1249529480.16688.13.camel@ben-desktop> (raw)
In-Reply-To: <BD79186B4FD85F4B8E60E381CAEE190901B7783E@mi8nycmail19.Mi8.com>

On Tue, 2009-08-04 at 20:48 -0400, H Hartley Sweeten wrote:

> For the record. The reason I sent this is I'm trying to work out an
> extension to gpiolib that adds gpio_port_* access to the API.  Most
> of the gpiolib drivers already the necessary logic since the raw I/O
> is performed on the entire 'chip'.  The API just needs the extensions
> added to request/free the port, set the direction and get/set the value.
> 
> Is this a worthwhile addition?

Plenty of people seem to think so.  Personally I haven't seen a great
use case except "'coz I can", but if you've got one I'd love to hear.

Have you seen http://lkml.org/lkml/2009/1/25/10 ?  Donno what ended up
happening to that patchset..

	--Ben.



  reply	other threads:[~2009-08-06  3:31 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 17:27 [PATCH] gpiolib: introduce for_each_gpio_in_chip macro H Hartley Sweeten
2009-08-04 21:14 ` David Brownell
2009-08-05  0:48   ` H Hartley Sweeten
2009-08-06  3:31     ` Ben Nizette [this message]
2009-09-19  0:03       ` Jaya Kumar
2009-09-19  0:42         ` H Hartley Sweeten
2009-09-19  4:40           ` Jaya Kumar

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=1249529480.16688.13.camel@ben-desktop \
    --to=bn@niasdigital.com \
    --cc=david-b@pacbell.net \
    --cc=hartleys@visionengravers.com \
    --cc=jayakumar.lkml@gmail.com \
    --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 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.