From: Richard Purdie <rpurdie@rpsys.net>
To: cbou@mail.ru
Cc: kogiidena@eggplant.ddo.jp, linux-kernel@vger.kernel.org,
lethal@linux-sh.org
Subject: Re: [PATCH 1/2] leds:arch/sh/boards/landisk LEDs supports
Date: Mon, 14 May 2007 00:16:22 +0100 [thread overview]
Message-ID: <1179098182.5883.31.camel@localhost.localdomain> (raw)
In-Reply-To: <20070509160328.GA13640@zarina>
On Wed, 2007-05-09 at 20:03 +0400, Anton Vorontsov wrote:
> Following patch sitting for a long time in our handhelds.org tree.
>
> kogiidena, I'm almost sure you'll find it useful, just apply patch,
> and implement .is_led_supported function for your trigger, which will
> eliminate trigger showing in
> /sys/class/leds/LED_WHICH_NOT_SUPPORTS_CUSTOM_TRIGGER/triggers
I like the approach and will apply something like this. Comments
follow...
> Custom triggers support, which are might not supported by all LEDs
>
> Signed-off-by: Anton Vorontsov <cbou@mail.ru>
>
> diff --git a/drivers/leds/led-triggers.c b/drivers/leds/led-triggers.c
> index 454fb09..0af0d61 100644
> --- a/drivers/leds/led-triggers.c
> +++ b/drivers/leds/led-triggers.c
> @@ -53,6 +53,9 @@ ssize_t led_trigger_store(struct class_device *dev, const char *buf,
> read_lock(&triggers_list_lock);
> list_for_each_entry(trig, &trigger_list, next_trig) {
> if (!strcmp(trigger_name, trig->name)) {
> + if (trig->is_led_supported &&
> + !trig->is_led_supported(led_cdev)) break;
Missing newline.
> @@ -85,6 +88,8 @@ ssize_t led_trigger_show(struct class_device *dev, char *buf)
> if (led_cdev->trigger && !strcmp(led_cdev->trigger->name,
> trig->name))
> len += sprintf(buf+len, "[%s] ", trig->name);
> + else if (trig->is_led_supported &&
> + !trig->is_led_supported(led_cdev)) continue;
ditto.
> @@ -127,6 +132,7 @@ void led_trigger_set(struct led_classdev *led_cdev, struct led_trigger *trigger)
> led_cdev->trigger->deactivate(led_cdev);
> led_set_brightness(led_cdev, LED_OFF);
> }
> + led_cdev->trigger = trigger;
> if (trigger) {
> write_lock_irqsave(&trigger->leddev_list_lock, flags);
> list_add_tail(&led_cdev->trig_list, &trigger->led_cdevs);
> @@ -134,7 +140,6 @@ void led_trigger_set(struct led_classdev *led_cdev, struct led_trigger *trigger)
> if (trigger->activate)
> trigger->activate(led_cdev);
> }
> - led_cdev->trigger = trigger;
> }
>
> void led_trigger_set_default(struct led_classdev *led_cdev)
Why was the above was changed?
I think we've discussed this before and it would be better to add a
trigger parameter to activate/deactivate if we really need it. Anyhow,
its not part of this patch and if you want that it should be in a
separate one with accompanying rational.
Can you resend with the above fixed and I'll apply.
Thanks,
Richard
next prev parent reply other threads:[~2007-05-13 23:16 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2007-05-08 12:26 [PATCH 1/2] leds:arch/sh/boards/landisk LEDs supports kogiidena
2007-05-08 12:54 ` Richard Purdie
2007-05-09 14:26 ` kogiidena
2007-05-09 15:13 ` Richard Purdie
2007-05-09 16:03 ` Anton Vorontsov
2007-05-10 11:52 ` kogiidena
2007-05-10 14:04 ` Paul Mundt
2007-05-11 15:03 ` kogiidena
2007-05-12 4:01 ` kogiidena
2007-05-13 23:16 ` Richard Purdie [this message]
2007-05-14 19:56 ` Anton Vorontsov
2007-05-14 20:12 ` Anton Vorontsov
2007-05-14 20:33 ` Richard Purdie
2007-05-14 21:13 ` Anton Vorontsov
2007-05-09 21:48 ` kogiidena
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=1179098182.5883.31.camel@localhost.localdomain \
--to=rpurdie@rpsys.net \
--cc=cbou@mail.ru \
--cc=kogiidena@eggplant.ddo.jp \
--cc=lethal@linux-sh.org \
--cc=linux-kernel@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.