mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Roger Quadros <quadros.roger@gmail.com>
To: pHilipp Zabel <philipp.zabel@gmail.com>
Cc: Mark Brown <broonie@opensource.wolfsonmicro.com>,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2] regulator: Add GPIO enable control to fixed voltage  regulator driver
Date: Fri, 31 Jul 2009 23:32:32 +0300	[thread overview]
Message-ID: <b90c0690907311332o958b7f4nd025aa7a8b273a88@mail.gmail.com> (raw)
In-Reply-To: <74d0deb30907311038w1b6cdd23iec3cfb2175fdedd0@mail.gmail.com>

On Fri, Jul 31, 2009 at 8:38 PM, pHilipp Zabel<philipp.zabel@gmail.com> wrote:
> On Fri, Jul 31, 2009 at 7:20 PM, Mark
> Brown<broonie@opensource.wolfsonmicro.com> wrote:
>> On Fri, Jul 31, 2009 at 07:19:49PM +0300, Roger Quadros wrote:
>>
>>
>>> +             ret = gpio_get_value(config->gpio);
>>
>> Can this fail?  It returns an int...
>
> No, gpio_get_value(_cansleep) return either zero or non-zero.
> I think some I2C gpio chips just return zero when the read fails.
> Also that's the return value if a gpiochip doesn't define the .get method.
>
> Only problem: drivers/gpio/gpiolib.c contains this piece of wisdom:
>
> /* Drivers MUST set GPIO direction before making get/set calls.  In
>  * some cases this is done in early boot, before IRQs are enabled.
>  [...]
>  */
>

Not having gpio_get_direction() in gpiolib is a limitation I think.
Can we just do the following for now ? (i.e. disable regulator by default)
Will there be any glitch? If yes, then how?

                ret = gpio_request(config->gpio, config->supply_name);
                ...

-               ret = gpio_get_value(config->gpio);
-               ret = gpio_direction_output(config->gpio, ret);
+               ret = gpio_direction_output(config->gpio, !config->enable_high);
                if (ret) {
                        dev_err(&pdev->dev, "Could not configure
enable GPIO %d direction: %d\n",
                                                        config->gpio, ret);
                        goto err_gpio;
                }

  reply	other threads:[~2009-07-31 20:32 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-07-31 16:19 Roger Quadros
2009-07-31 17:01 ` Felipe Balbi
2009-07-31 17:03 ` pHilipp Zabel
2009-07-31 17:20 ` Mark Brown
2009-07-31 17:38   ` pHilipp Zabel
2009-07-31 20:32     ` Roger Quadros [this message]
2009-07-31 21:44       ` Mark Brown
2009-08-01  5:57         ` Roger Quadros
2009-08-01  9:48           ` 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=b90c0690907311332o958b7f4nd025aa7a8b273a88@mail.gmail.com \
    --to=quadros.roger@gmail.com \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=philipp.zabel@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 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®