public inbox for linux-arm-kernel@lists.infradead.org
 help / color / mirror / Atom feed
From: arnd@arndb.de (Arnd Bergmann)
To: linux-arm-kernel@lists.infradead.org
Subject: Location for a kind of GPIO bus driver
Date: Fri, 26 Jul 2013 18:18:58 +0200	[thread overview]
Message-ID: <201307261818.59002.arnd@arndb.de> (raw)
In-Reply-To: <20130726085623.GM9916@kw.sim.vm.gnt>

On Friday 26 July 2013, Simon Guinot wrote:
> On Thu, Jul 25, 2013 at 12:03:24PM -0400, Jason Cooper wrote:
> > On Thu, Jul 25, 2013 at 05:49:32PM +0200, Simon Guinot wrote:

> > > > I would try drivers/gpio.  If there are complaints, it should be trivial
> > > > to move it in a new version of the series.
> > > 
> > > Why not, as long it is clear that the resulting driver will not provide
> > > a GPIO chip but rather functions as a library.
> > 
> > right, but the end result of what the library would do is expose a
> > series of LEDs and PM 'virtual gpios'.  So, even though it's not a gpio
> > expander per-se, it's still filling that role.  Or am I still missing
> > something?
> 
> The library could expose a function allowing to set the address and data
> registers: gpio_ext_set_value(int addr, int value).
> 
> Actually, it is how it works inside leds-netxbig. Simply this function
> would be also accessible by other drivers.

With that prototype it still sounds like a regular gpiochip driver would
fit that role well, since the function you describe is just like
gpio_set_value().

Maybe you can post the driver to let others understand what you are
trying to do if it's not just a gpio expander.

	Arnd

  parent reply	other threads:[~2013-07-26 16:18 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2013-07-23 15:18 Location for a kind of GPIO bus driver Simon Guinot
2013-07-24 18:19 ` Jason Cooper
2013-07-25 15:49   ` Simon Guinot
2013-07-25 16:03     ` Jason Cooper
2013-07-26  8:56       ` Simon Guinot
2013-07-26 11:27         ` Jason Cooper
2013-07-26 16:18         ` Arnd Bergmann [this message]
2013-07-25 21:46 ` Linus Walleij
2013-07-25 22:16   ` Greg KH
2013-07-26 12:01     ` Jason Cooper

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=201307261818.59002.arnd@arndb.de \
    --to=arnd@arndb.de \
    --cc=linux-arm-kernel@lists.infradead.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