← Documents Documentation/leds/leds-lp55xx.rst GitHub 원문 ↗

Linux 6.18.37 · LEDs

LP55xx Common Driver

LP5521·LP5523·LP55231·LP5562·LP8501의 공통 구조, firmware와 predefined pattern interface입니다.

Source pathDocumentation/leds/leds-lp55xx.rst
Source versionLinux v6.18.37
TranslationDUJINLABS 전문 번역 + 해설

요약·해설과 원문, 전문 번역을 서로 분리했습니다. API 이름, symbol, source path는 원문 표기를 사용합니다.

1. 요약·해설

원문의 핵심 논리와 kernel programming 관점의 보충 설명입니다. 아래의 전문 번역과는 별도로 작성했습니다.

요약·해설

leds-lp55xx.rst:1-224

LP55xx 공통 driver는 I2C·LED class·sysfs·program memory를 공통화하고, register 차이는 device별 callback과 config에 맡깁니다.

Firmware loading을 닫는 순간 callback이 실행된다는 점과 `run_engine`이 별도 단계라는 점, predefined pattern이 platform data 번호로 선택된다는 점이 운용의 핵심입니다.

2. 영어 원문 전체

번역 기준이 된 Linux v6.18.37 원문입니다. 줄 번호는 이 버전의 파일 좌표입니다.

원문 전체 펼치기
1 =================================================
2 LP5521/LP5523/LP55231/LP5562/LP8501 Common Driver
3 =================================================
4
5 Authors: Milo(Woogyom) Kim <[email protected]>
6
7 Description
8 -----------
9 LP5521, LP5523/55231, LP5562 and LP8501 have common features as below.
10
11 Register access via the I2C
12 Device initialization/deinitialization
13 Create LED class devices for multiple output channels
14 Device attributes for user-space interface
15 Program memory for running LED patterns
16
17 The LP55xx common driver provides these features using exported functions.
18
19 lp55xx_init_device() / lp55xx_deinit_device()
20 lp55xx_register_leds() / lp55xx_unregister_leds()
21 lp55xx_regsister_sysfs() / lp55xx_unregister_sysfs()
22
23 ( Driver Structure Data )
24
25 In lp55xx common driver, two different data structure is used.
26
27 * lp55xx_led
28 control multi output LED channels such as led current, channel index.
29 * lp55xx_chip
30 general chip control such like the I2C and platform data.
31
32 For example, LP5521 has maximum 3 LED channels.
33 LP5523/55231 has 9 output channels::
34
35 lp55xx_chip for LP5521 ... lp55xx_led #1
36 lp55xx_led #2
37 lp55xx_led #3
38
39 lp55xx_chip for LP5523 ... lp55xx_led #1
40 lp55xx_led #2
41 .
42 .
43 lp55xx_led #9
44
45 ( Chip Dependent Code )
46
47 To support device specific configurations, special structure
48 'lpxx_device_config' is used.
49
50 - Maximum number of channels
51 - Reset command, chip enable command
52 - Chip specific initialization
53 - Brightness control register access
54 - Setting LED output current
55 - Program memory address access for running patterns
56 - Additional device specific attributes
57
58 ( Firmware Interface )
59
60 LP55xx family devices have the internal program memory for running
61 various LED patterns.
62
63 This pattern data is saved as a file in the user-land or
64 hex byte string is written into the memory through the I2C.
65
66 LP55xx common driver supports the firmware interface.
67
68 LP55xx chips have three program engines.
69
70 To load and run the pattern, the programming sequence is following.
71
72 (1) Select an engine number (1/2/3)
73 (2) Mode change to load
74 (3) Write pattern data into selected area
75 (4) Mode change to run
76
77 The LP55xx common driver provides simple interfaces as below.
78
79 select_engine:
80 Select which engine is used for running program
81 run_engine:
82 Start program which is loaded via the firmware interface
83 firmware:
84 Load program data
85
86 In case of LP5523, one more command is required, 'enginex_leds'.
87 It is used for selecting LED output(s) at each engine number.
88 In more details, please refer to 'leds-lp5523.txt'.
89
90 For example, run blinking pattern in engine #1 of LP5521::
91
92 echo 1 > /sys/bus/i2c/devices/xxxx/select_engine
93 echo 1 > /sys/class/firmware/lp5521/loading
94 echo "4000600040FF6000" > /sys/class/firmware/lp5521/data
95 echo 0 > /sys/class/firmware/lp5521/loading
96 echo 1 > /sys/bus/i2c/devices/xxxx/run_engine
97
98 For example, run blinking pattern in engine #3 of LP55231
99
100 Two LEDs are configured as pattern output channels::
101
102 echo 3 > /sys/bus/i2c/devices/xxxx/select_engine
103 echo 1 > /sys/class/firmware/lp55231/loading
104 echo "9d0740ff7e0040007e00a0010000" > /sys/class/firmware/lp55231/data
105 echo 0 > /sys/class/firmware/lp55231/loading
106 echo "000001100" > /sys/bus/i2c/devices/xxxx/engine3_leds
107 echo 1 > /sys/bus/i2c/devices/xxxx/run_engine
108
109 To start blinking patterns in engine #2 and #3 simultaneously::
110
111 for idx in 2 3
112 do
113 echo $idx > /sys/class/leds/red/device/select_engine
114 sleep 0.1
115 echo 1 > /sys/class/firmware/lp5521/loading
116 echo "4000600040FF6000" > /sys/class/firmware/lp5521/data
117 echo 0 > /sys/class/firmware/lp5521/loading
118 done
119 echo 1 > /sys/class/leds/red/device/run_engine
120
121 Here is another example for LP5523.
122
123 Full LED strings are selected by 'engine2_leds'::
124
125 echo 2 > /sys/bus/i2c/devices/xxxx/select_engine
126 echo 1 > /sys/class/firmware/lp5523/loading
127 echo "9d80400004ff05ff437f0000" > /sys/class/firmware/lp5523/data
128 echo 0 > /sys/class/firmware/lp5523/loading
129 echo "111111111" > /sys/bus/i2c/devices/xxxx/engine2_leds
130 echo 1 > /sys/bus/i2c/devices/xxxx/run_engine
131
132 As soon as 'loading' is set to 0, registered callback is called.
133 Inside the callback, the selected engine is loaded and memory is updated.
134 To run programmed pattern, 'run_engine' attribute should be enabled.
135
136 The pattern sequence of LP8501 is similar to LP5523.
137
138 However pattern data is specific.
139
140 Ex 1) Engine 1 is used::
141
142 echo 1 > /sys/bus/i2c/devices/xxxx/select_engine
143 echo 1 > /sys/class/firmware/lp8501/loading
144 echo "9d0140ff7e0040007e00a001c000" > /sys/class/firmware/lp8501/data
145 echo 0 > /sys/class/firmware/lp8501/loading
146 echo 1 > /sys/bus/i2c/devices/xxxx/run_engine
147
148 Ex 2) Engine 2 and 3 are used at the same time::
149
150 echo 2 > /sys/bus/i2c/devices/xxxx/select_engine
151 sleep 1
152 echo 1 > /sys/class/firmware/lp8501/loading
153 echo "9d0140ff7e0040007e00a001c000" > /sys/class/firmware/lp8501/data
154 echo 0 > /sys/class/firmware/lp8501/loading
155 sleep 1
156 echo 3 > /sys/bus/i2c/devices/xxxx/select_engine
157 sleep 1
158 echo 1 > /sys/class/firmware/lp8501/loading
159 echo "9d0340ff7e0040007e00a001c000" > /sys/class/firmware/lp8501/data
160 echo 0 > /sys/class/firmware/lp8501/loading
161 sleep 1
162 echo 1 > /sys/class/leds/d1/device/run_engine
163
164 ( 'run_engine' and 'firmware_cb' )
165
166 The sequence of running the program data is common.
167
168 But each device has own specific register addresses for commands.
169
170 To support this, 'run_engine' and 'firmware_cb' are configurable in each driver.
171
172 run_engine:
173 Control the selected engine
174 firmware_cb:
175 The callback function after loading the firmware is done.
176
177 Chip specific commands for loading and updating program memory.
178
179 ( Predefined pattern data )
180
181 Without the firmware interface, LP55xx driver provides another method for
182 loading a LED pattern. That is 'predefined' pattern.
183
184 A predefined pattern is defined in the platform data and load it(or them)
185 via the sysfs if needed.
186
187 To use the predefined pattern concept, 'patterns' and 'num_patterns' should be
188 configured.
189
190 Example of predefined pattern data::
191
192 /* mode_1: blinking data */
193 static const u8 mode_1[] = {
194 0x40, 0x00, 0x60, 0x00, 0x40, 0xFF, 0x60, 0x00,
195 };
196
197 /* mode_2: always on */
198 static const u8 mode_2[] = { 0x40, 0xFF, };
199
200 struct lp55xx_predef_pattern board_led_patterns[] = {
201 {
202 .r = mode_1,
203 .size_r = ARRAY_SIZE(mode_1),
204 },
205 {
206 .b = mode_2,
207 .size_b = ARRAY_SIZE(mode_2),
208 },
209 }
210
211 struct lp55xx_platform_data lp5562_pdata = {
212 ...
213 .patterns = board_led_patterns,
214 .num_patterns = ARRAY_SIZE(board_led_patterns),
215 };
216
217 Then, mode_1 and mode_2 can be run via through the sysfs::
218
219 echo 1 > /sys/bus/i2c/devices/xxxx/led_pattern # red blinking LED pattern
220 echo 2 > /sys/bus/i2c/devices/xxxx/led_pattern # blue LED always on
221
222 To stop running pattern::
223
224 echo 0 > /sys/bus/i2c/devices/xxxx/led_pattern
225

3. 한국어 전문 번역

영어 원문의 문단 순서와 의미를 유지한 전체 번역입니다. 코드, 함수명, symbol과 URL은 원문 표기를 유지합니다.

LP55xx 공통 기능과 driver 구조

1-57

이 공통 driver는 LP5521, LP5523/LP55231, LP5562, LP8501이 공유하는 I2C register 접근, device 초기화·해제, 다중 output LED class device 생성, userspace device attribute, pattern 실행용 program memory 기능을 제공합니다.

공개 함수는 `lp55xx_init_device()`와 `lp55xx_deinit_device()`, `lp55xx_register_leds()`와 `lp55xx_unregister_leds()`, 원문 표기의 `lp55xx_regsister_sysfs()`와 `lp55xx_unregister_sysfs()`입니다. 오탈자로 보이는 symbol도 원문 보존을 위해 그대로 둡니다.

공통 driver는 두 자료 구조를 사용합니다. `lp55xx_led`는 LED current와 channel index 같은 개별 output 채널을 나타내고, `lp55xx_chip`은 I2C와 platform data 같은 chip 전체 제어 상태를 나타냅니다. LP5521의 chip 하나에는 최대 세 `lp55xx_led`, LP5523/55231에는 아홉 개가 연결됩니다.

Device별 차이는 원문 표기의 `lpxx_device_config`에 둡니다. 최대 채널 수, reset·enable 명령, chip별 초기화, brightness register 접근, output current 설정, pattern program memory 주소, 추가 attribute가 여기에 포함됩니다.

LP55xx driver 자료 구조
구조 또는 config범위주요 책임
`lp55xx_chip`Chip당 1개I2C와 platform data, 전체 제어
`lp55xx_led`Output 채널당 1개LED current와 channel index
`lpxx_device_config`Chip 종류별Register·초기화·memory·추가 attribute

Chip 공통 상태와 채널별 상태를 분리하고 device config로 차이를 주입합니다.

=================================================
LP5521/LP5523/LP55231/LP5562/LP8501 Common Driver
=================================================

Authors: Milo(Woogyom) Kim <[email protected]>

Description
-----------
LP5521, LP5523/55231, LP5562 and LP8501 have common features as below.

  Register access via the I2C
  Device initialization/deinitialization
  Create LED class devices for multiple output channels
  Device attributes for user-space interface
  Program memory for running LED patterns

The LP55xx common driver provides these features using exported functions.

  lp55xx_init_device() / lp55xx_deinit_device()
  lp55xx_register_leds() / lp55xx_unregister_leds()
  lp55xx_regsister_sysfs() / lp55xx_unregister_sysfs()

( Driver Structure Data )

In lp55xx common driver, two different data structure is used.

* lp55xx_led
    control multi output LED channels such as led current, channel index.
* lp55xx_chip
    general chip control such like the I2C and platform data.

For example, LP5521 has maximum 3 LED channels.
LP5523/55231 has 9 output channels::

  lp55xx_chip for LP5521 ... lp55xx_led #1
                             lp55xx_led #2
                             lp55xx_led #3

  lp55xx_chip for LP5523 ... lp55xx_led #1
                             lp55xx_led #2
                                   .
                                   .
                             lp55xx_led #9

( Chip Dependent Code )

To support device specific configurations, special structure
'lpxx_device_config' is used.

  - Maximum number of channels
  - Reset command, chip enable command
  - Chip specific initialization
  - Brightness control register access
  - Setting LED output current
  - Program memory address access for running patterns
  - Additional device specific attributes

공통 firmware interface

58-89

LP55xx 계열은 다양한 LED pattern을 실행할 내부 program memory와 세 개의 program engine을 갖습니다. Pattern data는 userspace file로 저장하거나 I2C를 통해 hex byte string으로 memory에 기록할 수 있습니다.

적재와 실행의 공통 순서는 engine 1·2·3 중 하나를 선택하고, mode를 load로 바꾸고, 선택 영역에 pattern data를 쓴 다음, mode를 run으로 바꾸는 것입니다.

공통 interface의 `select_engine`은 실행할 engine을 선택하고, `run_engine`은 firmware interface로 적재한 program을 시작하며, `firmware`는 program data를 적재합니다.

LP5523은 engine별 output을 선택하는 `enginex_leds` 명령이 하나 더 필요합니다. 세부 설명은 원문이 가리키는 `leds-lp5523.txt`에 있습니다.

LP55xx 공통 program lifecycle
Engine 번호 1·2·3 중 하나 선택선택한 engine을 load mode로 전환Program memory의 선택 영역에 pattern data 기록Engine을 run mode로 전환

모든 지원 chip이 공유하는 네 단계입니다.

( Firmware Interface )

LP55xx family devices have the internal program memory for running
various LED patterns.

This pattern data is saved as a file in the user-land or
hex byte string is written into the memory through the I2C.

LP55xx common driver supports the firmware interface.

LP55xx chips have three program engines.

To load and run the pattern, the programming sequence is following.

  (1) Select an engine number (1/2/3)
  (2) Mode change to load
  (3) Write pattern data into selected area
  (4) Mode change to run

The LP55xx common driver provides simple interfaces as below.

select_engine:
        Select which engine is used for running program
run_engine:
        Start program which is loaded via the firmware interface
firmware:
        Load program data

In case of LP5523, one more command is required, 'enginex_leds'.
It is used for selecting LED output(s) at each engine number.
In more details, please refer to 'leds-lp5523.txt'.

LP5521·LP55231·LP5523 적재 예제

90-134

LP5521 engine 1 blink 예제는 `select_engine = 1`, firmware `loading = 1`, data `4000600040FF6000`, `loading = 0`, `run_engine = 1` 순서입니다.

LP55231 engine 3 예제는 `9d0740ff7e0040007e00a0010000`을 적재한 뒤 `engine3_leds`에 `000001100`을 써서 두 LED를 output channel로 선택합니다.

LP5521의 engine 2와 3을 동시에 준비하는 shell loop는 각 engine을 차례로 선택하고 0.1초 기다린 뒤 같은 blink data를 적재합니다. 두 engine의 적재가 끝나면 `run_engine`을 한 번 활성화합니다.

LP5523 예제는 engine 2를 선택하고 `9d80400004ff05ff437f0000`을 적재한 뒤 `engine2_leds`에 `111111111`을 써서 아홉 LED 전체를 선택합니다.

Firmware `loading`을 `0`으로 바꾸는 즉시 등록된 callback이 호출되어 선택 engine과 program memory를 갱신합니다. 실제 pattern을 시작하려면 이어서 `run_engine` attribute를 활성화해야 합니다.

LP55xx firmware 예제 차이
ChipEngineProgram data추가 output 선택
LP55211`4000600040FF6000`없음
LP552313`9d0740ff7e0040007e00a0010000``engine3_leds = 000001100`
LP55232`9d80400004ff05ff437f0000``engine2_leds = 111111111`

공통 loading 절차에 chip별 data와 LED mux 단계가 더해집니다.

For example, run blinking pattern in engine #1 of LP5521::

        echo 1 > /sys/bus/i2c/devices/xxxx/select_engine
        echo 1 > /sys/class/firmware/lp5521/loading
        echo "4000600040FF6000" > /sys/class/firmware/lp5521/data
        echo 0 > /sys/class/firmware/lp5521/loading
        echo 1 > /sys/bus/i2c/devices/xxxx/run_engine

For example, run blinking pattern in engine #3 of LP55231

Two LEDs are configured as pattern output channels::

        echo 3 > /sys/bus/i2c/devices/xxxx/select_engine
        echo 1 > /sys/class/firmware/lp55231/loading
        echo "9d0740ff7e0040007e00a0010000" > /sys/class/firmware/lp55231/data
        echo 0 > /sys/class/firmware/lp55231/loading
        echo "000001100" > /sys/bus/i2c/devices/xxxx/engine3_leds
        echo 1 > /sys/bus/i2c/devices/xxxx/run_engine

To start blinking patterns in engine #2 and #3 simultaneously::

        for idx in 2 3
        do
        echo $idx > /sys/class/leds/red/device/select_engine
        sleep 0.1
        echo 1 > /sys/class/firmware/lp5521/loading
        echo "4000600040FF6000" > /sys/class/firmware/lp5521/data
        echo 0 > /sys/class/firmware/lp5521/loading
        done
        echo 1 > /sys/class/leds/red/device/run_engine

Here is another example for LP5523.

Full LED strings are selected by 'engine2_leds'::

        echo 2 > /sys/bus/i2c/devices/xxxx/select_engine
        echo 1 > /sys/class/firmware/lp5523/loading
        echo "9d80400004ff05ff437f0000" > /sys/class/firmware/lp5523/data
        echo 0 > /sys/class/firmware/lp5523/loading
        echo "111111111" > /sys/bus/i2c/devices/xxxx/engine2_leds
        echo 1 > /sys/bus/i2c/devices/xxxx/run_engine

As soon as 'loading' is set to 0, registered callback is called.
Inside the callback, the selected engine is loaded and memory is updated.
To run programmed pattern, 'run_engine' attribute should be enabled.

LP8501 예제와 device별 callback

135-178

LP8501의 pattern sequence는 LP5523과 비슷하지만 program data는 device별입니다. Engine 1 예제는 `9d0140ff7e0040007e00a001c000`을 적재합니다.

Engine 2와 3을 함께 사용할 때는 engine 2에 `9d0140ff7e0040007e00a001c000`, engine 3에 `9d0340ff7e0040007e00a001c000`을 각각 적재하며 단계 사이에 1초씩 기다립니다. 마지막에는 `/sys/class/leds/d1/device/run_engine`을 활성화합니다.

Program 실행 순서는 공통이지만 명령 register 주소는 device마다 다릅니다. 이를 지원하기 위해 각 driver가 `run_engine`과 `firmware_cb`를 구성합니다.

`run_engine` callback은 선택 engine을 제어합니다. `firmware_cb`는 firmware loading 완료 뒤 호출되어 chip별 명령으로 program memory를 적재하고 갱신합니다.

Firmware 완료 callback
Userspace가 firmware `loading`을 `0`으로 전환공통 driver가 등록된 `firmware_cb` 호출Chip별 callback이 선택 engine의 program memory 갱신Userspace가 `run_engine`을 활성화Device별 `run_engine` callback이 실제 engine 시작

공통 interface와 chip별 register 처리가 만나는 지점입니다.


The pattern sequence of LP8501 is similar to LP5523.

However pattern data is specific.

Ex 1) Engine 1 is used::

        echo 1 > /sys/bus/i2c/devices/xxxx/select_engine
        echo 1 > /sys/class/firmware/lp8501/loading
        echo "9d0140ff7e0040007e00a001c000" > /sys/class/firmware/lp8501/data
        echo 0 > /sys/class/firmware/lp8501/loading
        echo 1 > /sys/bus/i2c/devices/xxxx/run_engine

Ex 2) Engine 2 and 3 are used at the same time::

        echo 2 > /sys/bus/i2c/devices/xxxx/select_engine
        sleep 1
        echo 1 > /sys/class/firmware/lp8501/loading
        echo "9d0140ff7e0040007e00a001c000" > /sys/class/firmware/lp8501/data
        echo 0 > /sys/class/firmware/lp8501/loading
        sleep 1
        echo 3 > /sys/bus/i2c/devices/xxxx/select_engine
        sleep 1
        echo 1 > /sys/class/firmware/lp8501/loading
        echo "9d0340ff7e0040007e00a001c000" > /sys/class/firmware/lp8501/data
        echo 0 > /sys/class/firmware/lp8501/loading
        sleep 1
        echo 1 > /sys/class/leds/d1/device/run_engine

( 'run_engine' and 'firmware_cb' )

The sequence of running the program data is common.

But each device has own specific register addresses for commands.

To support this, 'run_engine' and 'firmware_cb' are configurable in each driver.

run_engine:
        Control the selected engine
firmware_cb:
        The callback function after loading the firmware is done.

        Chip specific commands for loading and updating program memory.

Platform data의 predefined pattern

179-224

Firmware interface 외에도 LP55xx driver는 platform data에 미리 정의한 LED pattern을 sysfs에서 선택해 적재하는 `predefined` 방식을 제공합니다.

이 방식을 사용하려면 platform data의 `patterns`와 `num_patterns`를 구성해야 합니다. 예제의 `mode_1`은 `0x40, 0x00, 0x60, 0x00, 0x40, 0xFF, 0x60, 0x00` blink data이고, `mode_2`는 `0x40, 0xFF` always-on data입니다.

`lp55xx_predef_pattern` 배열 첫 항목은 `mode_1`을 red program과 크기에 연결하고, 둘째 항목은 `mode_2`를 blue program과 크기에 연결합니다. `lp5562_pdata`는 이 배열과 `ARRAY_SIZE(board_led_patterns)`를 보관합니다.

Sysfs `led_pattern`에 `1`을 쓰면 red blink인 mode 1, `2`를 쓰면 blue always-on인 mode 2가 실행됩니다. 실행 중인 pattern을 중지하려면 `0`을 씁니다.

Predefined pattern 선택
`mode_1`, `mode_2` byte array 정의`lp55xx_predef_pattern`에서 색상별 data와 크기 연결`patterns`와 `num_patterns`를 platform data에 등록`led_pattern = 1` 또는 `2`로 선택 실행`led_pattern = 0`으로 중지

Board가 compile time에 제공한 pattern을 번호로 실행합니다.

( Predefined pattern data )

Without the firmware interface, LP55xx driver provides another method for
loading a LED pattern. That is 'predefined' pattern.

A predefined pattern is defined in the platform data and load it(or them)
via the sysfs if needed.

To use the predefined pattern concept, 'patterns' and 'num_patterns' should be
configured.

Example of predefined pattern data::

  /* mode_1: blinking data */
  static const u8 mode_1[] = {
                0x40, 0x00, 0x60, 0x00, 0x40, 0xFF, 0x60, 0x00,
                };

  /* mode_2: always on */
  static const u8 mode_2[] = { 0x40, 0xFF, };

  struct lp55xx_predef_pattern board_led_patterns[] = {
        {
                .r = mode_1,
                .size_r = ARRAY_SIZE(mode_1),
        },
        {
                .b = mode_2,
                .size_b = ARRAY_SIZE(mode_2),
        },
  }

  struct lp55xx_platform_data lp5562_pdata = {
  ...
        .patterns      = board_led_patterns,
        .num_patterns  = ARRAY_SIZE(board_led_patterns),
  };

Then, mode_1 and mode_2 can be run via through the sysfs::

  echo 1 > /sys/bus/i2c/devices/xxxx/led_pattern    # red blinking LED pattern
  echo 2 > /sys/bus/i2c/devices/xxxx/led_pattern    # blue LED always on

To stop running pattern::

  echo 0 > /sys/bus/i2c/devices/xxxx/led_pattern