From: "Sören Brinkmann" <soren.brinkmann@xilinx.com>
To: "Bryan Wu" <cooloney@gmail.com>,
"Richard Purdie" <rpurdie@rpsys.net>,
"Andreas Färber" <afaerber@suse.de>
Cc: linux-leds@vger.kernel.org, linux-kernel@vger.kernel.org,
Michal Simek <michal.simek@xilinx.com>
Subject: Re: [PATCH] leds: leds-gpio: Pass on error codes unmodified
Date: Sun, 1 Feb 2015 08:59:54 -0800 [thread overview]
Message-ID: <20150201165954.GX13057@xsjandreislx> (raw)
In-Reply-To: <1422760500-21793-1-git-send-email-soren.brinkmann@xilinx.com>
+ Andreas who actually reported this issue and also tested the patch.
On Sat, 2015-01-31 at 07:15PM -0800, Soren Brinkmann wrote:
> Instead of overriding error codes, pass them on unmodified. This
> way a EPROBE_DEFER is correctly passed to the driver core. This results
> in the LED driver correctly requesting probe deferral in cases the GPIO
> controller is not yet available.
>
> Signed-off-by: Soren Brinkmann <soren.brinkmann@xilinx.com>
Here should be a:
Reported-and-tested-by: Andreas Färber <afaerber@suse.de>
> ---
> Adding pinctrl on Zynq shuffled with probing order quite a bit and a lot
> of deferred probing is going on. With those changes I saw the LEDs
> failing to probe due to the GPIO controller deferring probe until the
> pincontroller is available. With this patch things work again:
>
> dmesg | grep -i led:
> of_get_named_gpiod_flags: parsed 'gpios' property of node '/leds/ds23[0]' - status (-517)
> platform leds: Driver leds-gpio requests probe deferral
> of_get_named_gpiod_flags: parsed 'gpios' property of node '/leds/ds23[0]' - status (0)
>
> Soren
> ---
> drivers/leds/leds-gpio.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/leds/leds-gpio.c b/drivers/leds/leds-gpio.c
> index 7ea1ea42c2d2..d26af0a79a90 100644
> --- a/drivers/leds/leds-gpio.c
> +++ b/drivers/leds/leds-gpio.c
> @@ -187,6 +187,7 @@ static struct gpio_leds_priv *gpio_leds_create(struct platform_device *pdev)
> led.gpiod = devm_get_gpiod_from_child(dev, child);
> if (IS_ERR(led.gpiod)) {
> fwnode_handle_put(child);
> + ret = PTR_ERR(led.gpiod);
> goto err;
> }
>
> @@ -229,7 +230,7 @@ static struct gpio_leds_priv *gpio_leds_create(struct platform_device *pdev)
> err:
> for (count = priv->num_leds - 2; count >= 0; count--)
> delete_gpio_led(&priv->leds[count]);
> - return ERR_PTR(-ENODEV);
> + return ERR_PTR(ret);
> }
>
> static const struct of_device_id of_gpio_leds_match[] = {
> --
> 2.2.2.1.g63c5777
>
next prev parent reply other threads:[~2015-02-01 17:07 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-01 3:15 [PATCH] leds: leds-gpio: Pass on error codes unmodified Soren Brinkmann
2015-02-01 16:59 ` Sören Brinkmann [this message]
2015-02-02 22:43 ` Bryan Wu
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=20150201165954.GX13057@xsjandreislx \
--to=soren.brinkmann@xilinx.com \
--cc=afaerber@suse.de \
--cc=cooloney@gmail.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=michal.simek@xilinx.com \
--cc=rpurdie@rpsys.net \
/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