Multicolor Framework v13
Subsystems (4)
v13 cover Multicolor Framework v13
Hello
Changes from v12:
https://lore.kernel.org/patchwork/project/lkml/list/?series=413816
Add 2 patches per request.
- Updated LP55xx dt binding to LED node naming convention [18/18]
- Update LP55xx-common to use devm_* for LED class registration [12/18]
Removed the dt binding changes from the 4/18 back into 1/18
MC Framework
- Removed inline functions from the header due to not being able to build the code as a module as ifdef was not set giving a redefinition issue when the module was being created.
LP55xx/23/21
- Renamed intensity_fn to multicolor_brightness_fn
- Call the devm_multicolor class registration
LP50xx
- Call the devm_multicolor class registration
Dan
Dan Murphy (18):
dt: bindings: Add multicolor class dt bindings documention
dt-bindings: leds: Add multicolor ID to the color ID list
leds: Add multicolor ID to the color ID list
leds: multicolor: Introduce a multicolor class definition
dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers
leds: lp50xx: Add the LP50XX family of the RGB LED driver
dt: bindings: lp55xx: Be consistent in the document with LED acronym
dt: bindings: lp55xx: Update binding for Multicolor Framework
ARM: dts: n900: Add reg property to the LP5523 channel node
ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 channel node
ARM: dts: ste-href: Add reg property to the LP5521 channel nodes
leds: lp55xx: Convert LED class registration to devm_*
leds: lp55xx: Add multicolor framework support to lp55xx
leds: lp5523: Update the lp5523 code to add multicolor brightness
function
leds: lp5521: Add multicolor framework multicolor brightness support
leds: lp55xx: Fix checkpatch file permissions issues
leds: lp5523: Fix checkpatch issues in the code
dt: bindings: Update lp55xx binding to recommended LED naming
.../ABI/testing/sysfs-class-led-multicolor | 36 + .../bindings/leds/leds-class-multicolor.txt | 98 +++ .../devicetree/bindings/leds/leds-lp50xx.txt | 148 ++++ .../devicetree/bindings/leds/leds-lp55xx.txt | 163 +++- Documentation/leds/index.rst | 1 + Documentation/leds/leds-class-multicolor.rst | 96 +++ arch/arm/boot/dts/imx6dl-yapp4-common.dtsi | 14 +- arch/arm/boot/dts/omap3-n900.dts | 29 +- arch/arm/boot/dts/ste-href.dtsi | 22 +- drivers/leds/Kconfig | 23 + drivers/leds/Makefile | 2 + drivers/leds/led-class-multicolor.c | 271 ++++++ drivers/leds/led-core.c | 1 + drivers/leds/leds-lp50xx.c | 799 ++++++++++++++++++ drivers/leds/leds-lp5521.c | 20 + drivers/leds/leds-lp5523.c | 39 +- drivers/leds/leds-lp55xx-common.c | 199 ++++- drivers/leds/leds-lp55xx-common.h | 9 + include/dt-bindings/leds/common.h | 3 +- include/linux/led-class-multicolor.h | 97 +++ include/linux/platform_data/leds-lp55xx.h | 7 + 21 files changed, 1980 insertions(+), 97 deletions(-) create mode 100644 Documentation/ABI/testing/sysfs-class-led-multicolor create mode 100644 Documentation/devicetree/bindings/leds/leds-class-multicolor.txt create mode 100644 Documentation/devicetree/bindings/leds/leds-lp50xx.txt create mode 100644 Documentation/leds/leds-class-multicolor.rst create mode 100644 drivers/leds/led-class-multicolor.c create mode 100644 drivers/leds/leds-lp50xx.c create mode 100644 include/linux/led-class-multicolor.h
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 1/18 dt: bindings: Add multicolor class dt bindings documention
Add DT bindings for the LEDs multicolor class framework.
--- .../bindings/leds/leds-class-multicolor.txt | 98 +++++++++++++++++++ 1 file changed, 98 insertions(+) create mode 100644 Documentation/devicetree/bindings/leds/leds-class-multicolor.txt
Documentation/devicetree/bindings/leds/leds-class-multicolor.txt new file +98 -0
@@ -0,0 +1,98 @@ +* Multicolor LED properties + +Bindings for multi color LEDs show how to describe current outputs of +either integrated multi-color LED elements (like RGB, RGBW, RGBWA-UV +etc.) or standalone LEDs, to achieve logically grouped multi-color LED +modules. This is achieved by adding multi-led nodes layer to the +monochrome LED bindings. + +The nodes and properties defined in this document are unique to the multicolor +LED class. Common LED nodes and properties are inherited from the common.txt +within this documentation directory. + +Required LED child properties: + - color : For multicolor LED support this property should be defined as + LED_COLOR_ID_MULTI and further definition can be found in + include/linux/leds/common.h. + +led-controller@30 { + #address-cells = <1>; + #size-cells = <0>; + compatible = "ti,lp5024"; + reg = <0x29>; + + multi-led@1 { + #address-cells = <1>; + #size-cells = <0>; + reg = <1>; + color = <LED_COLOR_ID_MULTI>; + function = LED_FUNCTION_CHARGING; + + + led@3 { + reg = <3>; + color = <LED_COLOR_ID_RED>; + }; + + led@4 { + reg = <4>; + color = <LED_COLOR_ID_GREEN>; + }; + + led@5 { + reg = <5>; + color = <LED_COLOR_ID_BLUE>; + }; + }; + + multi-led@2 { + #address-cells = <1>; + #size-cells = <0>; + color = <LED_COLOR_ID_MULTI>; + function = LED_FUNCTION_ACTIVITY; + reg = <2>; + ti,led-bank = <2 3 5>; + + led@6 { + reg = <0x6>; + color = <LED_COLOR_ID_RED>; + led-sources = <6 9 15>; + }; + + led@7 { + reg = <0x7>; + color = <LED_COLOR_ID_GREEN>; + led-sources = <7 10 16>; + }; + + led@8 { + reg = <0x8>; + color = <LED_COLOR_ID_BLUE>; + led-sources = <8 11 17>; + }; + }; + + multi-led@4 { + #address-cells = <1>; + #size-cells = <0>; + reg = <4>; + color = <LED_COLOR_ID_MULTI>; + function = LED_FUNCTION_ACTIVITY; + + led@12 { + reg = <12>; + color = <LED_COLOR_ID_RED>; + }; + + led@13 { + reg = <13>; + color = <LED_COLOR_ID_GREEN>; + }; + + led@14 { + reg = <14>; + color = <LED_COLOR_ID_BLUE>; + }; + }; + +};
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 2/18 dt-bindings: leds: Add multicolor ID to the color ID list
In reply to Dan MurphyAdd a new color ID that is declared as MULTICOLOR as with the multicolor framework declaring a definitive color is not accurate as the node can contain multiple colors.
--- include/dt-bindings/leds/common.h | 3 ++- 1 file changed, 2 insertions(+), 1 deletion(-)
include/dt-bindings/leds/common.h +2 -1
@@ -29,7 +29,8 @@#define LED_COLOR_ID_VIOLET 5#define LED_COLOR_ID_YELLOW 6#define LED_COLOR_ID_IR 7 -#define LED_COLOR_ID_MAX 8 +#define LED_COLOR_ID_MULTI 8 +#define LED_COLOR_ID_MAX 9/* Standard LED functions */ #define LED_FUNCTION_ACTIVITY "activity"
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 3/18 leds: Add multicolor ID to the color ID list
In reply to Dan MurphyAdd a new color ID that is declared as MULTICOLOR as with the multicolor framework declaring a definitive color is not accurate as the node can contain multiple colors.
--- drivers/leds/led-core.c | 1 + 1 file changed, 1 insertion(+)
drivers/leds/led-core.c +1 -0
@@ -34,6 +34,7 @@ const char * const led_colors[LED_COLOR_ID_MAX] = { [LED_COLOR_ID_VIOLET] = "violet", [LED_COLOR_ID_YELLOW] = "yellow", [LED_COLOR_ID_IR] = "ir", + [LED_COLOR_ID_MULTI ] ="multicolor" , };EXPORT_SYMBOL_GPL (led_colors);
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 4/18 leds: multicolor: Introduce a multicolor class definition
In reply to Dan MurphyIntroduce a multicolor class that groups colored LEDs within a LED node.
The multi color class groups monochrome LEDs and allows controlling two aspects of the final combined color: hue and lightness. The former is controlled via <color>_intensity files and the latter is controlled via brightness file.
--- .../ABI/testing/sysfs-class-led-multicolor | 36 +++ Documentation/leds/index.rst | 1 + Documentation/leds/leds-class-multicolor.rst | 96 +++++++ drivers/leds/Kconfig | 10 + drivers/leds/Makefile | 1 + drivers/leds/led-class-multicolor.c | 271 ++++++++++++++++++ include/linux/led-class-multicolor.h | 97 +++++++ 7 files changed, 512 insertions(+) create mode 100644 Documentation/ABI/testing/sysfs-class-led-multicolor create mode 100644 Documentation/leds/leds-class-multicolor.rst create mode 100644 drivers/leds/led-class-multicolor.c create mode 100644 include/linux/led-class-multicolor.h
Documentation/ABI/testing/sysfs-class-led-multicolor new file +36 -0
@@ -0,0 +1,36 @@ +What: /sys/class/leds/<led>/brightness +Date: Sept 2019 +KernelVersion: 5.5 +Contact: Dan Murphy <[email protected]> +Description: read/write + Writing to this file will update all LEDs within the group to a + calculated percentage of what each color LED intensity is set + to. The percentage is calculated for each grouped LED via the + equation below: + + led_brightness = brightness * <color>_intensity/<color>_max_intensity + + For additional details please refer to + Documentation/leds/leds-class-multicolor.rst. + + The value of the color is from 0 to + /sys/class/leds/<led>/max_brightness. + +What: /sys/class/leds/<led>/colors/<color>_intensity +Date: Sept 2019 +KernelVersion: 5.5 +Contact: Dan Murphy <[email protected]> +Description: read/write + The <color>_intensity file is created based on the color + defined by the registrar of the class. + There is one file per color presented. + + The value of the color is from 0 to + /sys/class/leds/<led>/colors/<color>_max_intensity. + +What: /sys/class/leds/<led>/colors/<color>_max_intensity +Date: Sept 2019 +KernelVersion: 5.5 +Contact: Dan Murphy <[email protected]> +Description: read only + Maximum intensity level for the LED color.
Documentation/leds/index.rst +1 -0
@@ -9,6 +9,7 @@ LEDs leds-class leds-class-flash + leds-class-multicolor ledtrig-oneshot ledtrig-transient ledtrig-usbport
Documentation/leds/leds-class-multicolor.rst new file +96 -0
96 lines not on this page · raw message
drivers/leds/Kconfig +10 -0
@@ -30,6 +30,16 @@ config LEDS_CLASS_FLASH for the flash related features of a LED device. It can be built as a module. +config LEDS_CLASS_MULTI_COLOR + tristate "LED Mulit Color LED Class Support" + depends on LEDS_CLASS + help + This option enables the multicolor LED sysfs class in /sys/class/leds. + It wraps LED class and adds multicolor LED specific sysfs attributes + and kernel internal API to it. You'll need this to provide support + for multicolor LEDs that are grouped together. This class is not + intended for single color LEDs. It can be built as a module. + config LEDS_BRIGHTNESS_HW_CHANGED bool "LED Class brightness_hw_changed attribute support" depends on LEDS_CLASS
drivers/leds/Makefile +1 -0
@@ -4,6 +4,7 @@ obj-$(CONFIG_NEW_LEDS) += led-core.o obj-$(CONFIG_LEDS_CLASS) += led-class.o obj-$(CONFIG_LEDS_CLASS_FLASH) += led-class-flash.o +obj-$(CONFIG_LEDS_CLASS_MULTI_COLOR) += led-class-multicolor.o obj-$(CONFIG_LEDS_TRIGGERS) += led-triggers.o # LED Platform Drivers
drivers/leds/led-class-multicolor.c new file +271 -0
271 lines not on this page · raw message
include/linux/led-class-multicolor.h new file +97 -0
97 lines not on this page · raw message
Signature · 1 line
2.22.0.214.g8dca754b1e
Re: [PATCH v13 04/18] leds: multicolor: Introduce a multicolor class definition
Dan,
Quoted 10 lines · Dan Murphy
Introduce a multicolor class that groups colored LEDs within a LED node.
The multi color class groups monochrome LEDs and allows controlling two aspects of the final combined color: hue and lightness. The former is controlled via <color>_intensity files and the latter is controlled via brightness file.
Signed-off-by Dan Murphy <[email protected]>---
[...]
Quoted 46 lines
(quoted diff) +46
-0+static int led_multicolor_init_color(struct led_classdev_mc *mcled_cdev, + int color_id) +{ + struct led_classdev *led_cdev = mcled_cdev->led_cdev; + struct led_mc_color_entry *mc_priv; + char *intensity_file_name; + char *max_intensity_file_name; + size_t len; + int ret; + + mc_priv = devm_kzalloc(led_cdev->dev, sizeof(*mc_priv), GFP_KERNEL); + if (!mc_priv) + return -ENOMEM; + + mc_priv->led_color_id = color_id; + mc_priv->mcled_cdev = mcled_cdev; + + sysfs_attr_init(&mc_priv->intensity_attr.attr); + len = strlen(led_colors[color_id]) + strlen(INTENSITY_NAME) + 1; + intensity_file_name = kzalloc(len, GFP_KERNEL); + if (!intensity_file_name) + return -ENOMEM; + + snprintf(intensity_file_name, len, "%s%s", + led_colors[color_id], INTENSITY_NAME); + mc_priv->intensity_attr.attr.name = intensity_file_name; + mc_priv->intensity_attr.attr.mode = 0644; + mc_priv->intensity_attr.store = intensity_store; + mc_priv->intensity_attr.show = intensity_show; + ret = sysfs_add_file_to_group(&led_cdev->dev->kobj, + &mc_priv->intensity_attr.attr, + led_color_group.name); + if (ret) + goto intensity_err_out; + + sysfs_attr_init(&mc_priv->max_intensity_attr.attr); + len = strlen(led_colors[color_id]) + strlen(MAX_INTENSITY_NAME) + 1; + max_intensity_file_name = kzalloc(len, GFP_KERNEL); + if (!max_intensity_file_name) { + ret = -ENOMEM; + goto intensity_err_out; + } + + snprintf(max_intensity_file_name, len, "%s%s", + led_colors[color_id], MAX_INTENSITY_NAME); + mc_priv->max_intensity_attr.attr.name = max_intensity_file_name;
Review
Quoted 10 lines
(quoted diff) +10
-0+ mc_priv->max_intensity_attr.attr.mode = 0444; + mc_priv->max_intensity_attr.show = max_intensity_show; + ret = sysfs_add_file_to_group(&led_cdev->dev->kobj, + &mc_priv->max_intensity_attr.attr, + led_color_group.name); + if (ret) + goto max_intensity_err_out; + + mc_priv->max_intensity = LED_FULL; + list_add_tail(&mc_priv->list, &mcled_cdev->color_list);
We don't need the list here since our collection of color LEDs will be fixed. Instead of the list we can do with a dynamically allocated array of a size depending on available color LEDs.
It will allow also to get rid of lp55xx_map_channel() since random access to array elements will be possible via lookup tables mapping colors to array element id.
And regarding my amendments to the DT parser - attached is the patch for your patch, that is compile-tested.
Quoted 9 lines
(quoted diff) +8
-0+ +max_intensity_err_out: + kfree(max_intensity_file_name); +intensity_err_out: + kfree(intensity_file_name); + return ret; +} +
Signature · 2 lines
Best regards, Jacek Anaszewski
From fb0ce79b97acf6ee68ec4a2a9e24d56080826766 Mon Sep 17 00:00:00 2001
From: Jacek Anaszewski <[email protected]>
Date: Sat, 19 Oct 2019 19:45:18 +0200
Subject: [PATCH] DT parser amendments
--- drivers/leds/leds-lp55xx-common.c | 109 ++++++++++++++++-------------- include/linux/platform_data/leds-lp55xx.h | 1 + 2 files changed, 61 insertions(+), 49 deletions(-)
drivers/leds/leds-lp55xx-common.c +60 -49
@@ -590,82 +590,93 @@ void lp55xx_unregister_sysfs(struct lp55xx_chip *chip) }EXPORT_SYMBOL_GPL (lp55xx_unregister_sysfs); -static int lp5xx_parse_common_child (struct device_node *np, -struct lp55xx_led_config *cfg, -int chan_num,bool is_multicolor, -int color_num) +static int lp55xx_parse_common_child (struct device_node *np, +struct lp55xx_led_config *cfg, +int led_number,int *chan_nr) { -u32 led_number;int ret;of_property_read_string (np,"chan-name" , - &cfg[chan_num].name); + &cfg[led_number].name);of_property_read_u8 (np,"led-cur" , - &cfg[chan_num].led_current); + &cfg[led_number].led_current);of_property_read_u8 (np,"max-cur" , - &cfg[chan_num].max_current); + &cfg[led_number].max_current); - ret =of_property_read_u32 (np,"reg" , &led_number); + ret =of_property_read_u32 (np,"reg" , chan_nr);if (ret)return ret; -if (led_number <0 || led_number >6 ) +if (chan_nr <0 || chan_nr > cfg->max_channel)return -EINVAL ; -if (is_multicolor) - cfg[chan_num].color_components[color_num].output_num = - led_number; -else - cfg[chan_num].chan_nr = led_number; -return 0 ; } -static int lp5xx_parse_channel_child (struct device_node *np, -struct lp55xx_led_config *cfg, -int child_number) +static int lp55xx_parse_mutli_led_child (struct device_node *child, +struct lp55xx_led_config *cfg, +int child_number,int color_number) { -struct device_node *child; -int channel_color; -int num_colors =0 ; -u32 color_id; -int ret; - - cfg[child_number].default_trigger = -of_get_property (np,"linux,default-trigger" ,NULL ); +int chan_nr, color_id, ret; - ret =of_property_read_u32 (np,"color" , &channel_color); + ret =lp55xx_parse_common_child (child, cfg, child_number, &chan_nr);if (ret) - channel_color = ret; +return ret; + ret =of_property_read_u32 (child,"color" , &color_id); +if (ret) +return ret; -if (channel_color ==LED_COLOR_ID_MULTI ) { -for_each_child_of_node (np, child) { - ret =lp5xx_parse_common_child (child, cfg, - child_number, true, - num_colors); -if (ret) -return ret; + cfg[child_number].color_components[color_number].color_id = color_id; + cfg[child_number].color_components[color_number].output_num = chan_nr; +set_bit (color_id, &cfg[child_number].available_colors); - ret =of_property_read_u32 (child,"color" , &color_id); -if (ret) -return ret; +return 0 ; +} - cfg[child_number].color_components[num_colors].color_id = - color_id; -set_bit (color_id, &cfg[child_number].available_colors); - num_colors++; - } +static int lp55xx_parse_mutli_led (struct device_node *np, +struct lp55xx_led_config *cfg, +int child_number) +{ +struct device_node *child; +int num_colors =0 , ret; - cfg[child_number].num_colors = num_colors; - }else { -return lp5xx_parse_common_child (np, cfg, child_number, false, - num_colors); +for_each_child_of_node (np, child) { + ret =lp55xx_parse_mutli_led_child (child, cfg, child_number, + num_colors); +if (ret) +return ret; + num_colors++; }return 0 ; } +static int lp55xx_parse_logical_led (struct device_node *np, +struct lp55xx_led_config *cfg, +int child_number) +{ +int led_color, ret; + + cfg[child_number].default_trigger = +of_get_property (np,"linux,default-trigger" ,NULL ); + + ret =of_property_read_u32 (np,"color" , &led_color); + +if (ret) { +int chan_nr; + ret =lp55xx_parse_common_child (np, cfg, child_number, + &chan_nr); +if (ret <0 ) +return ret; + cfg[child_number].chan_nr = chan_nr; + }else if (led_color ==LED_COLOR_ID_MULTI ) { +return lp55xx_parse_mutli_led (np, cfg, child_number); + } + +return ret; +} +struct lp55xx_platform_data *lp55xx_of_populate_pdata (struct device *dev,struct device_node *np) {
@@ -694,7 +705,7 @@ struct lp55xx_platform_data *lp55xx_of_populate_pdata(struct device *dev, pdata->num_channels = num_channels;for_each_child_of_node (np, child) { - ret =lp5xx_parse_channel_child (child, cfg, i); + ret =lp55xx_parse_logical_led (child, cfg, i);if (ret)return ERR_PTR (-EINVAL ); i++;
include/linux/platform_data/leds-lp55xx.h +1 -0
@@ -28,6 +28,7 @@ struct lp55xx_led_config {u8 led_current;/* mA x10, 0 if led is not connected */ u8 max_current;int num_colors; +unsigned int max_channel;unsigned long available_colors;struct led_mc_color_conversion color_components[LP55XX_MAX_GROUPED_CHAN ]; };
Signature · 1 line
2.11.0
PATCH v13 5/18 dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers
In reply to Dan MurphyIntroduce the bindings for the Texas Instruments LP5036, LP5030, LP5024, LP5018, LP5012 and LP5009 RGB LED device driver. The LP5036/30/24/18/12/9 can control RGB LEDs individually or as part of a control bank group. These devices have the ability to adjust the mixing control for the RGB LEDs to obtain different colors independent of the overall brightness of the LED grouping.
Datasheet:
http://www.ti.com/lit/ds/symlink/lp5012.pdf
http://www.ti.com/lit/ds/symlink/lp5024.pdf
http://www.ti.com/lit/ds/symlink/lp5036.pdf
--- .../devicetree/bindings/leds/leds-lp50xx.txt | 148 ++++++++++++++++++ 1 file changed, 148 insertions(+) create mode 100644 Documentation/devicetree/bindings/leds/leds-lp50xx.txt
Documentation/devicetree/bindings/leds/leds-lp50xx.txt new file +148 -0
@@ -0,0 +1,148 @@ +* Texas Instruments - LP5009/12/18/24/30/36 RGB LED driver + +The LP50XX is multi-channel, I2C RGB LED Drivers that can group RGB LEDs into +a LED group or control them individually. + +The difference in these RGB LED drivers is the number of supported RGB modules. + +Required parent properties: + - compatible: + "ti,lp5009" + "ti,lp5012" + "ti,lp5018" + "ti,lp5024" + "ti,lp5030" + "ti,lp5036" + - reg : I2C slave address + lp5009/12 - 0x14, 0x15, 0x16, 0x17 + lp5018/24 - 0x28, 0x29, 0x2a, 0x2b + lp5030/36 - 0x30, 0x31, 0x32, 0x33 + - #address-cells : 1 + - #size-cells : 0 + +Optional parent properties: + - enable-gpios : gpio pin to enable/disable the device. + - vled-supply : LED supply + +Required child properties: + - #address-cells : 1 + - #size-cells : 0 + - reg : This is the LED module number. + - color : Must be LED_COLOR_ID_MULTI + - function : see Documentation/devicetree/bindings/leds/common.txt + +Required child properties only is LED modules will be banked: + - ti,led-bank : This property denotes the LED module numbers that will + be controlled as a single RGB cluster. Each LED module + number will be controlled by a single LED class instance. + There can only be one instance of the ti,led-bank + property for each device node. + +Required grandchildren properties: + - reg : A single entry denoting the LED output that controls + the monochrome LED. + - color : see Documentation/devicetree/bindings/leds/common.txt + - led-sources : see Documentation/devicetree/bindings/leds/common.txt + +The LED outputs associated with the LED modules are defined in Table 1 of the +corresponding data sheets. + +LP5009 - 3 Total RGB cluster LED outputs 0-2 +LP5012 - 4 Total RGB cluster LED outputs 0-3 +LP5018 - 6 Total RGB cluster LED outputs 0-5 +LP5024 - 8 Total RGB cluster LED outputs 0-7 +LP5030 - 10 Total RGB cluster LED outputs 0-9 +LP5036 - 12 Total RGB cluster LED outputs 0-11 + +Optional child properties: + - label : see Documentation/devicetree/bindings/leds/common.txt + - linux,default-trigger : + see Documentation/devicetree/bindings/leds/common.txt + +Examples: +led-controller@29 { + #address-cells = <1>; + #size-cells = <0>; + compatible = "ti,lp5024"; + reg = <0x29>; + enable-gpios = <&gpio1 28 GPIO_ACTIVE_HIGH>; + vled-supply = <&vmmcsd_fixed>; + + multi-led@1 { + #address-cells = <1>; + #size-cells = <0>; + reg = <1>; + color = <LED_COLOR_ID_MULTI>; + function = LED_FUNCTION_STATUS; + + led@3 { + reg = <3>; + color = <LED_COLOR_ID_RED>; + }; + + led@4 { + reg = <4>; + color = <LED_COLOR_ID_GREEN>; + }; + + led@5 { + reg = <5>; + color = <LED_COLOR_ID_BLUE>; + }; + }; + + multi-led@2 { + #address-cells = <1>; + #size-cells = <0>; + reg = <2>; + color = <LED_COLOR_ID_MULTI>; + function = LED_FUNCTION_STANDBY; + ti,led-bank = <2 3 5>; + + led@6 { + reg = <0x6>; + color = <LED_COLOR_ID_RED>; + led-sources = <6 9 15>; + }; + + led@7 { + reg = <0x7>; + color = <LED_COLOR_ID_GREEN>; + led-sources = <7 10 16>; + }; + + led@8 { + reg = <0x8>; + color = <LED_COLOR_ID_BLUE>; + led-sources = <8 11 17>; + }; + }; + + multi-led@4 { + #address-cells = <1>; + #size-cells = <0>; + reg = <4>; + color = <LED_COLOR_ID_MULTI>; + function = LED_FUNCTION_ACTIVITY; + + led@12 { + reg = <12>; + color = <LED_COLOR_ID_RED>; + }; + + led@13 { + reg = <13>; + color = <LED_COLOR_ID_GREEN>; + }; + + led@14 { + reg = <14>; + color = <LED_COLOR_ID_BLUE>; + }; + }; +}; + +For more product information please see the link below: +http://www.ti.com/lit/ds/symlink/lp5012.pdf +http://www.ti.com/lit/ds/symlink/lp5024.pdf +http://www.ti.com/lit/ds/symlink/lp5036.pdf
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 6/18 leds: lp50xx: Add the LP50XX family of the RGB LED driver
In reply to Dan MurphyIntroduce the LP5036/30/24/18/12/9 RGB LED driver. The difference in these parts are the number of LED outputs where the:
LP5036 can control 36 LEDs
LP5030 can control 30 LEDs
LP5024 can control 24 LEDs
LP5018 can control 18 LEDs
LP5012 can control 12 LEDs
LP5009 can control 9 LEDs
The device has the ability to group LED output into control banks so that multiple LED banks can be controlled with the same mixing and brightness. Inversely the LEDs can also be controlled independently.
--- drivers/leds/Kconfig | 11 + drivers/leds/Makefile | 1 + drivers/leds/leds-lp50xx.c | 799 +++++++++++++++++++++++++++++++++++++ 3 files changed, 811 insertions(+) create mode 100644 drivers/leds/leds-lp50xx.c
drivers/leds/Kconfig +11 -0
@@ -363,6 +363,17 @@ config LEDS_LP3952 To compile this driver as a module, choose M here: the module will be called leds-lp3952. +config LEDS_LP50XX + tristate "LED Support for TI LP5036/30/24/18/12/9 LED driver chip" + depends on LEDS_CLASS && REGMAP_I2C + depends on LEDS_CLASS_MULTI_COLOR + help + If you say yes here you get support for the Texas Instruments + LP5036, LP5030, LP5024, LP5018, LP5012 and LP5009 LED driver. + + To compile this driver as a module, choose M here: the + module will be called leds-lp50xx. + config LEDS_LP55XX_COMMON tristate "Common Driver for TI/National LP5521/5523/55231/5562/8501" depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562 || LEDS_LP8501
drivers/leds/Makefile +1 -0
@@ -34,6 +34,7 @@ obj-$(CONFIG_LEDS_GPIO_REGISTER) += leds-gpio-register.o obj-$(CONFIG_LEDS_GPIO) += leds-gpio.o obj-$(CONFIG_LEDS_LP3944) += leds-lp3944.o obj-$(CONFIG_LEDS_LP3952) += leds-lp3952.o +obj-$(CONFIG_LEDS_LP50XX) += leds-lp50xx.o obj-$(CONFIG_LEDS_LP55XX_COMMON) += leds-lp55xx-common.o obj-$(CONFIG_LEDS_LP5521) += leds-lp5521.o obj-$(CONFIG_LEDS_LP5523) += leds-lp5523.o
drivers/leds/leds-lp50xx.c new file +799 -0
799 lines not on this page · raw message
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 7/18 dt: bindings: lp55xx: Be consistent in the document with LED acronym
In reply to Dan MurphyUpdate the document to be consistent in case when using "LED". This acronym should be capital throughout the document.
--- Documentation/devicetree/bindings/leds/leds-lp55xx.txt | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-)
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +3 -3
@@ -1,4 +1,4 @@ -Binding for TI/National Semiconductor LP55xx Led Drivers +Binding for TI/National Semiconductor LP55xx LED Drivers Required properties: - compatible: one of
@@ -12,8 +12,8 @@ Required properties: - 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. +- 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: - enable-gpio: GPIO attached to the chip's enable pin
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 8/18 dt: bindings: lp55xx: Update binding for Multicolor Framework
In reply to Dan MurphyUpdate the DT binding to include the properties to use the multicolor framework for the devices that use the LP55xx framework.
--- .../devicetree/bindings/leds/leds-lp55xx.txt | 149 +++++++++++++++--- 1 file changed, 124 insertions(+), 25 deletions(-)
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +124 -25
@@ -1,6 +1,8 @@ Binding for TI/National Semiconductor LP55xx LED Drivers Required properties: +- #address-cells: 1 +- #size-cells: 0 - compatible: one of national,lp5521 national,lp5523
@@ -14,6 +16,18 @@ Required properties: 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. +- reg: Output channel for the LED. This is zero based channel identifier and + the data sheet is a one based channel identifier. + reg value to output to LED output number + D1 = reg value is 0 + D2 = reg value is 1 + D3 = reg value is 2 + D4 = reg value is 3 + D5 = reg value is 4 + D6 = reg value is 5 + D7 = reg value is 6 + D8 = reg value is 7 + D9 = reg value is 8 Optional properties: - enable-gpio: GPIO attached to the chip's enable pin
@@ -35,23 +49,28 @@ example 1) LP5521 on channel 0. lp5521@32 { + #address-cells = <1>; + #size-cells = <0>; compatible = "national,lp5521"; reg = <0x32>; label = "lp5521_pri"; clock-mode = /bits/ 8 <2>; - chan0 { + chan@0 { + reg = <0>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; linux,default-trigger = "heartbeat"; }; - chan1 { + chan@1 { + reg = <1>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; }; - chan2 { + chan@2 { + reg = <2>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; };
@@ -70,59 +89,70 @@ ASEL1 ASEL0 Address VEN VEN 35h lp5523@32 { + #address-cells = <1>; + #size-cells = <0>; compatible = "national,lp5523"; reg = <0x32>; clock-mode = /bits/ 8 <1>; - chan0 { + chan@0 { + reg = <0>; chan-name = "d1"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan1 { + chan@1 { + reg = <1>; chan-name = "d2"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan2 { + chan@2 { + reg = <2>; chan-name = "d3"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan3 { + chan@3 { + reg = <3>; chan-name = "d4"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan4 { + chan@4 { + reg = <4>; chan-name = "d5"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan5 { + chan@5 { + reg = <5>; chan-name = "d6"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan6 { + chan@6 { + reg = <6>; chan-name = "d7"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan7 { + chan@7 { + reg = <7>; chan-name = "d8"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan8 { + chan@8 { + reg = <8>; chan-name = "d9"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>;
@@ -133,29 +163,35 @@ example 3) LP5562 4 channels are defined. lp5562@30 { + #address-cells = <1>; + #size-cells = <0>; compatible = "ti,lp5562"; reg = <0x30>; clock-mode = /bits/8 <2>; - chan0 { + chan@0 { + reg = <0>; chan-name = "R"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; }; - chan1 { + chan@1 { + reg = <1>; chan-name = "G"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; }; - chan2 { + chan@2 { + reg = <2>; chan-name = "B"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; }; - chan3 { + chan@3 { + reg = <3>; chan-name = "W"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>;
@@ -167,62 +203,125 @@ example 4) LP8501 Others are same as LP5523. lp8501@32 { + #address-cells = <1>; + #size-cells = <0>; compatible = "ti,lp8501"; reg = <0x32>; clock-mode = /bits/ 8 <2>; pwr-sel = /bits/ 8 <3>; /* D1~9 connected to VOUT */ - chan0 { + chan@0 { + reg = <0>; chan-name = "d1"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan1 { + chan@1 { + reg = <1>; chan-name = "d2"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan2 { + chan@2 { + reg = <2>; chan-name = "d3"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan3 { + chan@3 { + reg = <3>; chan-name = "d4"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan4 { + chan@4 { + reg = <4>; chan-name = "d5"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan5 { + chan@5 { + reg = <5>; chan-name = "d6"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan6 { + chan@6 { + reg = <6>; chan-name = "d7"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan7 { + chan@7 { + reg = <7>; chan-name = "d8"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan8 { + chan@8 { + reg = <8>; chan-name = "d9"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; }; + +Multicolor Framework Support +In addition to the nodes and properties defined above for device support the +properties below are needed for multicolor framework support as defined in +Documentation/devicetree/bindings/leds/leds-class-multicolor.txt + +Required child properties for multicolor framework + - color : Must be LED_COLOR_ID_MULTI + - function : see Documentation/devicetree/bindings/leds/common.txt + +Required grandchildren properties + - reg : This is the LED output of the device + - color : see Documentation/devicetree/bindings/leds/common.txt + +Multicolor LED example: +led-controller@32 { + #address-cells = <1>; + #size-cells = <0>; + compatible = "national,lp5523"; + reg = <0x32>; + clock-mode = /bits/ 8 <0>; /* LP55XX_CLOCK_AUTO */ + + multi-led@2 { + #address-cells = <1>; + #size-cells = <0>; + reg = <2>; + color = <LED_COLOR_ID_MULTI>; + function = LED_FUNCTION_STANDBY; + linux,default-trigger = "heartbeat"; + + led@0 { + led-cur = /bits/ 8 <50>; + max-cur = /bits/ 8 <100>; + reg = <0x0>; + color = <LED_COLOR_ID_GREEN>; + }; + + led@1 { + led-cur = /bits/ 8 <50>; + max-cur = /bits/ 8 <100>; + reg = <0x1>; + color = <LED_COLOR_ID_BLUE>; + }; + + led@6 { + led-cur = /bits/ 8 <50>; + max-cur = /bits/ 8 <100>; + reg = <0x6>; + color = <LED_COLOR_ID_RED>; + }; + }; +};
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 9/18 ARM: dts: n900: Add reg property to the LP5523 channel node
In reply to Dan MurphyAdd the reg property to each channel node. This update is to accomodate the multicolor framework. In addition to the accomodation this allows the LEDs to be placed on any channel and allow designs to skip channels as opposed to requiring sequential order.
k# interactive rebase in progress; onto ae89cc6d4a8c
--- arch/arm/boot/dts/omap3-n900.dts | 29 ++++++++++++++++++++--------- 1 file changed, 20 insertions(+), 9 deletions(-)
arch/arm/boot/dts/omap3-n900.dts +20 -9
@@ -607,63 +607,74 @@ }; lp5523: lp5523@32 { + #address-cells = <1>; + #size-cells = <0>; compatible = "national,lp5523"; reg = <0x32>; clock-mode = /bits/ 8 <0>; /* LP55XX_CLOCK_AUTO */ enable-gpio = <&gpio2 9 GPIO_ACTIVE_HIGH>; /* 41 */ - chan0 { + chan@0 { chan-name = "lp5523:kb1"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <0>; }; - chan1 { + chan@1 { chan-name = "lp5523:kb2"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <1>; }; - chan2 { + chan@2 { chan-name = "lp5523:kb3"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <2>; }; - chan3 { + chan@3 { chan-name = "lp5523:kb4"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <3>; }; - chan4 { + chan@4 { chan-name = "lp5523:b"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <4>; }; - chan5 { + chan@5 { chan-name = "lp5523:g"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <5>; }; - chan6 { + chan@6 { chan-name = "lp5523:r"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <6>; }; - chan7 { + chan@7 { chan-name = "lp5523:kb5"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <7>; }; - chan8 { + chan@8 { chan-name = "lp5523:kb6"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <8>; }; };
Signature · 1 line
2.22.0.214.g8dca754b1e
Re: [PATCH v13 09/18] ARM: dts: n900: Add reg property to the LP5523 channel node
Quoted 11 lines · Dan Murphy
Add the reg property to each channel node. This update is to accomodate the multicolor framework. In addition to the accomodation this allows the LEDs to be placed on any channel and allow designs to skip channels as opposed to requiring sequential order.
Signed-off-by Dan Murphy <[email protected]>CC Tony Lindgren <[email protected]>CC "Benoît Cousson" <[email protected]>k# interactive rebase in progress; onto
ae89cc6d4a8c
Maybe check what's up with the line above :)
Othwerwise looks good to me, best to merge this together with the rest of the series when ready:
Quoted 95 lines
--- arch/arm/boot/dts/omap3-n900.dts | 29 ++++++++++++++++++++--------- 1 file changed, 20 insertions(+), 9 deletions(-)arch/arm/boot/dts/omap3-n900.dts +20
-9@@ -607,63 +607,74 @@ }; lp5523: lp5523@32 { + #address-cells = <1>; + #size-cells = <0>; compatible = "national,lp5523"; reg = <0x32>; clock-mode = /bits/ 8 <0>; /* LP55XX_CLOCK_AUTO */ enable-gpio = <&gpio2 9 GPIO_ACTIVE_HIGH>; /* 41 */ - chan0 { + chan@0 { chan-name = "lp5523:kb1"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <0>; }; - chan1 { + chan@1 { chan-name = "lp5523:kb2"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <1>; }; - chan2 { + chan@2 { chan-name = "lp5523:kb3"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <2>; }; - chan3 { + chan@3 { chan-name = "lp5523:kb4"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <3>; }; - chan4 { + chan@4 { chan-name = "lp5523:b"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <4>; }; - chan5 { + chan@5 { chan-name = "lp5523:g"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <5>; }; - chan6 { + chan@6 { chan-name = "lp5523:r"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <6>; }; - chan7 { + chan@7 { chan-name = "lp5523:kb5"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <7>; }; - chan8 { + chan@8 { chan-name = "lp5523:kb6"; led-cur = /bits/ 8 <50>; max-cur = /bits/ 8 <100>; + reg = <8>; }; };Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 10/18 ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 channel node
In reply to Dan MurphyAdd the reg property to each channel node. This update is to accomodate the multicolor framework. In addition to the accomodation this allows the LEDs to be placed on any channel and allow designs to skip channels as opposed to requiring sequential order.
--- arch/arm/boot/dts/imx6dl-yapp4-common.dtsi | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)
arch/arm/boot/dts/imx6dl-yapp4-common.dtsi +10 -4
@@ -257,29 +257,35 @@ reg = <0x30>; clock-mode = /bits/ 8 <1>; status = "disabled"; + #address-cells = <1>; + #size-cells = <0>; - chan0 { + chan@0 { chan-name = "R"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; + reg = <0>; }; - chan1 { + chan@1 { chan-name = "G"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; + reg = <1>; }; - chan2 { + chan@2 { chan-name = "B"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; + reg = <2>; }; - chan3 { + chan@3 { chan-name = "W"; led-cur = /bits/ 8 <0x0>; max-cur = /bits/ 8 <0x0>; + reg = <3>; }; };
Signature · 1 line
2.22.0.214.g8dca754b1e
Re: [PATCH v13 10/18] ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 channel node
Quoted 21 lines · Dan Murphy
Add the reg property to each channel node. This update is to accomodate the multicolor framework. In addition to the accomodation this allows the LEDs to be placed on any channel and allow designs to skip channels as opposed to requiring sequential order.
Signed-off-by Dan Murphy <[email protected]>CC Shawn Guo <[email protected]>CC Sascha Hauer <[email protected]>CC Pengutronix Kernel Team <[email protected]>CC Fabio Estevam <[email protected]>CC NXP Linux Team <[email protected]>--- arch/arm/boot/dts/imx6dl-yapp4-common.dtsi | 14 ++++++++++---- 1 file changed, 10 insertions(+), 4 deletions(-)arch/arm/boot/dts/imx6dl-yapp4-common.dtsi +0
-0
arch/arm/boot/dts/imx6dl-yapp4-common.dtsi line 263
Quoted 8 lines
arch/arm/boot/dts/imx6dl-yapp4-common.dtsi +3
-1@@ -257,29 +257,35 @@ reg = <0x30>; clock-mode = /bits/ 8 <1>; status = "disabled"; + #address-cells = <1>; + #size-cells = <0>; - chan0 { + chan@0 {
Patch #18 updates bindings example to use led as node name. Maybe we should do the same here?
Shawn
Quoted 34 lines
arch/arm/boot/dts/imx6dl-yapp4-common.dtsi +7
-3chan-name = "R"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; + reg = <0>; }; - chan1 { + chan@1 { chan-name = "G"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; + reg = <1>; }; - chan2 { + chan@2 { chan-name = "B"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; + reg = <2>; }; - chan3 { + chan@3 { chan-name = "W"; led-cur = /bits/ 8 <0x0>; max-cur = /bits/ 8 <0x0>; + reg = <3>; }; };Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 11/18 ARM: dts: ste-href: Add reg property to the LP5521 channel nodes
In reply to Dan MurphyAdd the reg property to each channel node. This update is to accomodate the multicolor framework. In addition to the accomodation this allows the LEDs to be placed on any channel and allow designs to skip channels as opposed to requiring sequential order.
--- arch/arm/boot/dts/ste-href.dtsi | 22 ++++++++++++++++------ 1 file changed, 16 insertions(+), 6 deletions(-)
arch/arm/boot/dts/ste-href.dtsi +16 -6
@@ -56,16 +56,21 @@ reg = <0x33>; label = "lp5521_pri"; clock-mode = /bits/ 8 <2>; - chan0 { + #address-cells = <1>; + #size-cells = <0>; + chan@0 { + reg = <0>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; linux,default-trigger = "heartbeat"; }; - chan1 { + chan@1 { + reg = <1>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; }; - chan2 { + chan@2 { + reg = <2>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; };
@@ -75,15 +80,20 @@ reg = <0x34>; label = "lp5521_sec"; clock-mode = /bits/ 8 <2>; - chan0 { + #address-cells = <1>; + #size-cells = <0>; + chan@0 { + reg = <0>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; }; - chan1 { + chan@1 { + reg = <1>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; }; - chan2 { + chan@2 { + reg = <2>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; };
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 12/18 leds: lp55xx: Convert LED class registration to devm_*
In reply to Dan MurphyConvert the LED class registration calls to the LED devm_* registration calls.
--- drivers/leds/leds-lp55xx-common.c | 4 ++-- 1 file changed, 2 insertions(+), 2 deletions(-)
drivers/leds/leds-lp55xx-common.c +2 -2
@@ -181,7 +181,7 @@ static int lp55xx_init_led(struct lp55xx_led *led, led->cdev.name = name; } - ret =led_classdev_register (dev, &led->cdev); + ret =devm_led_classdev_register (dev, &led->cdev);if (ret) {dev_err (dev,"led register err: %d\n" , ret);return ret;
@@ -502,7 +502,7 @@ void lp55xx_unregister_leds(struct lp55xx_led *led, struct lp55xx_chip *chip)for (i =0 ; i < chip->num_leds; i++) { each = led + i; -led_classdev_unregister (&each->cdev); +devm_led_classdev_unregister (each->cdev.dev, &each->cdev); } }EXPORT_SYMBOL_GPL (lp55xx_unregister_leds);
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 13/18 leds: lp55xx: Add multicolor framework support to lp55xx
In reply to Dan MurphyAdd multicolor framework support for the lp55xx family.
--- drivers/leds/Kconfig | 2 + drivers/leds/leds-lp55xx-common.c | 175 +++++++++++++++++++--- drivers/leds/leds-lp55xx-common.h | 9 ++ include/linux/platform_data/leds-lp55xx.h | 7 + 4 files changed, 170 insertions(+), 23 deletions(-)
drivers/leds/Kconfig +2 -0
@@ -377,8 +377,10 @@ config LEDS_LP50XX config LEDS_LP55XX_COMMON tristate "Common Driver for TI/National LP5521/5523/55231/5562/8501" depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562 || LEDS_LP8501 + depends on OF select FW_LOADER select FW_LOADER_USER_HELPER + select LEDS_CLASS_MULTI_COLOR help This option supports common operations for LP5521/5523/55231/5562/8501 devices.
drivers/leds/leds-lp55xx-common.c +152 -23
229 lines not on this page · raw message
drivers/leds/leds-lp55xx-common.h +9 -0
@@ -12,6 +12,8 @@#ifndef _LEDS_LP55XX_COMMON_H#define _LEDS_LP55XX_COMMON_H +#include <linux/led-class-multicolor.h> +enum lp55xx_engine_index {LP55XX_ENGINE_INVALID , LP55XX_ENGINE_1,
@@ -109,6 +111,9 @@ struct lp55xx_device_config {/* access brightness register */ int (*brightness_fn)(struct lp55xx_led *led); +/* perform brightness value to multiple LEDs */ +int (*multicolor_brightness_fn)(struct lp55xx_led *led); +/* current setting function */ void (*set_led_current) (struct lp55xx_led *led,u8 led_current);
@@ -159,6 +164,8 @@ struct lp55xx_chip {* struct lp55xx_led * @chan_nr : Channel number * @cdev : LED class device +* @mc_cdev : Multi color class device +* @color_component : Multi color LED map information * @led_current : Current setting at each led channel * @max_current : Maximun current at each led channel * @brightness : Brightness value
@@ -167,6 +174,8 @@ struct lp55xx_chip {struct lp55xx_led {int chan_nr;struct led_classdev cdev; +struct led_classdev_mc mc_cdev; +struct led_mc_color_conversion color_component[LP55XX_MAX_GROUPED_CHAN ];u8 led_current;u8 max_current;u8 brightness;
include/linux/platform_data/leds-lp55xx.h +7 -0
@@ -12,17 +12,24 @@#ifndef _LEDS_LP55XX_H#define _LEDS_LP55XX_H +#include <linux/led-class-multicolor.h> +/* Clock configuration */ #define LP55XX_CLOCK_AUTO 0#define LP55XX_CLOCK_INT 1#define LP55XX_CLOCK_EXT 2 +#define LP55XX_MAX_GROUPED_CHAN 4 +struct lp55xx_led_config {const char *name;const char *default_trigger;u8 chan_nr;u8 led_current;/* mA x10, 0 if led is not connected */ u8 max_current; +int num_colors; +unsigned long available_colors; +struct led_mc_color_conversion color_component[LP55XX_MAX_GROUPED_CHAN ]; }; struct lp55xx_predef_pattern {
Signature · 1 line
2.22.0.214.g8dca754b1e
Re: [PATCH v13 13/18] leds: lp55xx: Add multicolor framework support to lp55xx
Dan,
Some variable naming related nitpicking below.
Quoted 30 lines · Dan Murphy
Add multicolor framework support for the lp55xx family.
Signed-off-by Dan Murphy <[email protected]>--- drivers/leds/Kconfig | 2 + drivers/leds/leds-lp55xx-common.c | 175 +++++++++++++++++++--- drivers/leds/leds-lp55xx-common.h | 9 ++ include/linux/platform_data/leds-lp55xx.h | 7 + 4 files changed, 170 insertions(+), 23 deletions(-)drivers/leds/Kconfig +2
-0@@ -377,8 +377,10 @@ config LEDS_LP50XX config LEDS_LP55XX_COMMON tristate "Common Driver for TI/National LP5521/5523/55231/5562/8501" depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562 || LEDS_LP8501 + depends on OF select FW_LOADER select FW_LOADER_USER_HELPER + select LEDS_CLASS_MULTI_COLOR help This option supports common operations for LP5521/5523/55231/5562/8501 devices.drivers/leds/leds-lp55xx-common.c +0
-0
drivers/leds/leds-lp55xx-common.c static struct attribute *lp55xx_led_attrs[] = { · line 140
Quoted 10 lines
drivers/leds/leds-lp55xx-common.c +7
-0@@ -131,14 +131,54 @@ static struct attribute *lp55xx_led_attrs[] = { };ATTRIBUTE_GROUPS (lp55xx_led); +static int lp55xx_map_channel (struct lp55xx_led *led,int color_id, +enum led_brightness brightness) +{ +int i; + +for (i =0 ; i < led->mc_cdev.num_leds; i++) { +if (led->color_component[i].color_id == color_id) {
I'd use plural "color_components" for the property name.
Quoted 15 lines
drivers/leds/leds-lp55xx-common.c +10
-0+ led->color_component[i].brightness = brightness; +return 0 ; + } + } + +return -EINVAL ; +} +static int lp55xx_set_brightness (struct led_classdev *cdev,enum led_brightness brightness) { +struct led_mc_color_conversion color_component[LP55XX_MAX_GROUPED_CHAN ];struct lp55xx_led *led =cdev_to_lp55xx_led (cdev);struct lp55xx_device_config *cfg = led->chip->cfg; +int ret;
drivers/leds/leds-lp55xx-common.c static struct attribute *lp55xx_led_attrs[] = { · line 163
Quoted 10 lines
drivers/leds/leds-lp55xx-common.c +7
-2+int i; - led->brightness = (u8 )brightness; -return cfg->brightness_fn (led); +if (led->mc_cdev.num_leds >1 ) { +if (!cfg->multicolor_brightness_fn) +return -EINVAL ; + +led_mc_calc_color_components (&led->mc_cdev, brightness, + color_component);
Similarly here - you calculate all components so it is weird to pass variable of singular color_component form.
Quoted 18 lines
drivers/leds/leds-lp55xx-common.c +18
-0+ +for (i =0 ; i < led->mc_cdev.num_leds; i++) { + ret =lp55xx_map_channel (led, + color_component[i].color_id, + color_component[i].brightness); +if (ret) +return ret; + } + + ret = cfg->multicolor_brightness_fn (led); +if (ret) +return ret; + }else { + led->brightness = (u8 )brightness; + ret = cfg->brightness_fn (led); + } + +return ret;
[...]
Signature · 2 lines
Best regards, Jacek Anaszewski
Re: [PATCH v13 13/18] leds: lp55xx: Add multicolor framework support to lp55xx
And one more issue regarding LEDS_CLASS_MULTI_COLOR config.
Quoted 15 lines · Jacek Anaszewski
Dan,
Some variable naming related nitpicking below.
Quoted 10 lines · Dan Murphy
Add multicolor framework support for the lp55xx family.
Signed-off-by Dan Murphy <[email protected]>--- drivers/leds/Kconfig | 2 + drivers/leds/leds-lp55xx-common.c | 175 +++++++++++++++++++--- drivers/leds/leds-lp55xx-common.h | 9 ++ include/linux/platform_data/leds-lp55xx.h | 7 + 4 files changed, 170 insertions(+), 23 deletions(-)
Quoted 12 lines
drivers/leds/Kconfig config LEDS_LP50XX · line 383
Quoted 12 lines
drivers/leds/Kconfig +2
-0@@ -377,8 +377,10 @@ config LEDS_LP50XX config LEDS_LP55XX_COMMON tristate "Common Driver for TI/National LP5521/5523/55231/5562/8501" depends on LEDS_LP5521 || LEDS_LP5523 || LEDS_LP5562 || LEDS_LP8501 + depends on OF select FW_LOADER select FW_LOADER_USER_HELPER + select LEDS_CLASS_MULTI_COLOR
Why so? This is unnecessary.
Quoted 50 lines
Quoted 8 lines
drivers/leds/Kconfig +0
-0help This option supports common operations for LP5521/5523/55231/5562/8501 devices.drivers/leds/leds-lp55xx-common.c +0
-0drivers/leds/leds-lp55xx-common.c static struct attribute *lp55xx_led_attrs[] = { · line 140
Quoted 10 lines
drivers/leds/leds-lp55xx-common.c +7
-0@@ -131,14 +131,54 @@ static struct attribute *lp55xx_led_attrs[] = { };ATTRIBUTE_GROUPS (lp55xx_led); +static int lp55xx_map_channel (struct lp55xx_led *led,int color_id, +enum led_brightness brightness) +{ +int i; + +for (i =0 ; i < led->mc_cdev.num_leds; i++) { +if (led->color_component[i].color_id == color_id) {I'd use plural "
color_components" for the property name.Quoted 15 lines
drivers/leds/leds-lp55xx-common.c +10
-0+ led->color_component[i].brightness = brightness; +return 0 ; + } + } + +return -EINVAL ; +} +static int lp55xx_set_brightness (struct led_classdev *cdev,enum led_brightness brightness) { +struct led_mc_color_conversion color_component[LP55XX_MAX_GROUPED_CHAN ];struct lp55xx_led *led =cdev_to_lp55xx_led (cdev);struct lp55xx_device_config *cfg = led->chip->cfg; +int ret;drivers/leds/leds-lp55xx-common.c static struct attribute *lp55xx_led_attrs[] = { · line 163
Quoted 10 lines
drivers/leds/leds-lp55xx-common.c +7
-2+int i; - led->brightness = (u8 )brightness; -return cfg->brightness_fn (led); +if (led->mc_cdev.num_leds >1 ) { +if (!cfg->multicolor_brightness_fn) +return -EINVAL ; + +led_mc_calc_color_components (&led->mc_cdev, brightness, + color_component);Similarly here - you calculate all components so it is weird to pass variable of singular
color_componentform.
Quoted 12 lines
drivers/leds/leds-lp55xx-common.c static struct attribute *lp55xx_led_attrs[] = { · line 175
Quoted 12 lines
drivers/leds/leds-lp55xx-common.c +12
-0+ +for (i =0 ; i < led->mc_cdev.num_leds; i++) { + ret =lp55xx_map_channel (led, + color_component[i].color_id, + color_component[i].brightness); +if (ret) +return ret; + } + + ret = cfg->multicolor_brightness_fn (led); +if (ret) +return ret;
Please wrap what you have under "if: case into a function, e.g.:
static int lp55xx_set_mc_brightness()
{
int ret = -EINVAL;#if IS_ENABLED(CONFIG_LEDS_CLASS_MULTI_COLOR) if (!cfg->multicolor_brightness_fn) ....
#endif
return ret; }
And then have here:
if (led->mc_cdev.num_leds > 1)
ret = lp55xx_set_mc_brightness();
You won't need inline empty led_mc_calc_color_components() then.
Quoted 8 lines
Quoted 6 lines
drivers/leds/leds-lp55xx-common.c +6
-0+ }else { + led->brightness = (u8 )brightness; + ret = cfg->brightness_fn (led); + } + +return ret;[...]
Signature · 2 lines
Best regards, Jacek Anaszewski
PATCH v13 14/18 leds: lp5523: Update the lp5523 code to add multicolor brightness function
In reply to Dan MurphyAdd the multicolor brightness call back to support the multicolor framework. This call back allows setting brightness on grouped channels in a single function.
--- drivers/leds/leds-lp5523.c | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+)
drivers/leds/leds-lp5523.c +20 -0
@@ -791,6 +791,25 @@ static ssize_t store_master_fader_leds(struct device *dev,return ret; } +static int lp5523_multicolor_brightness (struct lp55xx_led *led) +{ +struct lp55xx_chip *chip = led->chip; +int ret; +int i; + +mutex_lock (&chip->lock); +for (i =0 ; i < led->mc_cdev.num_leds; i++) { + ret =lp55xx_write (chip, +LP5523_REG_LED_PWM_BASE + + led->color_component[i].output_num, + led->color_component[i].brightness); +if (ret) +break ; + } +mutex_unlock (&chip->lock); +return ret; +} +static int lp5523_led_brightness (struct lp55xx_led *led) {struct lp55xx_chip *chip = led->chip;
@@ -857,6 +876,7 @@ static struct lp55xx_device_config lp5523_cfg = { .max_channel = LP5523_MAX_LEDS, .post_init_device = lp5523_post_init_device, .brightness_fn = lp5523_led_brightness, + .multicolor_brightness_fn = lp5523_multicolor_brightness, .set_led_current = lp5523_set_led_current, .firmware_cb = lp5523_firmware_loaded, .run_engine = lp5523_run_engine,
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 15/18 leds: lp5521: Add multicolor framework multicolor brightness support
In reply to Dan MurphyAdd the multicolor brightness call back to support the multicolor framework. This function allows setting the brightness across grouped LED channels in a single call.
--- drivers/leds/leds-lp5521.c | 20 ++++++++++++++++++++ 1 file changed, 20 insertions(+)
drivers/leds/leds-lp5521.c +20 -0
@@ -349,6 +349,25 @@ static int lp5521_run_selftest(struct lp55xx_chip *chip, char *buf)return 0 ; } +static int lp5521_multicolor_brightness (struct lp55xx_led *led) +{ +struct lp55xx_chip *chip = led->chip; +int ret; +int i; + +mutex_lock (&chip->lock); +for (i =0 ; i < led->mc_cdev.num_leds; i++) { + ret =lp55xx_write (chip, +LP5521_REG_LED_PWM_BASE + + led->color_component[i].output_num, + led->color_component[i].brightness); +if (ret) +break ; + } +mutex_unlock (&chip->lock); +return ret; +} +static int lp5521_led_brightness (struct lp55xx_led *led) {struct lp55xx_chip *chip = led->chip;
@@ -490,6 +509,7 @@ static struct lp55xx_device_config lp5521_cfg = { .max_channel = LP5521_MAX_LEDS, .post_init_device = lp5521_post_init_device, .brightness_fn = lp5521_led_brightness, + .multicolor_brightness_fn = lp5521_multicolor_brightness, .set_led_current = lp5521_set_led_current, .firmware_cb = lp5521_firmware_loaded, .run_engine = lp5521_run_engine,
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 16/18 leds: lp55xx: Fix checkpatch file permissions issues
In reply to Dan MurphyFix the checkpatch warnings for the use of the file permission macros. In converting the file permissions to the DEVICE_ATTR_XX macros the call back function names needed to be updated within the code.
This means that the lp55xx_ needed to be dropped in the name to keep in harmony with the ABI documentation.
--- drivers/leds/leds-lp55xx-common.c | 22 ++++++++++------------ 1 file changed, 10 insertions(+), 12 deletions(-)
drivers/leds/leds-lp55xx-common.c +10 -12
@@ -78,7 +78,7 @@ static int lp55xx_post_init_device(struct lp55xx_chip *chip)return cfg->post_init_device (chip); } -static ssize_t lp55xx_show_current (struct device *dev, +static ssize_t led_current_show (struct device *dev,struct device_attribute *attr,char *buf) {
@@ -87,7 +87,7 @@ static ssize_t lp55xx_show_current(struct device *dev,return scnprintf (buf,PAGE_SIZE ,"%d\n" , led->led_current); } -static ssize_t lp55xx_store_current (struct device *dev, +static ssize_t led_current_store (struct device *dev,struct device_attribute *attr,const char *buf,size_t len) {
@@ -111,7 +111,7 @@ static ssize_t lp55xx_store_current(struct device *dev,return len; } -static ssize_t lp55xx_show_max_current (struct device *dev, +static ssize_t max_current_show (struct device *dev,struct device_attribute *attr,char *buf) {
@@ -120,9 +120,8 @@ static ssize_t lp55xx_show_max_current(struct device *dev,return scnprintf (buf,PAGE_SIZE ,"%d\n" , led->max_current); } -static DEVICE_ATTR(led_current, S_IRUGO | S_IWUSR, lp55xx_show_current, - lp55xx_store_current); -static DEVICE_ATTR(max_current, S_IRUGO , lp55xx_show_max_current, NULL); +static DEVICE_ATTR_RW (led_current); +static DEVICE_ATTR_RO (max_current);static struct attribute *lp55xx_led_attrs[] = { &dev_attr_led_current.attr,
@@ -282,7 +281,7 @@ static int lp55xx_request_firmware(struct lp55xx_chip *chip) GFP_KERNEL, chip, lp55xx_firmware_loaded); } -static ssize_t lp55xx_show_engine_select (struct device *dev, +static ssize_t select_engine_show (struct device *dev,struct device_attribute *attr,char *buf) {
@@ -292,7 +291,7 @@ static ssize_t lp55xx_show_engine_select(struct device *dev,return sprintf (buf,"%d\n" , chip->engine_idx); } -static ssize_t lp55xx_store_engine_select (struct device *dev, +static ssize_t select_engine_store (struct device *dev,struct device_attribute *attr,const char *buf,size_t len) {
@@ -334,7 +333,7 @@ static inline void lp55xx_run_engine(struct lp55xx_chip *chip, bool start) chip->cfg->run_engine (chip, start); } -static ssize_t lp55xx_store_engine_run (struct device *dev, +static ssize_t run_engine_store (struct device *dev,struct device_attribute *attr,const char *buf,size_t len) {
@@ -359,9 +358,8 @@ static ssize_t lp55xx_store_engine_run(struct device *dev,return len; } -static DEVICE_ATTR(select_engine, S_IRUGO | S_IWUSR, - lp55xx_show_engine_select, lp55xx_store_engine_select); -static DEVICE_ATTR(run_engine, S_IWUSR, NULL, lp55xx_store_engine_run); +static DEVICE_ATTR_RW (select_engine); +static DEVICE_ATTR_WO (run_engine);static struct attribute *lp55xx_engine_attributes[] = { &dev_attr_select_engine.attr,
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 17/18 leds: lp5523: Fix checkpatch issues in the code
In reply to Dan MurphyFix checkpatch errors and warnings for the LP5523.c device driver.
--- drivers/leds/leds-lp5523.c | 19 ++++++++++--------- 1 file changed, 10 insertions(+), 9 deletions(-)
drivers/leds/leds-lp5523.c +10 -9
@@ -23,13 +23,13 @@#define LP5523_PROGRAM_LENGTH 32/* bytes */ /* Memory is used like this: -0x00 engine 1 program -0x10 engine 2 program -0x20 engine 3 program -0x30 engine 1 muxing info -0x40 engine 2 muxing info -0x50 engine 3 muxing info -*/ +* 0x00 engine 1 program +* 0x10 engine 2 program +* 0x20 engine 3 program +* 0x30 engine 1 muxing info +* 0x40 engine 2 muxing info +* 0x50 engine 3 muxing info +*/ #define LP5523_MAX_LEDS 9/* Registers */
@@ -326,7 +326,7 @@ static int lp5523_update_program_memory(struct lp55xx_chip *chip, const u8 *data, size_t size) {u8 pattern[LP5523_PROGRAM_LENGTH ] = {0 }; -unsigned cmd; +unsigned int cmd;char c[3 ];int nrchars;int ret;
@@ -468,6 +468,7 @@ static int lp5523_mux_parse(const char *buf, u16 *mux, size_t len)static void lp5523_mux_to_array (u16 led_mux,char *array) {int i, pos =0 ; +for (i =0 ; i <LP5523_MAX_LEDS ; i++) pos +=sprintf (array + pos,"%x" ,LED_ACTIVE (led_mux, i));
@@ -506,7 +507,7 @@ static int lp5523_load_mux(struct lp55xx_chip *chip, u16 mux, int nr)if (ret)return ret; - ret =lp55xx_write (chip,LP5523_REG_PROG_MEM , (u8)(mux >>8 )); + ret =lp55xx_write (chip,LP5523_REG_PROG_MEM , (u8)(mux >>8 ));if (ret)return ret;
Signature · 1 line
2.22.0.214.g8dca754b1e
PATCH v13 18/18 dt: bindings: Update lp55xx binding to recommended LED naming
In reply to Dan MurphyUpdate the LP55xx DT binding examples to the recommended node naming convention. There are no changes to the DT properties.
--- .../devicetree/bindings/leds/leds-lp55xx.txt | 58 +++++++++---------- 1 file changed, 29 insertions(+), 29 deletions(-)
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +29 -29
@@ -48,7 +48,7 @@ example 1) LP5521 'lp5521_pri:channel1' and 'lp5521_pri:channel2', with a heartbeat trigger on channel 0. -lp5521@32 { +led-controller@32 { #address-cells = <1>; #size-cells = <0>; compatible = "national,lp5521";
@@ -56,20 +56,20 @@ lp5521@32 { label = "lp5521_pri"; clock-mode = /bits/ 8 <2>; - chan@0 { + led@0 { reg = <0>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; linux,default-trigger = "heartbeat"; }; - chan@1 { + led@1 { reg = <1>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>; }; - chan@2 { + led@2 { reg = <2>; led-cur = /bits/ 8 <0x2f>; max-cur = /bits/ 8 <0x5f>;
@@ -88,70 +88,70 @@ ASEL1 ASEL0 Address VEN GND 34h VEN VEN 35h -lp5523@32 { +led-controller@32 { #address-cells = <1>; #size-cells = <0>; compatible = "national,lp5523"; reg = <0x32>; clock-mode = /bits/ 8 <1>; - chan@0 { + led@0 { reg = <0>; chan-name = "d1"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@1 { + led@1 { reg = <1>; chan-name = "d2"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@2 { + led@2 { reg = <2>; chan-name = "d3"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@3 { + led@3 { reg = <3>; chan-name = "d4"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@4 { + led@4 { reg = <4>; chan-name = "d5"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@5 { + led@5 { reg = <5>; chan-name = "d6"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@6 { + led@6 { reg = <6>; chan-name = "d7"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@7 { + led@7 { reg = <7>; chan-name = "d8"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@8 { + led@8 { reg = <8>; chan-name = "d9"; led-cur = /bits/ 8 <0x14>;
@@ -162,35 +162,35 @@ lp5523@32 { example 3) LP5562 4 channels are defined. -lp5562@30 { +led-controller@30 { #address-cells = <1>; #size-cells = <0>; compatible = "ti,lp5562"; reg = <0x30>; clock-mode = /bits/8 <2>; - chan@0 { + led@0 { reg = <0>; chan-name = "R"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; }; - chan@1 { + led@1 { reg = <1>; chan-name = "G"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; }; - chan@2 { + led@2 { reg = <2>; chan-name = "B"; led-cur = /bits/ 8 <0x20>; max-cur = /bits/ 8 <0x60>; }; - chan@3 { + led@3 { reg = <3>; chan-name = "W"; led-cur = /bits/ 8 <0x20>;
@@ -202,7 +202,7 @@ example 4) LP8501 9 channels are defined. The 'pwr-sel' is LP8501 specific property. Others are same as LP5523. -lp8501@32 { +led-controller@32 { #address-cells = <1>; #size-cells = <0>; compatible = "ti,lp8501";
@@ -210,63 +210,63 @@ lp8501@32 { clock-mode = /bits/ 8 <2>; pwr-sel = /bits/ 8 <3>; /* D1~9 connected to VOUT */ - chan@0 { + led@0 { reg = <0>; chan-name = "d1"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@1 { + led@1 { reg = <1>; chan-name = "d2"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@2 { + led@2 { reg = <2>; chan-name = "d3"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@3 { + led@3 { reg = <3>; chan-name = "d4"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@4 { + led@4 { reg = <4>; chan-name = "d5"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@5 { + led@5 { reg = <5>; chan-name = "d6"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@6 { + led@6 { reg = <6>; chan-name = "d7"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@7 { + led@7 { reg = <7>; chan-name = "d8"; led-cur = /bits/ 8 <0x14>; max-cur = /bits/ 8 <0x20>; }; - chan@8 { + led@8 { reg = <8>; chan-name = "d9"; led-cur = /bits/ 8 <0x14>;
Signature · 1 line
2.22.0.214.g8dca754b1e