From: Jacek Anaszewski <j.anaszewski@samsung.com>
To: "Rafał Miłecki" <zajec5@gmail.com>
Cc: Richard Purdie <rpurdie@rpsys.net>,
"open list:LED SUBSYSTEM" <linux-leds@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] leds: leds-gpio: Set of_node for created LED devices
Date: Mon, 11 Jul 2016 09:34:30 +0200 [thread overview]
Message-ID: <57834C06.4020506@samsung.com> (raw)
In-Reply-To: <1467982420-15718-1-git-send-email-zajec5@gmail.com>
Hi Rafał,
Thanks for the patch.
On 07/08/2016 02:53 PM, Rafał Miłecki wrote:
> When working with Device Tree we iterate over children of "gpio-leds"
> compatible node and create LED device for each of them. We take care of
> all common DT properties (label, default trigger, state, etc.), however
> some triggers may want to support more of them.
>
> It could be useful for timer trigger to support setting delay on/off
> values with Device Tree property. Or for transient trigger to support
> e.g. duration property.
>
> We obviously should handle such properties in triggers, not in generic
> code. To let trigger drivers read properties from DT node we need to set
> of_node to point the relevant node. This change allows using all kind of
> of helpers in e.g. "activate" callbacks.
>
> Signed-off-by: Rafał Miłecki <zajec5@gmail.com>
> ---
> drivers/leds/leds-gpio.c | 5 +++--
> 1 file changed, 3 insertions(+), 2 deletions(-)
>
> diff --git a/drivers/leds/leds-gpio.c b/drivers/leds/leds-gpio.c
> index 8229f06..9b991d4 100644
> --- a/drivers/leds/leds-gpio.c
> +++ b/drivers/leds/leds-gpio.c
> @@ -165,6 +165,7 @@ static struct gpio_leds_priv *gpio_leds_create(struct platform_device *pdev)
> return ERR_PTR(-ENOMEM);
>
> device_for_each_child_node(dev, child) {
> + struct gpio_led_data *led_dat = &priv->leds[priv->num_leds];
This seems to be an unrelated change.
> struct gpio_led led = {};
> const char *state = NULL;
>
> @@ -205,12 +206,12 @@ static struct gpio_leds_priv *gpio_leds_create(struct platform_device *pdev)
> if (fwnode_property_present(child, "panic-indicator"))
> led.panic_indicator = 1;
>
> - ret = create_gpio_led(&led, &priv->leds[priv->num_leds],
> - dev, NULL);
> + ret = create_gpio_led(&led, led_dat, dev, NULL);
> if (ret < 0) {
> fwnode_handle_put(child);
> goto err;
> }
> + led_dat->cdev.dev->of_node = np;
> priv->num_leds++;
> }
>
>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2016-07-11 7:34 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-07-08 12:53 [PATCH] leds: leds-gpio: Set of_node for created LED devices Rafał Miłecki
2016-07-11 7:34 ` Jacek Anaszewski [this message]
2016-07-11 7:52 ` Rafał Miłecki
2016-07-11 8:20 ` Jacek Anaszewski
2016-07-11 8:23 ` Rafał Miłecki
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=57834C06.4020506@samsung.com \
--to=j.anaszewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=rpurdie@rpsys.net \
--cc=zajec5@gmail.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