From: Juergen Schindele <schindele@nentec.de>
To: linux-leds@vger.kernel.org
Subject: Switching off LED triggers udev
Date: Mon, 10 Apr 2017 16:29:30 +0200 [thread overview]
Message-ID: <1803981.yiQbQ3iWBI@sherry> (raw)
Hello List,
i hope i found the right addres for this small problem.
I have a userspace daemon which controls leds via sysfs API
"/sys/class/leds/Soft1/brightness". Each time i turn the LED off
by writing 0 to brightness the /proc/sys/kernel/hotplug deamon
is called with "ACTION:change SUBSYSTEM:leds DEVNAME:(null)
DEVPATH:/devices/...."
from led-class.c ----------------------------
if (state == LED_OFF)
led_trigger_remove(led_cdev);
__led_set_brightness(led_cdev, state);
But in fact there is no change of trigger because "none" was setup between
enabling LED and disabling it. So from my point of view there is no change
from "none" to "remove" which justifies a "kobject_uevent_env(&led_cdev->dev-
>kobj, KOBJ_CHANGE, envp)".
To solve this problem of unusefull waste of CPU-time i suggest the following
patch. Please consider the implementation which saved a lot of valuable CPU-
power in my case:
Index: drivers/leds/led-triggers.c
===================================================================
--- drivers/leds/led-triggers.c (Revision 14968)
+++ drivers/leds/led-triggers.c (Arbeitskopie)
@@ -106,10 +106,11 @@
const char *name;
name = trig ? trig->name : "none";
- event = kasprintf(GFP_KERNEL, "TRIGGER=%s", name);
/* Remove any existing trigger */
if (led_cdev->trigger) {
+ event = kasprintf(GFP_KERNEL, "TRIGGER=%s", name);
+
write_lock_irqsave(&led_cdev->trigger->leddev_list_lock,
flags);
list_del(&led_cdev->trig_list);
write_unlock_irqrestore(&led_cdev->trigger->leddev_list_lock,
@@ -122,6 +123,8 @@
led_set_brightness(led_cdev, LED_OFF);
}
if (trig) {
+ event = kasprintf(GFP_KERNEL, "TRIGGER=%s", name);
+
write_lock_irqsave(&trig->leddev_list_lock, flags);
list_add_tail(&led_cdev->trig_list, &trig->led_cdevs);
write_unlock_irqrestore(&trig->leddev_list_lock, flags);
Thank you for your attention
--
i. A.
Jürgen Schindele
Softwareentwicklung
PSI Nentec GmbH
Greschbachstraße 12
76229 Karlsruhe
Deutschland
Telefon: +49 721 94249-51
Telefax: +49 721 94249-10
schindele@nentec.de
www.nentec.de
Geschäftsführung: Klaus Becker, Wolfgang Fischer
Sitz der Gesellschaft: Karlsruhe
Handelsregister: Amtsgericht Mannheim HRB 107658
Diese E-Mail enthält vertrauliche oder rechtlich geschützte Informationen.
Wenn Sie nicht der vorgesehene Empfänger sind, informieren Sie bitte sofort
den Absender und löschen Sie diese E-Mail. Das unbefugte Kopieren dieser E-
Mail oder die unbefugte Weitergabe der enthaltenen Informationen ist nicht
gestattet.
The information contained in this message is confidential or protected by law.
If you are not the intended recipient, please contact the sender and delete
this message. Any unauthorised copying of this message or unauthorised
distribution of the information contained herein is prohibited.
next reply other threads:[~2017-04-10 14:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-04-10 14:29 Juergen Schindele [this message]
2017-04-10 18:42 ` Switching off LED triggers udev Jacek Anaszewski
2017-04-11 7:25 ` Juergen Schindele
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=1803981.yiQbQ3iWBI@sherry \
--to=schindele@nentec.de \
--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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox