From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Liviu Dudau <liviu@dudau.co.uk>
Cc: Linus Walleij <linus.walleij@linaro.org>,
Pavel Machek <pavel@ucw.cz>,
linux-leds@vger.kernel.org, LKML <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] leds: gpio: set led_dat->gpiod pointer for OF defined GPIO leds
Date: Thu, 25 Oct 2018 21:18:04 +0200 [thread overview]
Message-ID: <02905f80-4d61-33c7-778a-68e7aa29c2c2@gmail.com> (raw)
In-Reply-To: <20181023111842.GA29083@bart.dudau.co.uk>
Hi Liviu,
Thank you for the patch.
On 10/23/2018 01:18 PM, Liviu Dudau wrote:
> On Thu, Oct 18, 2018 at 01:14:32AM +0100, Liviu Dudau wrote:
>> Commit 45d4c6de4e49 ("leds: gpio: Try to lookup gpiod from device")
>> removed the common code path that set the led_dat->gpiod pointer in
>> create_gpio_led(), but only added it back for the devices that have
>> a valid gpio_led_platform_data structure. Calling gpio_leds_create()
>> in gpio_led_probe() is not enough to get a valid gpiod pointer.
>>
>> Fortunately enough, gpio_leds_create() already gets the needed pointer,
>> we just need to assign it to the relevant gpio_led_data structure.
>>
>> Fixes: 45d4c6de4e49 ("leds: gpio: Try to lookup gpiod from device")
>> Cc: Linus Walleij <linus.walleij@linaro.org>
>> Cc: Jacek Anaszewski <jacek.anaszewski@gmail.com>
>> Signed-off-by: Liviu Dudau <liviu@dudau.co.uk>
>> ---
>
> Gentle ping! I haven't seen any reply to this, even if the commit it fixes is
> still in for-next branch.
I found this message in the Spam folder of my gmail mailbox.
It can have something in common with the ASCII art in your signature.
Anyway, I've just applied the patch to the fixes-for-4.20-rc2 branch
of linux-leds.git.
Best regards,
Jacek Anaszewski
>
>>
>> Hi,
>>
>> I found this issue while testing linux-next-20181017, I don't know how
>> stable the leds for-next tree is in terms of commit IDs, if that gets
>> rebased then the Fixes commit ID needs updating.
>>
>> Best regards,
>> Liviu
>>
>> drivers/leds/leds-gpio.c | 2 ++
>> 1 file changed, 2 insertions(+)
>>
>> diff --git a/drivers/leds/leds-gpio.c b/drivers/leds/leds-gpio.c
>> index 32fa752565bc..45e012093865 100644
>> --- a/drivers/leds/leds-gpio.c
>> +++ b/drivers/leds/leds-gpio.c
>> @@ -163,6 +163,8 @@ static struct gpio_leds_priv *gpio_leds_create(struct platform_device *pdev)
>> return ERR_CAST(led.gpiod);
>> }
>>
>> + led_dat->gpiod = led.gpiod;
>> +
>> fwnode_property_read_string(child, "linux,default-trigger",
>> &led.default_trigger);
>>
>> --
>> 2.19.0
>>
>
next prev parent reply other threads:[~2018-10-25 19:18 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-10-18 0:14 Liviu Dudau
2018-10-23 11:18 ` Liviu Dudau
2018-10-25 13:08 ` Pavel Machek
2018-10-25 19:18 ` Jacek Anaszewski [this message]
2018-10-25 12:55 ` 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=02905f80-4d61-33c7-778a-68e7aa29c2c2@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=linus.walleij@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=liviu@dudau.co.uk \
--cc=pavel@ucw.cz \
/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®