On Thu, Jan 10, 2019 at 02:05:57PM -0600, Doug Zobel wrote:
Driver for the TI LP5562 4 channel LED controller. Supports independent on/off control of all 4 channels. Supports LED_BLINK on 3 independent channels: blue/green/red. The white channel can blink, but shares the blue channel blink rate.
doc/device-tree-bindings/leds/leds-lp5562.txt | 61 +++ drivers/led/Kconfig | 8 + drivers/led/Makefile | 1 + drivers/led/led_lp5562.c | 571 ++++++++++++++++++++++++++ 4 files changed, 641 insertions(+) create mode 100644 doc/device-tree-bindings/leds/leds-lp5562.txt create mode 100644 drivers/led/led_lp5562.c
diff --git a/doc/device-tree-bindings/leds/leds-lp5562.txt b/doc/device-tree-bindings/leds/leds-lp5562.txt new file mode 100644 index 0000000..d6e3192 --- /dev/null +++ b/doc/device-tree-bindings/leds/leds-lp5562.txt @@ -0,0 +1,61 @@ +LEDs connected to TI LP5562 controller
+This driver works with a TI LP5562 4-channel LED controller. +CONFIG_LED_BLINK is supported using the controller engines. However +there are only 3 engines available for the 4 channels. This means +that the blue and white channels share the same engine. When both +blue and white LEDs are set to blink, they will share the same blink +rate. Changing the blink rate of the blue LED will affect the white +LED and vice-versa. Manual on/off is handled independtly for all +4 channels.
My biggest concern here is that in Linux this is handled via bindings/leds/leds-lp55xx.txt with an entirely different compatible and so forth. Since the general goal is to be able to share trees and bindings, can you rework things with that binding instead? Thanks!