From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Jean-Jacques Hiblot <jjhiblot@ti.com>,
pavel@ucw.cz, robh+dt@kernel.org, mark.rutland@arm.com,
lee.jones@linaro.org, daniel.thompson@linaro.org
Cc: dmurphy@ti.com, linux-leds@vger.kernel.org,
linux-kernel@vger.kernel.org, dri-devel@lists.freedesktop.org,
tomi.valkeinen@ti.com
Subject: Re: [PATCH v7 2/5] leds: Add of_led_get() and led_put()
Date: Tue, 24 Sep 2019 23:08:51 +0200 [thread overview]
Message-ID: <700942d3-8e67-8520-d42a-605addcc2e06@gmail.com> (raw)
In-Reply-To: <20190918145730.22805-3-jjhiblot@ti.com>
Hi Jean,
Thank you for the patch.
I have one nit below.
On 9/18/19 4:57 PM, Jean-Jacques Hiblot wrote:
> From: Tomi Valkeinen <tomi.valkeinen@ti.com>
>
> This patch adds basic support for a kernel driver to get a LED device.
> This will be used by the led-backlight driver.
>
> Only OF version is implemented for now, and the behavior is similar to
> PWM's of_pwm_get() and pwm_put().
>
> Signed-off-by: Tomi Valkeinen <tomi.valkeinen@ti.com>
> Signed-off-by: Jean-Jacques Hiblot <jjhiblot@ti.com>
> Acked-by: Pavel Machek <pavel@ucw.cz>
> ---
> drivers/leds/led-class.c | 50 ++++++++++++++++++++++++++++++++++++++++
> include/linux/leds.h | 4 ++++
> 2 files changed, 54 insertions(+)
>
> diff --git a/drivers/leds/led-class.c b/drivers/leds/led-class.c
> index c2167b66b61f..2b8f20f94128 100644
> --- a/drivers/leds/led-class.c
> +++ b/drivers/leds/led-class.c
> @@ -19,6 +19,7 @@
> #include <linux/spinlock.h>
> #include <linux/timer.h>
> #include <uapi/linux/uleds.h>
> +#include <linux/of.h>
> #include "leds.h"
>
> static struct class *leds_class;
> @@ -214,6 +215,55 @@ static int led_resume(struct device *dev)
>
> static SIMPLE_DEV_PM_OPS(leds_class_dev_pm_ops, led_suspend, led_resume);
>
> +static int led_match_led_of_node(struct device *led_dev, const void *data)
> +{
> + return led_dev->of_node == data;
> +}
> +
> +/**
> + * of_led_get() - request a LED device via the LED framework
> + * @np: device node to get the LED device from
> + * @index: the index of the LED
> + *
> + * Returns the LED device parsed from the phandle specified in the "leds"
> + * property of a device tree node or a negative error-code on failure.
> + */
> +struct led_classdev *of_led_get(struct device_node *np, int index)
> +{
> + struct device *led_dev;
> + struct led_classdev *led_cdev;
> + struct device_node *led_node;
> +
> + led_node = of_parse_phandle(np, "leds", index);
> + if (!led_node)
> + return ERR_PTR(-ENOENT);
> +
> + led_dev = class_find_device(leds_class, NULL, led_node,
> + led_match_led_of_node);
Now we have class_find_device_by_of_node().
> + of_node_put(led_node);
> +
> + if (!led_dev)
> + return ERR_PTR(-EPROBE_DEFER);
> +
> + led_cdev = dev_get_drvdata(led_dev);
> +
> + if (!try_module_get(led_cdev->dev->parent->driver->owner))
> + return ERR_PTR(-ENODEV);
> +
> + return led_cdev;
> +}
> +EXPORT_SYMBOL_GPL(of_led_get);
> +
> +/**
> + * led_put() - release a LED device
> + * @led_cdev: LED device
> + */
> +void led_put(struct led_classdev *led_cdev)
> +{
> + module_put(led_cdev->dev->parent->driver->owner);
> +}
> +EXPORT_SYMBOL_GPL(led_put);
> +
> static int led_classdev_next_name(const char *init_name, char *name,
> size_t len)
> {
> diff --git a/include/linux/leds.h b/include/linux/leds.h
> index b8df71193329..6f7371bc7757 100644
> --- a/include/linux/leds.h
> +++ b/include/linux/leds.h
> @@ -20,6 +20,7 @@
>
> struct device;
> struct led_pattern;
> +struct device_node;
> /*
> * LED Core
> */
> @@ -196,6 +197,9 @@ extern void devm_led_classdev_unregister(struct device *parent,
> extern void led_classdev_suspend(struct led_classdev *led_cdev);
> extern void led_classdev_resume(struct led_classdev *led_cdev);
>
> +extern struct led_classdev *of_led_get(struct device_node *np, int index);
> +extern void led_put(struct led_classdev *led_cdev);
> +
> /**
> * led_blink_set - set blinking with software fallback
> * @led_cdev: the LED to start blinking
>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2019-09-24 21:08 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-18 14:57 [PATCH v7 0/5] Add a generic driver for LED-based backlight Jean-Jacques Hiblot
2019-09-18 14:57 ` [PATCH v7 1/5] leds: populate the device's of_node when possible Jean-Jacques Hiblot
2019-09-24 21:03 ` Jacek Anaszewski
2019-10-02 13:58 ` Jean-Jacques Hiblot
2019-10-02 19:47 ` Jacek Anaszewski
2019-09-18 14:57 ` [PATCH v7 2/5] leds: Add of_led_get() and led_put() Jean-Jacques Hiblot
2019-09-24 21:08 ` Jacek Anaszewski [this message]
2019-09-18 14:57 ` [PATCH v7 3/5] leds: Add managed API to get a LED from a device driver Jean-Jacques Hiblot
2019-09-24 21:10 ` Jacek Anaszewski
2019-09-18 14:57 ` [PATCH v7 4/5] dt-bindings: backlight: Add led-backlight binding Jean-Jacques Hiblot
2019-10-04 14:38 ` Lee Jones
2019-09-18 14:57 ` [PATCH v7 5/5] backlight: add led-backlight driver Jean-Jacques Hiblot
2019-10-04 14:39 ` Lee Jones
2019-10-04 15:49 ` Jean-Jacques Hiblot
2019-10-14 7:57 ` Lee Jones
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=700942d3-8e67-8520-d42a-605addcc2e06@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=daniel.thompson@linaro.org \
--cc=dmurphy@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jjhiblot@ti.com \
--cc=lee.jones@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pavel@ucw.cz \
--cc=robh+dt@kernel.org \
--cc=tomi.valkeinen@ti.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).