From: Heiner Kallweit <hkallweit1@gmail.com>
To: Jacek Anaszewski <j.anaszewski@samsung.com>
Cc: "linux-leds@vger.kernel.org" <linux-leds@vger.kernel.org>,
Linux Kernel Mailing List <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 1/3] leds: triggers: add support for RGB triggers
Date: Thu, 17 Mar 2016 20:53:49 +0100 [thread overview]
Message-ID: <56EB0B4D.6040809@gmail.com> (raw)
In-Reply-To: <56EAB407.60904@samsung.com>
Am 17.03.2016 um 14:41 schrieb Jacek Anaszewski:
> Hi Heiner,
>
> On 03/13/2016 06:14 PM, Heiner Kallweit wrote:
>> Add basic support for RGB triggers. Triggers with flag LED_TRIG_CAP_RGB
>> set are available to RGB LED devices only.
>>
>> Signed-off-by: Heiner Kallweit <hkallweit1@gmail.com>
>> ---
>> drivers/leds/led-triggers.c | 15 ++++++++++++---
>> include/linux/leds.h | 3 +++
>> 2 files changed, 15 insertions(+), 3 deletions(-)
>>
>> diff --git a/drivers/leds/led-triggers.c b/drivers/leds/led-triggers.c
>> index 2181581..3ccf88b 100644
>> --- a/drivers/leds/led-triggers.c
>> +++ b/drivers/leds/led-triggers.c
>> @@ -30,6 +30,13 @@ static LIST_HEAD(trigger_list);
>>
>> /* Used by LED Class */
>>
>> +static inline bool led_trig_check_rgb(struct led_trigger *trig,
>> + struct led_classdev *led_cdev)
>> +{
>> + return !(trig->flags & LED_TRIG_CAP_RGB) ||
>> + led_cdev->flags & LED_DEV_CAP_RGB;
>> +}
>
> Could you explain what is the purpose of this function?
> What actually do we want to check here?
>
Triggers using RGB functionality can't be used with non-RGB LED's.
This check checks for such unsupported combinations:
It returns false if the trigger uses RGB functionality but LED doesn't
support the RGB extension.
>> ssize_t led_trigger_store(struct device *dev, struct device_attribute *attr,
>> const char *buf, size_t count)
>> {
>> @@ -52,12 +59,12 @@ ssize_t led_trigger_store(struct device *dev, struct device_attribute *attr,
>> down_read(&triggers_list_lock);
>> list_for_each_entry(trig, &trigger_list, next_trig) {
>> if (sysfs_streq(buf, trig->name)) {
>> + if (!led_trig_check_rgb(trig, led_cdev))
>> + break;
Check for the case that userspace wants to set a RGB trigger for a non-RGB LED via sysfs.
>> down_write(&led_cdev->trigger_lock);
>> led_trigger_set(led_cdev, trig);
>> up_write(&led_cdev->trigger_lock);
>> -
>> - up_read(&triggers_list_lock);
>> - goto unlock;
>> + break;
>> }
>> }
>> up_read(&triggers_list_lock);
>> @@ -84,6 +91,8 @@ ssize_t led_trigger_show(struct device *dev, struct device_attribute *attr,
>> len += sprintf(buf+len, "none ");
>>
>> list_for_each_entry(trig, &trigger_list, next_trig) {
>> + if (!led_trig_check_rgb(trig, led_cdev))
>> + continue;
Omit RGB triggers when listing the available triggers for a non-RGB LED via sysfs.
>> if (led_cdev->trigger && !strcmp(led_cdev->trigger->name,
>> trig->name))
>> len += sprintf(buf+len, "[%s] ", trig->name);
>> diff --git a/include/linux/leds.h b/include/linux/leds.h
>> index 58e22e6..07eb074 100644
>> --- a/include/linux/leds.h
>> +++ b/include/linux/leds.h
>> @@ -248,6 +248,9 @@ enum led_brightness led_hsv_to_rgb(enum led_brightness hsv);
>> struct led_trigger {
>> /* Trigger Properties */
>> const char *name;
>> + u8 flags;
>> +#define LED_TRIG_CAP_RGB BIT(0)
>> +
>> void (*activate)(struct led_classdev *led_cdev);
>> void (*deactivate)(struct led_classdev *led_cdev);
>>
>>
>
>
next prev parent reply other threads:[~2016-03-17 20:04 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-13 17:14 [PATCH 1/3] leds: triggers: add support for RGB triggers Heiner Kallweit
2016-03-17 13:41 ` Jacek Anaszewski
2016-03-17 19:53 ` Heiner Kallweit [this message]
2016-03-18 13:10 ` Jacek Anaszewski
2016-03-19 19:11 ` Heiner Kallweit
2016-03-21 15:35 ` Jacek Anaszewski
2016-03-21 17:34 ` Heiner Kallweit
2016-03-22 8:05 ` Jacek Anaszewski
2016-03-22 11:47 ` Heiner Kallweit
2016-03-22 16:00 ` Jacek Anaszewski
2016-03-22 22:06 ` Heiner Kallweit
2016-03-23 8:32 ` Jacek Anaszewski
2016-03-23 11:57 ` Heiner Kallweit
2016-03-23 16:02 ` Jacek Anaszewski
2016-03-23 16:36 ` Heiner Kallweit
2016-03-24 13:23 ` Jacek Anaszewski
2016-03-24 15:44 ` Heiner Kallweit
2016-03-24 21:32 ` Jacek Anaszewski
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=56EB0B4D.6040809@gmail.com \
--to=hkallweit1@gmail.com \
--cc=j.anaszewski@samsung.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
/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.