From: Jacek Anaszewski <jacek.anaszewski@gmail.com>
To: Krzysztof Kozlowski <krzk@kernel.org>,
Pavel Machek <pavel@ucw.cz>, Rob Herring <robh+dt@kernel.org>,
Mark Rutland <mark.rutland@arm.com>,
Baolin Wang <baolin.wang@linaro.org>,
Raphael Teysseyre <rteysseyre@gmail.com>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 4/4] leds: trigger: Add pattern initialization from Device Tree
Date: Sun, 9 Dec 2018 19:55:26 +0100 [thread overview]
Message-ID: <fcb28be6-7d6a-1216-5a22-339f30366fd1@gmail.com> (raw)
In-Reply-To: <8222f85b-4e61-69c4-6d31-ba559de02829@gmail.com>
On 12/8/18 7:44 PM, Jacek Anaszewski wrote:
> Hi Krzysztof,
>
> Thank you for the patch set.
>
> Applied 1/4 and 2/4.
>
> I'll hold on merging 3/4 until we sort out the issues
> I have with this one. Please refer to my comment below.
>
> On 12/7/18 1:32 PM, Krzysztof Kozlowski wrote:
>> Allow initialization of pattern used in pattern trigger from Device Tree
>> property.
>>
>> This is especially useful for embedded systems where the pattern trigger
>> would be used to indicate the process of boot status in a nice,
>> user-friendly blinking way. This initialization pattern will be used
>> till user-space is brought up and sets its own pattern, indicating the
>> boot status is for example finished.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzk@kernel.org>
>> ---
>> drivers/leds/trigger/ledtrig-pattern.c | 18 ++++++++++++++++++
>> 1 file changed, 18 insertions(+)
>>
>> diff --git a/drivers/leds/trigger/ledtrig-pattern.c
>> b/drivers/leds/trigger/ledtrig-pattern.c
>> index 1870cf87afe1..96309d3bc43c 100644
>> --- a/drivers/leds/trigger/ledtrig-pattern.c
>> +++ b/drivers/leds/trigger/ledtrig-pattern.c
>> @@ -11,6 +11,7 @@
>> #include <linux/leds.h>
>> #include <linux/module.h>
>> #include <linux/mutex.h>
>> +#include <linux/of.h>
>> #include <linux/slab.h>
>> #include <linux/timer.h>
>> @@ -331,6 +332,21 @@ static const struct attribute_group
>> *pattern_trig_groups[] = {
>> NULL,
>> };
>> +static void pattern_init(struct led_classdev *led_cdev)
>> +{
>> + struct device_node *np = dev_of_node(led_cdev->dev);
>> + const char *pattern;
>> +
>> + if (!np)
>> + return;
>> +
>> + if (!of_property_read_string(np, "linux,trigger-pattern",
>> &pattern)) {
>> + if (strlen(pattern))
>> + pattern_trig_store_patterns(led_cdev, pattern,
>> + strlen(pattern), false);
>> + }
>> +}
>> +
>> static int pattern_trig_activate(struct led_classdev *led_cdev)
>> {
>> struct pattern_trig_data *data;
>> @@ -354,6 +370,8 @@ static int pattern_trig_activate(struct
>> led_classdev *led_cdev)
>> timer_setup(&data->timer, pattern_trig_timer_function, 0);
>> led_cdev->activated = true;
>> + pattern_init(led_cdev);
With my recent patches it would suffice to replace above line with:
if (led_cdev->flags & LED_INIT_DEFAULT_TRIGGER) {
pattern_init(led_cdev);
led_cdev->flags &= ~LED_INIT_DEFAULT_TRIGGER;
}
> It means that the pattern defined in DT would be applied
> whenever the pattern trigger is set for a LED class device,
> whereas it should happen only on LED class device initialization,
> if linux,default-trigger is set to "pattern".
>
> What we would need for making that work is a generic support for
> parsing trigger specific initialization data in the
> of_led_classdev_register().
>
>> +
>> return 0;
>> }
>>
>
--
Best regards,
Jacek Anaszewski
next prev parent reply other threads:[~2018-12-09 18:55 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-12-07 12:32 [PATCH 1/4] leds: pwm: Simplify with resource-managed devm_led_classdev_register() Krzysztof Kozlowski
2018-12-07 12:32 ` [PATCH 2/4] leds: pwm: Use OF variant of LED registering function Krzysztof Kozlowski
2018-12-07 12:32 ` [PATCH 3/4] dt-bindings: leds: Add pattern initialization from Device Tree Krzysztof Kozlowski
2018-12-07 12:32 ` [PATCH 4/4] leds: trigger: " Krzysztof Kozlowski
2018-12-08 18:44 ` Jacek Anaszewski
2018-12-09 18:55 ` Jacek Anaszewski [this message]
2018-12-10 8:35 ` Krzysztof Kozlowski
2018-12-09 8:17 ` Pavel Machek
2018-12-10 8:34 ` Krzysztof Kozlowski
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=fcb28be6-7d6a-1216-5a22-339f30366fd1@gmail.com \
--to=jacek.anaszewski@gmail.com \
--cc=baolin.wang@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk@kernel.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=rteysseyre@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
all inboxes | Powered by JetHome®