Bug 52981 - led framework cannot handle more triggers than leds
Summary: led framework cannot handle more triggers than leds
Status: NEW
Alias: None
Product: Drivers
Classification: Unclassified
Component: Other (show other bugs)
Hardware: All Linux
: P1 enhancement
Assignee: drivers_other
URL:
Keywords:
Depends on:
Blocks:
 
Reported: 2013-01-24 14:26 UTC by Michal Suchanek
Modified: 2013-06-12 09:41 UTC (History)
3 users (show)

See Also:
Kernel Version: 3.4.19 .. master
Subsystem:
Regression: No
Bisected commit-id:


Attachments

Description Michal Suchanek 2013-01-24 14:26:07 UTC
The file Documentation/leds/leds-class.txt provides no hint whatsoever about the use of the leds neither from userspace nor from kernel drivers that would like to implement triggers.

Presumably the reason to implement this framework to prevent everybody implementing a led driver hiding the feature in some obscure corner of the kernel.

Now some leds features are unified in this framework but what use is that without any docs?
Comment 1 Michal Suchanek 2013-01-24 15:46:01 UTC
Well, maybe all the features that can be used are documented and are just insufficeint. At least the features usable with the current userspace interface.

There is just no way to use the LED framework in the situation when you have 4 disks and 1 led.
Comment 2 Michal Suchanek 2013-06-12 09:41:36 UTC
I looked at the led framework closely and it's not lack of documentation. The led framework just does not have code that would allow using a led as disk led when you have more than one disk controller.

Note You need to log in before you can comment on or make changes to this bug.