From: Felipe Balbi <balbi@ti.com>
To: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
Cc: Felipe Balbi <balbi@ti.com>,
linux-kernel@vger.kernel.org,
Nicolas Ferre <nicolas.ferre@atmel.com>,
Grant Likely <grant.likely@secretlab.ca>
Subject: Re: [PATCH 1/2] gpiolib: introduce gpio_set_pullup
Date: Fri, 25 Nov 2011 16:59:06 +0200 [thread overview]
Message-ID: <20111125145905.GA17151@legolas.emea.dhcp.ti.com> (raw)
In-Reply-To: <20111125142305.GA15008@game.jcrosoft.org>
[-- Attachment #1: Type: text/plain, Size: 2813 bytes --]
On Fri, Nov 25, 2011 at 03:23:05PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> On 16:16 Fri 25 Nov , Felipe Balbi wrote:
> > Hi,
> >
> > On Fri, Nov 25, 2011 at 03:08:39PM +0100, Jean-Christophe PLAGNIOL-VILLARD wrote:
> > > Signed-off-by: Jean-Christophe PLAGNIOL-VILLARD <plagnioj@jcrosoft.com>
> > > Cc: Nicolas Ferre <nicolas.ferre@atmel.com>
> > > Cc: Grant Likely <grant.likely@secretlab.ca>
> > > ---
> > > drivers/gpio/gpiolib.c | 44 ++++++++++++++++++++++++++++++++++++++++++++
> > > include/asm-generic/gpio.h | 4 ++++
> > > include/linux/gpio.h | 5 +++++
> > > 3 files changed, 53 insertions(+), 0 deletions(-)
> > >
> > > diff --git a/drivers/gpio/gpiolib.c b/drivers/gpio/gpiolib.c
> > > index a971e3d..b7e5e75 100644
> > > --- a/drivers/gpio/gpiolib.c
> > > +++ b/drivers/gpio/gpiolib.c
> > > @@ -1519,6 +1519,50 @@ fail:
> > > }
> > > EXPORT_SYMBOL_GPL(gpio_set_debounce);
> > >
> > > +/**
> > > + * gpio_set_pullup - sets @pullup for a @gpio
> > > + * @gpio: the gpio to set pullup
> > > + * @pullup: pullup level
> > > + */
> > > +int gpio_set_pullup(unsigned gpio, unsigned pullup)
> > > +{
> > > + unsigned long flags;
> > > + struct gpio_chip *chip;
> > > + struct gpio_desc *desc = &gpio_desc[gpio];
> > > + int status = -EINVAL;
> > > +
> > > + spin_lock_irqsave(&gpio_lock, flags);
> > > +
> > > + if (!gpio_is_valid(gpio))
> > > + goto fail;
> > > + chip = desc->chip;
> > > + if (!chip || !chip->set_pullup)
> > > + goto fail;
> > > + gpio -= chip->base;
> > > + if (gpio >= chip->ngpio)
> > > + goto fail;
> > > + status = gpio_ensure_requested(desc, gpio);
> > > + if (status < 0)
> > > + goto fail;
> > > +
> > > + /* now we know the gpio is valid and chip won't vanish */
> > > +
> > > + spin_unlock_irqrestore(&gpio_lock, flags);
> > > +
> > > + might_sleep_if(chip->can_sleep);
> > > +
> > > + return chip->set_pullup(chip, gpio, pullup);
> > > +
> > > +fail:
> > > + spin_unlock_irqrestore(&gpio_lock, flags);
> > > + if (status)
> > > + pr_debug("%s: gpio-%d status %d\n",
> > > + __func__, gpio, status);
> > > +
> > > + return status;
> > > +}
> > > +EXPORT_SYMBOL_GPL(gpio_set_pullup);
> >
> > Maybe I'm missing something, but isn't it essentially what
> > gpio_set_value() does ? I mean, you set a pullup and you get '1' value
> > and set a pulldown and you get a '0' value ??
> >
> > Without a proper description of the necessity for this change, I can't
> > easily tell them apart :-(
> set_value is for output set_pullup is for input mode
>
> some IP allow you when you configure an gpio as input to enable the
> internal pullup so no need on the board to add an external pull up
I see, that would fit nicely on the changelog :-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 836 bytes --]
next prev parent reply other threads:[~2011-11-25 14:59 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-11-25 14:08 Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 14:08 ` [PATCH 2/2] gpiolib: introduce gpio_set_deglitch Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 14:14 ` Felipe Balbi
2011-11-25 15:00 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 14:16 ` [PATCH 1/2] gpiolib: introduce gpio_set_pullup Felipe Balbi
2011-11-25 14:23 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-25 14:59 ` Felipe Balbi [this message]
2011-11-25 15:34 ` Mark Brown
2011-11-27 9:35 ` Igor Grinberg
2011-11-29 2:37 ` Jean-Christophe PLAGNIOL-VILLARD
2011-11-29 16:51 ` Stephen Warren
2011-12-05 15:40 ` Jean-Christophe PLAGNIOL-VILLARD
2011-12-05 15:56 ` 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=20111125145905.GA17151@legolas.emea.dhcp.ti.com \
--to=balbi@ti.com \
--cc=grant.likely@secretlab.ca \
--cc=linux-kernel@vger.kernel.org \
--cc=nicolas.ferre@atmel.com \
--cc=plagnioj@jcrosoft.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 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®