public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Stephen Warren <swarren@wwwdotorg.org>
To: Mark Brown <broonie@opensource.wolfsonmicro.com>
Cc: Liam Girdwood <lrg@ti.com>,
	linux-kernel@vger.kernel.org, Stephen Warren <swarren@nvidia.com>
Subject: Re: [PATCH] regulator: fixed: support deferred probe for DT GPIOs
Date: Fri, 29 Jun 2012 09:30:51 -0600	[thread overview]
Message-ID: <4FEDCA2B.3060204@wwwdotorg.org> (raw)
In-Reply-To: <20120629012507.GL28922@opensource.wolfsonmicro.com>

On 06/28/2012 07:25 PM, Mark Brown wrote:
> On Thu, Jun 28, 2012 at 04:31:32PM -0600, Stephen Warren wrote:
> 
>> static struct fixed_voltage_config * 
>> -of_get_fixed_voltage_config(struct device *dev) 
>> +of_get_fixed_voltage_config(struct device *dev, bool
>> *defer_probe)
> 
> This is pretty contorted, we should just be able to pass the
> return value back more directly and of course ideally gpiolib would
> be doing the -EPROBE_DEFER for us anyway (I did send a patch for
> this, Grant didn't apply it due to a mostly unrelated issue in the
> current probe deferral implementation).  Or just defer if we don't
> get a config passed back or something.

I did consider making of_get_fixed_voltage_config() return a result
code, but then it needs some other way of returning the pointer, so
that seemed just as convoluted. Oh, I suppose it could use ERR_PTR()
to do that; that'd be nice and simple. Would that do?

Re: gpiolib doing it: How is that possible? of_get_named_gpio()
certainly can return -EPROBE_DEFER, but the caller would still need to
check it. The ideal case might be to just do:

ret = gpio_request(of_get_named_gpio(...));
if (ret)
    return ret;

and have gpio_request pass -EPROBE_DEFER from input to output.

i.e. only check the gpio_request() result code, not the
of_get_named_gpio() result code, and rely on gpio_request() to do
validation later.

But gpio_request takes an unsigned int, so the error code wouldn't
survive the translation:-(

  reply	other threads:[~2012-06-29 15:30 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2012-06-28 22:31 [PATCH] regulator: fixed: support deferred probe for DT GPIOs Stephen Warren
2012-06-29  1:25 ` Mark Brown
2012-06-29 15:30   ` Stephen Warren [this message]
2012-06-30 11: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=4FEDCA2B.3060204@wwwdotorg.org \
    --to=swarren@wwwdotorg.org \
    --cc=broonie@opensource.wolfsonmicro.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lrg@ti.com \
    --cc=swarren@nvidia.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