diff options
author | Milo Kim <milo.kim@ti.com> | 2013-08-08 01:11:29 -0400 |
---|---|---|
committer | Bryan Wu <cooloney@gmail.com> | 2013-08-26 20:22:13 -0400 |
commit | 863724a696e1a96b07c1bd0eb03cf08f10a714ba (patch) | |
tree | 0a4ad79c55d9262b9937e2aaa544bd02302a3e26 /Documentation/leds | |
parent | 2f733cad3699c6fd1cc3350ab43c9f684b976e73 (diff) |
Documentation: leds-lp5521,lp5523: update device attribute information
Now, all legacy application interfaces are restored.
Each driver documentation is updated.
Cc: Pali Rohár <pali.rohar@gmail.com>
Signed-off-by: Milo Kim <milo.kim@ti.com>
Signed-off-by: Bryan Wu <cooloney@gmail.com>
Diffstat (limited to 'Documentation/leds')
-rw-r--r-- | Documentation/leds/leds-lp5521.txt | 20 | ||||
-rw-r--r-- | Documentation/leds/leds-lp5523.txt | 21 |
2 files changed, 39 insertions, 2 deletions
diff --git a/Documentation/leds/leds-lp5521.txt b/Documentation/leds/leds-lp5521.txt index 79e4c2e6e5e8..d08d8c179f85 100644 --- a/Documentation/leds/leds-lp5521.txt +++ b/Documentation/leds/leds-lp5521.txt | |||
@@ -18,7 +18,25 @@ All three channels can be also controlled using the engine micro programs. | |||
18 | More details of the instructions can be found from the public data sheet. | 18 | More details of the instructions can be found from the public data sheet. |
19 | 19 | ||
20 | LP5521 has the internal program memory for running various LED patterns. | 20 | LP5521 has the internal program memory for running various LED patterns. |
21 | For the details, please refer to 'firmware' section in leds-lp55xx.txt | 21 | There are two ways to run LED patterns. |
22 | |||
23 | 1) Legacy interface - enginex_mode and enginex_load | ||
24 | Control interface for the engines: | ||
25 | x is 1 .. 3 | ||
26 | enginex_mode : disabled, load, run | ||
27 | enginex_load : store program (visible only in engine load mode) | ||
28 | |||
29 | Example (start to blink the channel 2 led): | ||
30 | cd /sys/class/leds/lp5521:channel2/device | ||
31 | echo "load" > engine3_mode | ||
32 | echo "037f4d0003ff6000" > engine3_load | ||
33 | echo "run" > engine3_mode | ||
34 | |||
35 | To stop the engine: | ||
36 | echo "disabled" > engine3_mode | ||
37 | |||
38 | 2) Firmware interface - LP55xx common interface | ||
39 | For the details, please refer to 'firmware' section in leds-lp55xx.txt | ||
22 | 40 | ||
23 | sysfs contains a selftest entry. | 41 | sysfs contains a selftest entry. |
24 | The test communicates with the chip and checks that | 42 | The test communicates with the chip and checks that |
diff --git a/Documentation/leds/leds-lp5523.txt b/Documentation/leds/leds-lp5523.txt index 899fdad509fe..5b3e91d4ac59 100644 --- a/Documentation/leds/leds-lp5523.txt +++ b/Documentation/leds/leds-lp5523.txt | |||
@@ -28,7 +28,26 @@ If both fields are NULL, 'lp5523' is used by default. | |||
28 | /sys/class/leds/lp5523:channelN (N: 0 ~ 8) | 28 | /sys/class/leds/lp5523:channelN (N: 0 ~ 8) |
29 | 29 | ||
30 | LP5523 has the internal program memory for running various LED patterns. | 30 | LP5523 has the internal program memory for running various LED patterns. |
31 | For the details, please refer to 'firmware' section in leds-lp55xx.txt | 31 | There are two ways to run LED patterns. |
32 | |||
33 | 1) Legacy interface - enginex_mode, enginex_load and enginex_leds | ||
34 | Control interface for the engines: | ||
35 | x is 1 .. 3 | ||
36 | enginex_mode : disabled, load, run | ||
37 | enginex_load : microcode load (visible only in load mode) | ||
38 | enginex_leds : led mux control (visible only in load mode) | ||
39 | |||
40 | cd /sys/class/leds/lp5523:channel2/device | ||
41 | echo "load" > engine3_mode | ||
42 | echo "9d80400004ff05ff437f0000" > engine3_load | ||
43 | echo "111111111" > engine3_leds | ||
44 | echo "run" > engine3_mode | ||
45 | |||
46 | To stop the engine: | ||
47 | echo "disabled" > engine3_mode | ||
48 | |||
49 | 2) Firmware interface - LP55xx common interface | ||
50 | For the details, please refer to 'firmware' section in leds-lp55xx.txt | ||
32 | 51 | ||
33 | Selftest uses always the current from the platform data. | 52 | Selftest uses always the current from the platform data. |
34 | 53 | ||