linux-gpio.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Andy Shevchenko <andriy.shevchenko@linux.intel.com>
To: Hans de Goede <hdegoede@redhat.com>,
	Dmitry Torokhov <dmitry.torokhov@gmail.com>,
	Linus Walleij <linus.walleij@linaro.org>
Cc: Alexandre Courbot <gnurou@gmail.com>,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	"Rafael J. Wysocki" <rafael.j.wysocki@intel.com>,
	linux-gpio@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] ACPI / gpio: do not fall back to parsing _CRS when we get a deferral
Date: Wed, 29 Mar 2017 19:42:26 +0300	[thread overview]
Message-ID: <1490805746.708.51.camel@linux.intel.com> (raw)
In-Reply-To: <8eb1f4c1-61b2-1670-9ee2-086e2ea15cda@redhat.com>

On Wed, 2017-03-29 at 18:33 +0200, Hans de Goede wrote:
> HI,
> 
> On 28-03-17 17:04, Andy Shevchenko wrote:
> > On Thu, 2017-03-23 at 13:21 -0700, Dmitry Torokhov wrote:
> > > If, while locating GPIOs by name, we get probe deferral, we should
> > > immediately report it to caller rather than trying to fall back to
> > > parsing
> > > unnamed GPIOs from _CRS block.
> > 
> > +Cc: Hans.
> > 
> > Hans, do have any objections on this? Would you ideally give your
> > Tested-by?
> 
> Looks good to me and also does not seem to break anything on my test
> devices, so:
> 
> Acked-and-Tested-by: Hans de Goede <hdegoede@redhat.com>

Thanks!

Linus, I'm fully satisfied :-)

> 
> Regards,
> 
> Hans
> 
> 
> > 
> > > 
> > > Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> > > ---
> > >  drivers/gpio/gpiolib-acpi.c | 4 +++-
> > >  1 file changed, 3 insertions(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/gpio/gpiolib-acpi.c b/drivers/gpio/gpiolib-
> > > acpi.c
> > > index a3faefa44f68..d3f9f028a37b 100644
> > > --- a/drivers/gpio/gpiolib-acpi.c
> > > +++ b/drivers/gpio/gpiolib-acpi.c
> > > @@ -572,8 +572,10 @@ struct gpio_desc *acpi_find_gpio(struct
> > > device
> > > *dev,
> > >  		}
> > > 
> > >  		desc = acpi_get_gpiod_by_index(adev, propname,
> > > idx,
> > > &info);
> > > -		if (!IS_ERR(desc) || (PTR_ERR(desc) ==
> > > -EPROBE_DEFER))
> > > +		if (!IS_ERR(desc))
> > >  			break;
> > > +		if (PTR_ERR(desc) == -EPROBE_DEFER)
> > > +			return ERR_CAST(desc);
> > >  	}
> > > 
> > >  	/* Then from plain _CRS GPIOs */
> > > --
> > > 2.12.1.500.gab5fba24ee-goog
> > > 
> > > 

-- 
Andy Shevchenko <andriy.shevchenko@linux.intel.com>
Intel Finland Oy

  reply	other threads:[~2017-03-29 16:47 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-03-23 20:21 [PATCH] ACPI / gpio: do not fall back to parsing _CRS when we get a deferral Dmitry Torokhov
2017-03-28 13:25 ` Linus Walleij
2017-03-28 13:32   ` Mika Westerberg
2017-03-28 15:03   ` Andy Shevchenko
2017-03-28 15:04 ` Andy Shevchenko
2017-03-29 16:33   ` Hans de Goede
2017-03-29 16:42     ` Andy Shevchenko [this message]
2017-03-30  9:08 ` Linus Walleij

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=1490805746.708.51.camel@linux.intel.com \
    --to=andriy.shevchenko@linux.intel.com \
    --cc=dmitry.torokhov@gmail.com \
    --cc=gnurou@gmail.com \
    --cc=hdegoede@redhat.com \
    --cc=linus.walleij@linaro.org \
    --cc=linux-gpio@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    --cc=rafael.j.wysocki@intel.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;
as well as URLs for NNTP newsgroup(s).