From: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
To: Roland Stigge <stigge@antcom.de>
Cc: linus.walleij@linaro.org, linux-kernel@vger.kernel.org,
w.sang@pengutronix.de, grant.likely@secretlab.ca,
linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH RFC 1/2] gpio: Add a block GPIO API to gpiolib
Date: Fri, 28 Sep 2012 12:28:22 +0200 [thread overview]
Message-ID: <20120928102822.GY17667@game.jcrosoft.org> (raw)
In-Reply-To: <20120928090848.GX17667@game.jcrosoft.org>
On 11:08 Fri 28 Sep , Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 10:51 Fri 28 Sep , Roland Stigge wrote:
> > Hi!
> >
> > On 09/28/2012 09:51 AM, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > >> Right - will add checking for the request state of the respective GPIOs.
> > >>
> > >> The list of GPIOs to handle is defined by the offset (specified GPIO)
> > >> and bitmapped list.
> > >>
> > >> If it looks more natural, I can change this to a list of ints specifying
> > >> GPIOs directly.
> > > you pass the correctly information to the gpiolib
> > >
> > > as if you do not request the gpio the gpiolib will auto request the gpios
> > > so you api will be
> > > int gpio_get_block(unsigned int *gpios, u8* values, size_t size);
> > >
> > > return an error
> > >
> > > int gpio_set_block(unsigned int *gpios, u8* set, size_t size);
> > >
> > > so you do not care about the banks you work on the gpiolib framework will call
> > > each gpio_chip seperatly. If the set_block get_block is not availlable the
> > > gpiolib could fallback to get/set
> > >
> > > inside of the gpiolib that you call each bank with a bitmapped list is correct
> > > but not in the public gpiolib API
> >
> > Good idea! Talking about the public API (your above gpio_set_block()):
> > *gpios is a list of GPIOs, but set is still bitmapped (mapped onto the
> > list specified in *gpios)? To prevent confusion about what the size
> > argument means (number of gpios in *gpios _or_ number of bytes in the
> > bitmap *set) - wouldn't it be clearer to have a "bool *set" and "bool
> > *values" list?
> public API list of gpio as example
>
> gpios = {1, 33, 34, 55};
> set = {1, 0, 0 ,1};
>
> gpio_set_blocks(gpios, set, 4);
>
> private you do just provide the array related to the gpio_chip
> lets assume 4 bank with 32 gpio each
>
> gpio0 = {1};
> set0 = {1};
>
> gpio1 = {33, 34};
here should be
pin0 = {1};
set0 = {1};
pin1 = {1, 2, 23};
set1 = {0, 0, 1};
set_blocks(gpio_chip0, pin0, set0, 1);
set_blocks(gpio_chip1, pin1, set1, 3);
You may need to add a prepare to do not do the conversion between array and
gpio_chip array as I guess you will work on gpio block with multiple time
acces
Best Regards,
J.
next prev parent reply other threads:[~2012-09-28 12:59 UTC|newest]
Thread overview: 29+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-09-27 21:22 Roland Stigge
2012-09-27 21:22 ` [PATCH RFC 2/2] gpio-max730x: Add block GPIO API Roland Stigge
2012-09-28 2:47 ` [PATCH RFC 1/2] gpio: Add a block GPIO API to gpiolib Jean-Christophe PLAGNIOL-VILLARD
2012-09-28 7:14 ` Roland Stigge
2012-09-28 7:51 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-28 8:51 ` Roland Stigge
2012-09-28 9:08 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-28 9:23 ` Roland Stigge
2012-09-28 10:28 ` Jean-Christophe PLAGNIOL-VILLARD [this message]
2012-09-28 11:32 ` Roland Stigge
2012-09-28 16:01 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-28 18:32 ` Roland Stigge
2012-09-29 19:57 ` Jean-Christophe PLAGNIOL-VILLARD
2012-09-30 10:34 ` Roland Stigge
2012-09-30 15:11 ` Stijn Devriendt
2012-09-28 9:14 ` Linus Walleij
2012-09-28 9:52 ` Roland Stigge
2012-09-28 11:34 ` Linus Walleij
2012-09-28 12:35 ` Roland Stigge
[not found] ` <CAOY=C6GG6jqqEAAGJjmDG-BFT2eq=9+ck+F_EOcthRgDCDv8=Q@mail.gmail.com>
2012-09-30 9:39 ` Stijn Devriendt
2012-09-30 10:50 ` Roland Stigge
2012-09-30 14:52 ` Stijn Devriendt
2012-09-30 15:09 ` Roland Stigge
2012-09-30 15:19 ` Stijn Devriendt
2012-09-30 15:46 ` Roland Stigge
2012-10-03 23:11 ` Linus Walleij
2012-10-03 23:07 ` Linus Walleij
2012-10-04 20:25 ` Roland Stigge
2012-10-03 19:08 ` Mark Brown
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=20120928102822.GY17667@game.jcrosoft.org \
--to=plagnioj@jcrosoft.com \
--cc=grant.likely@secretlab.ca \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=stigge@antcom.de \
--cc=w.sang@pengutronix.de \
/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
Powered by JetHome