summaryrefslogtreecommitdiff
path: root/Documentation/leds-class.txt
diff options
context:
space:
mode:
authorLen Brown <len.brown@intel.com>2009-09-19 09:55:27 +0400
committerLen Brown <len.brown@intel.com>2009-09-19 09:55:27 +0400
commitb4549a24b6194201077d0295207ec204f785fab1 (patch)
treed290a7868f12a1b62aba0449f6c693dd0ff91130 /Documentation/leds-class.txt
parent3bb29ec14ce5f448ab37a5da16c3d720ae5af9cf (diff)
parent52cc96bd5b61775db2792780c610979fc02313eb (diff)
downloadlinux-b4549a24b6194201077d0295207ec204f785fab1.tar.xz
Merge branch 'asus' into release
Diffstat (limited to 'Documentation/leds-class.txt')
-rw-r--r--Documentation/leds-class.txt9
1 files changed, 5 insertions, 4 deletions
diff --git a/Documentation/leds-class.txt b/Documentation/leds-class.txt
index 6399557cdab3..8fd5ca2ae32d 100644
--- a/Documentation/leds-class.txt
+++ b/Documentation/leds-class.txt
@@ -1,3 +1,4 @@
+
LED handling under Linux
========================
@@ -5,10 +6,10 @@ If you're reading this and thinking about keyboard leds, these are
handled by the input subsystem and the led class is *not* needed.
In its simplest form, the LED class just allows control of LEDs from
-userspace. LEDs appear in /sys/class/leds/. The brightness file will
-set the brightness of the LED (taking a value 0-255). Most LEDs don't
-have hardware brightness support so will just be turned on for non-zero
-brightness settings.
+userspace. LEDs appear in /sys/class/leds/. The maximum brightness of the
+LED is defined in max_brightness file. The brightness file will set the brightness
+of the LED (taking a value 0-max_brightness). Most LEDs don't have hardware
+brightness support so will just be turned on for non-zero brightness settings.
The class also introduces the optional concept of an LED trigger. A trigger
is a kernel based source of led events. Triggers can either be simple or