linux-leds.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: "Rafael J. Wysocki" <rafael.j.wysocki@intel.com>
To: Geert Uytterhoeven <geert+renesas@glider.be>,
	Bryan Wu <cooloney@gmail.com>
Cc: Mika Westerberg <mika.westerberg@linux.intel.com>,
	Alexandre Courbot <acourbot@nvidia.com>,
	Arnd Bergmann <arnd@arndb.de>,
	Grant Likely <grant.likely@linaro.org>,
	Richard Purdie <rpurdie@rpsys.net>,
	Linus Walleij <linus.walleij@linaro.org>,
	linux-leds@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
	linux-sh@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] leds: leds-gpio: Fix legacy GPIO number case
Date: Thu, 06 Nov 2014 18:31:58 +0100	[thread overview]
Message-ID: <545BB08E.60408@intel.com> (raw)
In-Reply-To: <1415273003-27674-1-git-send-email-geert+renesas@glider.be>

On 11/6/2014 12:23 PM, Geert Uytterhoeven wrote:
> In the legacy case, led_dat->gpiod is initialized correctly, but
> overwritten later by template->gpiod, which is NULL, causing leds-gpio
> to fail with:
>
>      gpiod_direction_output: invalid GPIO
>      leds-gpio: probe of leds-gpio failed with error -22
>
> Move the initialization of led_dat->gpiod from template->gpiod up, and
> always use led_dat->gpiod later, to fix this.
>
> Fixes: 5c51277a9ababfa4 ("leds: leds-gpio: Add support for GPIO descriptors")
> Signed-off-by: Geert Uytterhoeven <geert+renesas@glider.be>

Since it fixes a bug in a patch going from my tree, the fix needs to go 
into my tree as well.
Thus I'm going to take into my device-properties branch.

Bryan, please let me know if there are any problems with that.

Rafael


> ---
>   drivers/leds/leds-gpio.c | 6 +++---
>   1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/leds/leds-gpio.c b/drivers/leds/leds-gpio.c
> index ba4698c32bb04bde..b3c5d9d6a42bcd8b 100644
> --- a/drivers/leds/leds-gpio.c
> +++ b/drivers/leds/leds-gpio.c
> @@ -92,7 +92,8 @@ static int create_gpio_led(const struct gpio_led *template,
>   {
>   	int ret, state;
>   
> -	if (!template->gpiod) {
> +	led_dat->gpiod = template->gpiod;
> +	if (!led_dat->gpiod) {
>   		/*
>   		 * This is the legacy code path for platform code that
>   		 * still uses GPIO numbers. Ultimately we would like to get
> @@ -122,8 +123,7 @@ static int create_gpio_led(const struct gpio_led *template,
>   
>   	led_dat->cdev.name = template->name;
>   	led_dat->cdev.default_trigger = template->default_trigger;
> -	led_dat->gpiod = template->gpiod;
> -	led_dat->can_sleep = gpiod_cansleep(template->gpiod);
> +	led_dat->can_sleep = gpiod_cansleep(led_dat->gpiod);
>   	led_dat->blinking = 0;
>   	if (blink_set) {
>   		led_dat->platform_gpio_blink_set = blink_set;


      parent reply	other threads:[~2014-11-06 17:31 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2014-11-06 11:23 [PATCH] leds: leds-gpio: Fix legacy GPIO number case Geert Uytterhoeven
2014-11-06 11:50 ` Mika Westerberg
2014-11-06 17:31 ` Rafael J. Wysocki [this message]

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=545BB08E.60408@intel.com \
    --to=rafael.j.wysocki@intel.com \
    --cc=acourbot@nvidia.com \
    --cc=arnd@arndb.de \
    --cc=cooloney@gmail.com \
    --cc=geert+renesas@glider.be \
    --cc=grant.likely@linaro.org \
    --cc=linus.walleij@linaro.org \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=linux-sh@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.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;
as well as URLs for NNTP newsgroup(s).