leds: add device trigger
Subsystems (2)
cover leds: add device trigger
A series of patches that add yet another LED trigger, a device activity trigger.
The motivation is to have a LED trigger that is associated with a device and can be fired from cetrain points in the code that have been chosen by the developer. With this this device activity trigger it is possible for instance to easily hook up a tty driver for a console to blink one LED, yet another serial port to blink a second LED and writes to a block device to trigger a third LED.
The patches have been tested on Wandboard Quad.
The first patch adds the actual trigger. Each device wishing to use the trigger has to be explicitly registered by calling ledtrig_dev_add(), and passing it's dev_t. The intention is that the trigger will be used in scenarios that are impossible to foresee at this moment, and are likely to be approach in a case by case manner anyway.
The second patch adds couple of debugfs helpers.
The third patch adds documentation and notes on debugfs interface.
Maciek Borzecki (3):
leds: add device activity LED triggers
leds: add debugfs to device trigger
Documentation: leds: document ledtrig-device trigger
Documentation/leds/00-INDEX | 3 + Documentation/leds/ledtrig-device.txt | 32 ++++ drivers/leds/trigger/Kconfig | 8 + drivers/leds/trigger/Makefile | 1 + drivers/leds/trigger/ledtrig-device.c | 289 ++++++++++++++++++++++++++++++++++ include/linux/leds.h | 10 ++ 6 files changed, 343 insertions(+) create mode 100644 Documentation/leds/ledtrig-device.txt create mode 100644 drivers/leds/trigger/ledtrig-device.c
Signature · 1 line
2.5.3
PATCH 1/3 leds: add device activity LED triggers
The patch adds LED triggers for indicating an activity on a selected device. The drivers that intend to use triggers need to register respective devices using ledtrig_dev_add(). Triggers are generated by explicitly calling ledtrig_dev_activity().
--- drivers/leds/trigger/Kconfig | 8 ++ drivers/leds/trigger/Makefile | 1 + drivers/leds/trigger/ledtrig-device.c | 185 ++++++++++++++++++++++++++++++++++ include/linux/leds.h | 10 ++ 4 files changed, 204 insertions(+) create mode 100644 drivers/leds/trigger/ledtrig-device.c
drivers/leds/trigger/Kconfig +8 -0
@@ -108,4 +108,12 @@ config LEDS_TRIGGER_CAMERA This enables direct flash/torch on/off by the driver, kernel space. If unsure, say Y. +config LEDS_TRIGGER_DEVICE + bool "LED Device Activity Trigger" + depends on LEDS_TRIGGERS + help + This allows LEDs to be triggered by an actvity on a selected + device. + If unsure, say Y. + endif # LEDS_TRIGGERS
drivers/leds/trigger/Makefile +1 -0
@@ -8,3 +8,4 @@ obj-$(CONFIG_LEDS_TRIGGER_CPU) += ledtrig-cpu.o obj-$(CONFIG_LEDS_TRIGGER_DEFAULT_ON) += ledtrig-default-on.o obj-$(CONFIG_LEDS_TRIGGER_TRANSIENT) += ledtrig-transient.o obj-$(CONFIG_LEDS_TRIGGER_CAMERA) += ledtrig-camera.o +obj-$(CONFIG_LEDS_TRIGGER_DEVICE) += ledtrig-device.o
drivers/leds/trigger/ledtrig-device.c new file +185 -0
185 lines not on this page · raw message
include/linux/leds.h +10 -0
@@ -369,4 +369,14 @@ static inline void ledtrig_cpu(enum cpu_led_event evt) }#endif +#ifdef CONFIG_LEDS_TRIGGER_DEVICE +extern void ledtrig_dev_add (dev_t dev); +extern void ledtrig_dev_del (dev_t dev); +extern void ledtrig_dev_activity (dev_t dev); +#else +static inline void ledtrig_dev_add (dev_t dev) {} +static inline void ledtrig_dev_del (dev_t dev) {} +static inline void ledtrig_dev_activity (dev_t dev) {} +#endif +#endif /* __LINUX_LEDS_H_INCLUDED */
Signature · 1 line
2.5.3
PATCH 2/3 leds: add debugfs to device trigger
In reply to Maciek BorzeckiAdd debugfs entries for device activity trigger. Three entries are created under /sys/kernel/debug/ledtrig-dev when the driver gets loaded. These are:
devices - cat'ing will produce a list of currently registered devices
in <major>:<minor> format, a line for each device.
register - echo'ing <major>:<minor> will create a trigger for this
device
trigger - echo'ing <major>:<minor> will fire a trigger for this device
--- drivers/leds/trigger/ledtrig-device.c | 113 +++++++++++++++++++++++++++++++++- 1 file changed, 111 insertions(+), 2 deletions(-)
drivers/leds/trigger/ledtrig-device.c +111 -2
@@ -16,15 +16,18 @@#include <linux/list.h> #include <linux/rwsem.h> #include <linux/kdev_t.h> +#include <linux/fs.h> +#include <linux/debugfs.h> +#include <linux/seq_file.h> #define BLINK_DELAY 30static unsigned long blink_delay =BLINK_DELAY ;static DECLARE_RWSEM (devs_list_lock);static LIST_HEAD (devs_list); +static struct dentry *debug_root;#define MAX_NAME_LEN 20 -struct ledtrig_dev_data {char name[MAX_NAME_LEN ];dev_t dev;
@@ -114,8 +117,11 @@ void ledtrig_dev_add(dev_t dev)/* register with led triggers */ led_trigger_register_simple (new_dev_trig->name, &new_dev_trig->trig); - else + else { +pr_warn ("device %u:%u already registered\n" , +MAJOR (dev),MINOR (dev));kfree (new_dev_trig); + } }EXPORT_SYMBOL (ledtrig_dev_add);
@@ -167,13 +173,116 @@ static void ledtrig_dev_remove_all(void)up_write (&devs_list_lock); } +static int ledtrig_dev_devices_show (struct seq_file *s,void *unused) +{ +struct ledtrig_dev_data *dev_trig; + +down_read (&devs_list_lock); +list_for_each_entry (dev_trig, &devs_list, node) { +seq_printf (s,"%u:%u\n" ,MAJOR (dev_trig->dev), +MINOR (dev_trig->dev)); + } +up_read (&devs_list_lock); +return 0 ; +} + +static int ledtrig_dev_devices_open (struct inode *inode,struct file *file) +{ +return single_open (file, ledtrig_dev_devices_show, + &inode->i_private); +} + +static const struct file_operations debug_devices_ops = { + .owner =THIS_MODULE , + .open = ledtrig_dev_devices_open, + .read = seq_read, + .llseek = seq_lseek, + .release = single_release +}; + +static int get_dev_from_user (const char __user *buf,size_t size, +dev_t *dev) +{ +unsigned int major; +unsigned int minor; +int ret; + +WARN_ON (dev ==NULL ); +if (dev ==NULL ) +return -EINVAL ; + + ret =sscanf (buf,"%u:%u" , &major, &minor); +if (ret <2 ) +return -EINVAL ; + + *dev =MKDEV (major, minor); +return 0 ; +} + +static ssize_t ledtrig_dev_register_write (struct file *filp, +const char __user *buf, +size_t size,loff_t *off) +{ +dev_t dev; +int ret; + + ret =get_dev_from_user (buf, size, &dev); +if (ret <0 ) +return ret; + +pr_debug ("got device %u:%u\n" ,MAJOR (dev),MINOR (dev)); +ledtrig_dev_add (dev); + +return size; +} + +static const struct file_operations debug_register_ops = { + .owner =THIS_MODULE , + .write = ledtrig_dev_register_write, +}; + +static ssize_t ledtrig_dev_trigger_write (struct file *filp, +const char __user *buf, +size_t size,loff_t *off) +{ +dev_t dev; +int ret; + + ret =get_dev_from_user (buf, size, &dev); +if (ret <0 ) +return ret; + +pr_debug ("trigger device %u:%u\n" ,MAJOR (dev),MINOR (dev)); +ledtrig_dev_activity (dev); + +return size; +} + +static const struct file_operations debug_trigger_ops = { + .owner =THIS_MODULE , + .write = ledtrig_dev_trigger_write, +}; +static int __init ledtrig_dev_init (void ) { + debug_root =debugfs_create_dir ("ledtrig-dev" ,NULL ); + +if (debug_root) { +debugfs_create_file ("devices" ,0444 , debug_root,NULL , + &debug_devices_ops); +debugfs_create_file ("register" ,0200 , debug_root,NULL , + &debug_register_ops); +debugfs_create_file ("trigger" ,0200 , debug_root,NULL , + &debug_trigger_ops); + } +return 0 ; } static void __exit ledtrig_dev_exit(void) { +debugfs_remove_recursive (debug_root); +ledtrig_dev_remove_all (); }
Signature · 1 line
2.5.3
kbuild test robot
build botRe: [PATCH 2/3] leds: add debugfs to device trigger
reproduce:
Hi Maciek,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
reproduce:
# apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__
sparse warnings: (new ones prefixed by >>)
>> drivers/leds/trigger/ledtrig-device.c:214:22: sparse: incorrect type in argument 1 (different address spaces)
drivers/leds/trigger/ledtrig-device.c:214:22: expected char const *<noident>
drivers/leds/trigger/ledtrig-device.c:214:22: got char const [noderef] <asn:1>*buf
vim +214 drivers/leds/trigger/ledtrig-device.c
198 .read = seq_read,
199 .llseek = seq_lseek,
200 .release = single_release
201 };
202
203 static int get_dev_from_user(const char __user *buf, size_t size,
204 dev_t *dev)
205 {
206 unsigned int major;
207 unsigned int minor;
208 int ret;
209
210 WARN_ON(dev == NULL);
211 if (dev == NULL)
212 return -EINVAL;
213
> 214 ret = sscanf(buf, "%u:%u", &major, &minor);
215 if (ret < 2)
216 return -EINVAL;
217
218 *dev = MKDEV(major, minor);
219 return 0;
220 }
221
222 static ssize_t ledtrig_dev_register_write(struct file *filp,
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
Re: [PATCH 2/3] leds: add debugfs to device trigger
Quoted 10 lines · kbuild test robot
Hi Maciek,
[auto build test results on v4.3-rc3 -- if it's inappropriate base, please ignore]
reproduce:
# apt-get install sparse make ARCH=x86_64 allmodconfig make C=1 CF=-D__CHECK_ENDIAN__
Quoted 5 lines
sparse warnings: (new ones prefixed by >>)
Quoted 1 line
Quoted 1 line
drivers/leds/trigger/ledtrig-device.c:214:22: sparse: incorrect type in argument 1 (different address spaces)
drivers/leds/trigger/ledtrig-device.c:214:22: expected char const *<noident>
drivers/leds/trigger/ledtrig-device.c:214:22: got char const [noderef] <asn:1>*buf
Right, noted right after sending the patch. Will fix in v2.
Quoted 29 lines
vim +214
drivers/leds/trigger/ledtrig-device.c198 .read = seq_read, 199 .llseek = seq_lseek, 200 .release = single_release 201 }; 202 203 static int get_dev_from_user(const char __user *buf, size_t size, 204 dev_t *dev) 205 { 206 unsigned int major; 207 unsigned int minor; 208 int ret; 209 210 WARN_ON(dev == NULL); 211 if (dev == NULL) 212 return -EINVAL; 213Quoted 1 line
214 ret =
sscanf(buf, "%u:%u", &major, &minor);215 if (ret < 2)
216 return -EINVAL; 217 218 *dev = MKDEV(major, minor); 219 return 0; 220 } 221 222 static ssize_t ledtrig_dev_register_write(struct file *filp,
Quoted 3 lines
---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation
--
Maciek Borzecki
Re: [PATCH 2/3] leds: add debugfs to device trigger
In reply to Maciek BorzeckiHi Maciek,
Please test your solution thoroughly before submitting the next version. Writing to debugfs register attribute fails due to lack of proper copying from user memory, which makes testing impossible.
Best Regards,
Jacek Anaszewski
Quoted 172 lines · Maciek Borzecki
Add debugfs entries for device activity trigger. Three entries are created under
/sys/kernel/debug/ledtrig-devwhen the driver gets loaded. These are:devices - cat'ing will produce a list of currently registered devices
in <major>:<minor> format, a line for each device.register - echo'ing <major>:<minor> will create a trigger for this
devicetrigger - echo'ing <major>:<minor> will fire a trigger for this device
Signed-off-by Maciek Borzecki <[email protected]>--- drivers/leds/trigger/ledtrig-device.c | 113 +++++++++++++++++++++++++++++++++- 1 file changed, 111 insertions(+), 2 deletions(-)drivers/leds/trigger/ledtrig-device.c +111
-2@@ -16,15 +16,18 @@#include <linux/list.h> #include <linux/rwsem.h> #include <linux/kdev_t.h> +#include <linux/fs.h> +#include <linux/debugfs.h> +#include <linux/seq_file.h> #define BLINK_DELAY 30static unsigned long blink_delay =BLINK_DELAY ;static DECLARE_RWSEM (devs_list_lock);static LIST_HEAD (devs_list); +static struct dentry *debug_root;#define MAX_NAME_LEN 20 -struct ledtrig_dev_data {char name[MAX_NAME_LEN ];dev_t dev;@@ -114,8 +117,11 @@ void ledtrig_dev_add(dev_t dev)/* register with led triggers */ led_trigger_register_simple (new_dev_trig->name, &new_dev_trig->trig); - else + else { +pr_warn ("device %u:%u already registered\n" , +MAJOR (dev),MINOR (dev));kfree (new_dev_trig); + } }EXPORT_SYMBOL (ledtrig_dev_add);@@ -167,13 +173,116 @@ static void ledtrig_dev_remove_all(void)up_write (&devs_list_lock); } +static int ledtrig_dev_devices_show (struct seq_file *s,void *unused) +{ +struct ledtrig_dev_data *dev_trig; + +down_read (&devs_list_lock); +list_for_each_entry (dev_trig, &devs_list, node) { +seq_printf (s,"%u:%u\n" ,MAJOR (dev_trig->dev), +MINOR (dev_trig->dev)); + } +up_read (&devs_list_lock); +return 0 ; +} + +static int ledtrig_dev_devices_open (struct inode *inode,struct file *file) +{ +return single_open (file, ledtrig_dev_devices_show, + &inode->i_private); +} + +static const struct file_operations debug_devices_ops = { + .owner =THIS_MODULE , + .open = ledtrig_dev_devices_open, + .read = seq_read, + .llseek = seq_lseek, + .release = single_release +}; + +static int get_dev_from_user (const char __user *buf,size_t size, +dev_t *dev) +{ +unsigned int major; +unsigned int minor; +int ret; + +WARN_ON (dev ==NULL ); +if (dev ==NULL ) +return -EINVAL ; + + ret =sscanf (buf,"%u:%u" , &major, &minor); +if (ret <2 ) +return -EINVAL ; + + *dev =MKDEV (major, minor); +return 0 ; +} + +static ssize_t ledtrig_dev_register_write (struct file *filp, +const char __user *buf, +size_t size,loff_t *off) +{ +dev_t dev; +int ret; + + ret =get_dev_from_user (buf, size, &dev); +if (ret <0 ) +return ret; + +pr_debug ("got device %u:%u\n" ,MAJOR (dev),MINOR (dev)); +ledtrig_dev_add (dev); + +return size; +} + +static const struct file_operations debug_register_ops = { + .owner =THIS_MODULE , + .write = ledtrig_dev_register_write, +}; + +static ssize_t ledtrig_dev_trigger_write (struct file *filp, +const char __user *buf, +size_t size,loff_t *off) +{ +dev_t dev; +int ret; + + ret =get_dev_from_user (buf, size, &dev); +if (ret <0 ) +return ret; + +pr_debug ("trigger device %u:%u\n" ,MAJOR (dev),MINOR (dev)); +ledtrig_dev_activity (dev); + +return size; +} + +static const struct file_operations debug_trigger_ops = { + .owner =THIS_MODULE , + .write = ledtrig_dev_trigger_write, +}; +static int __init ledtrig_dev_init (void ) { + debug_root =debugfs_create_dir ("ledtrig-dev" ,NULL ); + +if (debug_root) { +debugfs_create_file ("devices" ,0444 , debug_root,NULL , + &debug_devices_ops); +debugfs_create_file ("register" ,0200 , debug_root,NULL , + &debug_register_ops); +debugfs_create_file ("trigger" ,0200 , debug_root,NULL , + &debug_trigger_ops); + } +return 0 ; } static void __exit ledtrig_dev_exit(void) { +debugfs_remove_recursive (debug_root); +ledtrig_dev_remove_all (); }
Re: [PATCH 2/3] leds: add debugfs to device trigger
Quoted 6 lines · Jacek Anaszewski
Hi Maciek,
Please test your solution thoroughly before submitting the next version. Writing to debugfs register attribute fails due to lack of proper copying from user memory, which makes testing impossible.
Hi, thanks for the comment. Indeed, I noticed the problem just after sending the patch. Surprisingly this didn't fail on iMX6 for some reason.
Aside from the __user access problem, is the approach, in general, ok for you or would you suggest that I changed something?
Regards,
--
Maciek Borzecki
Re: [PATCH 2/3] leds: add debugfs to device trigger
Quoted 8 lines · Maciek Borzecki
Quoted 6 lines · Jacek Anaszewski
Hi Maciek,
Please test your solution thoroughly before submitting the next version. Writing to debugfs register attribute fails due to lack of proper copying from user memory, which makes testing impossible.
Quoted 6 lines
Hi, thanks for the comment. Indeed, I noticed the problem just after sending the patch. Surprisingly this didn't fail on iMX6 for some reason.
Aside from the
__useraccess problem, is the approach, in general, ok for you or would you suggest that I changed something?
At first glance the feature looks nice. I'll be able to say more after testing working version.
Signature · 2 lines
Best Regards, Jacek Anaszewski
Re: [PATCH 2/3] leds: add debugfs to device trigger
In reply to Maciek BorzeckiQuoted 11 lines · Maciek Borzecki
Add debugfs entries for device activity trigger. Three entries are created under
/sys/kernel/debug/ledtrig-devwhen the driver gets loaded. These are:devices - cat'ing will produce a list of currently registered devices
in <major>:<minor> format, a line for each device.register - echo'ing <major>:<minor> will create a trigger for this
devicetrigger - echo'ing <major>:<minor> will fire a trigger for this device
Debugfs? Please don't. This is not debugging infrastructure.
PATCH 3/3 Documentation: leds: document ledtrig-device trigger
In reply to Maciek BorzeckiThis patch adds documentation for ledtrig-device trigger.
--- Documentation/leds/00-INDEX | 3 +++ Documentation/leds/ledtrig-device.txt | 32 ++++++++++++++++++++++++++++++++ 2 files changed, 35 insertions(+) create mode 100644 Documentation/leds/ledtrig-device.txt
Documentation/leds/00-INDEX +3 -0
@@ -20,3 +20,6 @@ ledtrig-oneshot.txt - One-shot LED trigger for both sporadic and dense events. ledtrig-transient.txt - LED Transient Trigger, one shot timer activation. +ledtrig-device.txt + - LED Device Activity Trigger for indicating an activity + on a device
Documentation/leds/ledtrig-device.txt new file +32 -0
@@ -0,0 +1,32 @@ +Device Activity LED Trigger +========================== + +This is a LED trigger useful for signaling an activity on a given +device identified by it's MKDEV(major, minor). A typical use case +would be debugging of a device or a driver on an embedded board, +patching up trivial electronic hardware design deficiencies in +software or just plain desire to indicate activity on a certain +device. + +Internally, a instance of a trigger is created and registered with LED +triggers for every device added via ledtrig_dev_add() call. The +triggers are named in the following manner: + + `dev-<major>:<minor>` + +And can be selected from under /sys/class/leds/*/trigger. A device +activity is explicitly indicated by calling ledtrig_dev_activity() for +a registered device. + +The driver also creates a set of debugfs entries under +/sys/kernel/debug/ledtrig-dev, these are: + + devices - cat'ing will produce a list of currently registered + devices + + register - echo'ing <major>:<minor> will create a trigger for this + device (note, you still need to add at least + ledtrig_dev_activity() hook) + + trigger - echo'ing <major>:<minor> will fire the trigger for this + device
Signature · 1 line
2.5.3