-
Notifications
You must be signed in to change notification settings - Fork 0
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
Merge branch 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/…
…git/cooloney/linux-leds Pull LED subsystem updates from Bryan Wu: - lp55xx device tree updates - mc13xxx driver updates - some clean up * 'for-next' of git://git.kernel.org/pub/scm/linux/kernel/git/cooloney/linux-leds: leds: mc13783: Fix "uninitialized variable" warning leds: Convert led class driver from legacy pm ops to dev_pm_ops leds: leds-mc13783: Add MC13892 LED support leds: leds-mc13783: Prepare driver to support MC13892 LEDs leds: renesas-tpu: cleanup a small type issue leds: use platform_{get,set}_drvdata() leds: leds-gpio: Let device core handle pinctrl leds: lp5562: Properly setup of_device_id table leds: lp5523: Properly setup of_device_id table leds: lp5521: Properly setup of_device_id table leds: lp5562: support the device tree feature leds: lp55xx: support dynamic channel settings in the device tree structure leds: leds-ns2: remove unnecessary platform_set_drvdata() leds: leds-mc13783: remove unnecessary platform_set_drvdata() leds: leds-gpio: remove unnecessary platform_set_drvdata() leds: atmel-pwm: remove unnecessary platform_set_drvdata() leds: lp55xx: add support for Device Tree bindings
- Loading branch information
Showing
18 changed files
with
553 additions
and
346 deletions.
There are no files selected for viewing
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -0,0 +1,147 @@ | ||
Binding for TI/National Semiconductor LP55xx Led Drivers | ||
|
||
Required properties: | ||
- compatible: "national,lp5521" or "national,lp5523" or "ti,lp5562" | ||
- reg: I2C slave address | ||
- clock-mode: Input clock mode, (0: automode, 1: internal, 2: external) | ||
|
||
Each child has own specific current settings | ||
- led-cur: Current setting at each led channel (mA x10, 0 if led is not connected) | ||
- max-cur: Maximun current at each led channel. | ||
|
||
Optional properties: | ||
- label: Used for naming LEDs | ||
|
||
Alternatively, each child can have specific channel name | ||
- chan-name: Name of each channel name | ||
|
||
example 1) LP5521 | ||
3 LED channels, external clock used. Channel names are 'lp5521_pri:channel0', | ||
'lp5521_pri:channel1' and 'lp5521_pri:channel2' | ||
|
||
lp5521@32 { | ||
compatible = "national,lp5521"; | ||
reg = <0x32>; | ||
label = "lp5521_pri"; | ||
clock-mode = /bits/ 8 <2>; | ||
|
||
chan0 { | ||
led-cur = /bits/ 8 <0x2f>; | ||
max-cur = /bits/ 8 <0x5f>; | ||
}; | ||
|
||
chan1 { | ||
led-cur = /bits/ 8 <0x2f>; | ||
max-cur = /bits/ 8 <0x5f>; | ||
}; | ||
|
||
chan2 { | ||
led-cur = /bits/ 8 <0x2f>; | ||
max-cur = /bits/ 8 <0x5f>; | ||
}; | ||
}; | ||
|
||
example 2) LP5523 | ||
9 LED channels with specific name. Internal clock used. | ||
The I2C slave address is configurable with ASEL1 and ASEL0 pins. | ||
Available addresses are 32/33/34/35h. | ||
|
||
ASEL1 ASEL0 Address | ||
------------------------- | ||
GND GND 32h | ||
GND VEN 33h | ||
VEN GND 34h | ||
VEN VEN 35h | ||
|
||
lp5523@32 { | ||
compatible = "national,lp5523"; | ||
reg = <0x32>; | ||
clock-mode = /bits/ 8 <1>; | ||
|
||
chan0 { | ||
chan-name = "d1"; | ||
led-cur = /bits/ 8 <0x14>; | ||
max-cur = /bits/ 8 <0x20>; | ||
}; | ||
|
||
chan1 { | ||
chan-name = "d2"; | ||
led-cur = /bits/ 8 <0x14>; | ||
max-cur = /bits/ 8 <0x20>; | ||
}; | ||
|
||
chan2 { | ||
chan-name = "d3"; | ||
led-cur = /bits/ 8 <0x14>; | ||
max-cur = /bits/ 8 <0x20>; | ||
}; | ||
|
||
chan3 { | ||
chan-name = "d4"; | ||
led-cur = /bits/ 8 <0x14>; | ||
max-cur = /bits/ 8 <0x20>; | ||
}; | ||
|
||
chan4 { | ||
chan-name = "d5"; | ||
led-cur = /bits/ 8 <0x14>; | ||
max-cur = /bits/ 8 <0x20>; | ||
}; | ||
|
||
chan5 { | ||
chan-name = "d6"; | ||
led-cur = /bits/ 8 <0x14>; | ||
max-cur = /bits/ 8 <0x20>; | ||
}; | ||
|
||
chan6 { | ||
chan-name = "d7"; | ||
led-cur = /bits/ 8 <0x14>; | ||
max-cur = /bits/ 8 <0x20>; | ||
}; | ||
|
||
chan7 { | ||
chan-name = "d8"; | ||
led-cur = /bits/ 8 <0x14>; | ||
max-cur = /bits/ 8 <0x20>; | ||
}; | ||
|
||
chan8 { | ||
chan-name = "d9"; | ||
led-cur = /bits/ 8 <0x14>; | ||
max-cur = /bits/ 8 <0x20>; | ||
}; | ||
}; | ||
|
||
example 3) LP5562 | ||
4 channels are defined. | ||
|
||
lp5562@30 { | ||
compatible = "ti,lp5562"; | ||
reg = <0x30>; | ||
clock-mode = /bits/8 <2>; | ||
|
||
chan0 { | ||
chan-name = "R"; | ||
led-cur = /bits/ 8 <0x20>; | ||
max-cur = /bits/ 8 <0x60>; | ||
}; | ||
|
||
chan1 { | ||
chan-name = "G"; | ||
led-cur = /bits/ 8 <0x20>; | ||
max-cur = /bits/ 8 <0x60>; | ||
}; | ||
|
||
chan2 { | ||
chan-name = "B"; | ||
led-cur = /bits/ 8 <0x20>; | ||
max-cur = /bits/ 8 <0x60>; | ||
}; | ||
|
||
chan3 { | ||
chan-name = "W"; | ||
led-cur = /bits/ 8 <0x20>; | ||
max-cur = /bits/ 8 <0x60>; | ||
}; | ||
}; |
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Oops, something went wrong.