From: Pavel Machek <pavel@ucw.cz>
To: Jean-Jacques Hiblot <jjhiblot@ti.com>
Cc: jacek.anaszewski@gmail.com, robh+dt@kernel.org,
mark.rutland@arm.com, lee.jones@linaro.org,
daniel.thompson@linaro.org, jingoohan1@gmail.com, 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 v3 1/4] leds: Add of_led_get() and led_put()
Date: Wed, 10 Jul 2019 21:09:50 +0200 [thread overview]
Message-ID: <20190710190949.GA22995@amd> (raw)
In-Reply-To: <20190710123932.28244-2-jjhiblot@ti.com>
[-- Attachment #1: Type: text/plain, Size: 1281 bytes --]
On Wed 2019-07-10 14:39:29, 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>
> @@ -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_node(struct device *led_dev, const void *data)
> +{
> + return led_dev->of_node == data ? 1 : 0;
> +}
Get rid of the "? 1 : 0"?
> + 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_node);
> + of_node_put(led_node);
> +
> + if (!led_dev)
> + return ERR_PTR(-EPROBE_DEFER);
Won't this defer probe "forever" when the driver is not available?
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 181 bytes --]
next prev parent reply other threads:[~2019-07-10 19:09 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-07-10 12:39 [PATCH v3 0/4] Add a generic driver for LED-based backlight Jean-Jacques Hiblot
2019-07-10 12:39 ` Jean-Jacques Hiblot
2019-07-10 12:39 ` [PATCH v3 1/4] leds: Add of_led_get() and led_put() Jean-Jacques Hiblot
2019-07-10 12:39 ` Jean-Jacques Hiblot
2019-07-10 19:09 ` Pavel Machek [this message]
2019-07-12 13:52 ` Jean-Jacques Hiblot
2019-07-12 13:52 ` Jean-Jacques Hiblot
2019-07-10 12:39 ` [PATCH v3 2/4] leds: Add managed API to get a LED from a device driver Jean-Jacques Hiblot
2019-07-10 12:39 ` Jean-Jacques Hiblot
2019-07-10 19:11 ` Pavel Machek
2019-07-10 12:39 ` [PATCH v3 3/4] dt-bindings: backlight: Add led-backlight binding Jean-Jacques Hiblot
2019-07-10 12:39 ` Jean-Jacques Hiblot
2019-07-10 19:13 ` Pavel Machek
2019-07-12 13:57 ` Jean-Jacques Hiblot
2019-07-12 13:57 ` Jean-Jacques Hiblot
2019-07-10 12:39 ` [PATCH v3 4/4] backlight: add led-backlight driver Jean-Jacques Hiblot
2019-07-10 12:39 ` Jean-Jacques Hiblot
2019-07-10 19:16 ` Pavel Machek
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=20190710190949.GA22995@amd \
--to=pavel@ucw.cz \
--cc=daniel.thompson@linaro.org \
--cc=dmurphy@ti.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=jacek.anaszewski@gmail.com \
--cc=jingoohan1@gmail.com \
--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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.