Skip to contentSkip to conversation

Multicolor Framework v12

PATCH Superseded Dan Murphy 3 participants 31 messages Oct 11, 2019 – Oct 21, 2019

Subsystems (4)

v12 of 17 Superseded Latest is v17 →

lore
Share & tools
lore

Dan Murphy

author
#0 lore raw

v12 cover Multicolor Framework v12

Hello

Minor changes per review comments.
https://lore.kernel.org/patchwork/project/lkml/list/?series=413385

Rebased the series on top of Pavel's next branch.

Multicolor changes:
Rename led_mc_calc_brightness to led_mc_calc_color_components Updated the binding example for the function from STATUS to CHARGING

LP50xx changes:
None

LP55xx changes:
Changed color_component array allocation from COLOR_MAX_ID to MAX_GROUPED_CHANNELS Updated MC API to call led_mc_calc_color_components

Dan

Dan Murphy (16):
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: Add multicolor framework support to lp55xx
leds: lp5523: Update the lp5523 code to add intensity function
leds: lp5521: Add multicolor framework intensity support
leds: lp55xx: Fix checkpatch file permissions issues
leds: lp5523: Fix checkpatch issues in the code

 .../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  | 155 +++-
 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                          |  22 +
 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             | 198 ++++-
 drivers/leds/leds-lp55xx-common.h             |   9 +
 include/dt-bindings/leds/common.h             |   3 +-
 include/linux/led-class-multicolor.h          | 143 ++++
 include/linux/platform_data/leds-lp55xx.h     |   7 +
 21 files changed, 2020 insertions(+), 93 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
author
#1 lore raw

PATCH v12 1/16 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
new file mode 100644
index 000000000000..8619c9bf1811
@@ -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_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>;
+		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
author
#2 lore raw

PATCH v12 2/16 dt-bindings: leds: Add multicolor ID to the color ID list

In reply to Dan Murphy

Add 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
index 9e1256a7c1bf..7006d15f71e8 100644
@@ -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
author
#3 lore raw

PATCH v12 3/16 leds: Add multicolor ID to the color ID list

In reply to Dan Murphy

Add 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
index f1f718dbe0f8..846248a0693d 100644
@@ -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
author
#4 lore raw

PATCH v12 4/16 leds: multicolor: Introduce a multicolor class definition

In reply to 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.

---
 .../ABI/testing/sysfs-class-led-multicolor    |  36 +++
 .../bindings/leds/leds-class-multicolor.txt   |   4 +-
 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          | 143 +++++++++
 8 files changed, 560 insertions(+), 2 deletions(-)
 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
new file mode 100644
index 000000000000..3d1f9d726c70
@@ -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/devicetree/bindings/leds/leds-class-multicolor.txt +2 -2
index 8619c9bf1811..4b1bd82f2a42 100644
@@ -10,7 +10,7 @@ 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:
+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.
@@ -26,7 +26,7 @@ led-controller@30 {
 		#size-cells = <0>;
 		reg = <1>;
 		color = <LED_COLOR_ID_MULTI>;
-		function = LED_FUNCTION_STATUS;
+		function = LED_FUNCTION_CHARGING;
 
 
 		led@3 {
Documentation/leds/index.rst +1 -0
index 060f4e485897..bc70c6aa7138 100644
@@ -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
index 4b68520ac251..a1ede89afc9e 100644
@@ -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
index 2da39e896ce8..841038cfe35b 100644
@@ -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 +143 -0

143 lines not on this page · raw message

Signature · 1 line
2.22.0.214.g8dca754b1e
#5 lore raw

Re: [PATCH v12 04/16] leds: multicolor: Introduce a multicolor class definition

Dan,

Quoted 80 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.

---
 .../ABI/testing/sysfs-class-led-multicolor    |  36 +++
 .../bindings/leds/leds-class-multicolor.txt   |   4 +-
 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          | 143 +++++++++
 8 files changed, 560 insertions(+), 2 deletions(-)
 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
new file mode 100644
index 000000000000..3d1f9d726c70
@@ -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/devicetree/bindings/leds/leds-class-multicolor.txt +1 -1
index 8619c9bf1811..4b1bd82f2a42 100644
@@ -10,7 +10,7 @@ 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:
+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.

Documentation/devicetree/bindings/leds/leds-class-multicolor.txt led-controller@30 { · line 30

Quoted 6 lines
Documentation/devicetree/bindings/leds/leds-class-multicolor.txt +1 -1
@@ -26,7 +26,7 @@ led-controller@30 {
 		#size-cells = <0>;
 		reg = <1>;
 		color = <LED_COLOR_ID_MULTI>;
-		function = LED_FUNCTION_STATUS;
+		function = LED_FUNCTION_CHARGING;
 

So this went to wrong patch.

Signature · 2 lines
Best regards,
Jacek Anaszewski
#6 lore raw

Re: [PATCH v12 04/16] leds: multicolor: Introduce a multicolor class definition

In reply to Dan Murphy
I love your patch! Yet something to improve:

Hi Dan,

I love your patch! Yet something to improve:

[auto build test ERROR on j.anaszewski-leds/for-next]
[cannot apply to v5.4-rc3 next-20191011]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Dan-Murphy/Multicolor-Framework-v12/20191014-103058
base:   https://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git for-next
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.4.0

reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=sparc64

If you fix the issue, kindly add following tag

All errors (new ones prefixed by >>):

>> drivers//leds/led-class-multicolor.c:17:5: error: redefinition of 'led_mc_calc_color_components'
    int led_mc_calc_color_components(struct led_classdev_mc *mcled_cdev,
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
   In file included from drivers//leds/led-class-multicolor.c:7:0:
   include/linux/led-class-multicolor.h:119:19: note: previous definition of 'led_mc_calc_color_components' was here
    static inline int led_mc_calc_color_components(struct led_classdev_mc *mcled_cdev,
                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers//leds/led-class-multicolor.c:182:5: error: redefinition of 'led_classdev_multicolor_register_ext'
    int led_classdev_multicolor_register_ext(struct device *parent,
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   In file included from drivers//leds/led-class-multicolor.c:7:0:
   include/linux/led-class-multicolor.h:104:19: note: previous definition of 'led_classdev_multicolor_register_ext' was here
    static inline int led_classdev_multicolor_register_ext(struct device *parent,
                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers//leds/led-class-multicolor.c:204:6: error: redefinition of 'led_classdev_multicolor_unregister'
    void led_classdev_multicolor_unregister(struct led_classdev_mc *mcled_cdev)
         ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   In file included from drivers//leds/led-class-multicolor.c:7:0:
   include/linux/led-class-multicolor.h:117:20: note: previous definition of 'led_classdev_multicolor_unregister' was here
    static inline void led_classdev_multicolor_unregister(struct led_classdev_mc *mcled_cdev) {}
                       ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers//leds/led-class-multicolor.c:224:5: error: redefinition of 'devm_led_classdev_multicolor_register_ext'
    int devm_led_classdev_multicolor_register_ext(struct device *parent,
        ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
   In file included from drivers//leds/led-class-multicolor.c:7:0:
   include/linux/led-class-multicolor.h:126:19: note: previous definition of 'devm_led_classdev_multicolor_register_ext' was here
    static inline int devm_led_classdev_multicolor_register_ext(struct device *parent,
                      ^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>> drivers//leds/led-class-multicolor.c:260:6: error: redefinition of 'devm_led_classdev_multicolor_unregister'

void devm_led_classdev_multicolor_unregister(struct device *dev,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
In file included from drivers//leds/led-class-multicolor.c:7:0:
include/linux/led-class-multicolor.h:139:20: note: previous definition of 'devm_led_classdev_multicolor_unregister' was here
static inline void devm_led_classdev_multicolor_unregister(struct device *parent,
^~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~

vim +/led_mc_calc_color_components +17 drivers//leds/led-class-multicolor.c

    16	
  > 17	int led_mc_calc_color_components(struct led_classdev_mc *mcled_cdev,
    18					 enum led_brightness brightness,
    19				       struct led_mc_color_conversion color_component[])
    20	{
    21		struct led_mc_color_entry *priv;
    22		int i = 0;
    23	
    24		list_for_each_entry(priv, &mcled_cdev->color_list, list) {
    25			color_component[i].color_id = priv->led_color_id;
    26			color_component[i].brightness = brightness *
    27						  priv->intensity / priv->max_intensity;
    28			i++;
    29		}
    30	
    31		return 0;
    32	}
    33	EXPORT_SYMBOL_GPL(led_mc_calc_color_components);
    34	
    35	static ssize_t intensity_store(struct device *dev,
    36					struct device_attribute *intensity_attr,
    37					const char *buf, size_t size)
    38	{
    39		struct led_mc_color_entry *priv = container_of(intensity_attr,
    40							    struct led_mc_color_entry,
    41							      intensity_attr);
    42		struct led_classdev *led_cdev = priv->mcled_cdev->led_cdev;
    43		unsigned long value;
    44		ssize_t ret;
    45	
    46		mutex_lock(&led_cdev->led_access);
    47	
    48		ret = kstrtoul(buf, 10, &value);
    49		if (ret)
    50			goto unlock;
    51	
    52		if (value > priv->max_intensity) {
    53			ret = -EINVAL;
    54			goto unlock;
    55		}
    56	
    57		priv->intensity = value;
    58		ret = size;
    59	
    60	unlock:
    61		mutex_unlock(&led_cdev->led_access);
    62		return ret;
    63	}
    64	
    65	static ssize_t intensity_show(struct device *dev,
    66				      struct device_attribute *intensity_attr,
    67				      char *buf)
    68	{
    69		struct led_mc_color_entry *priv = container_of(intensity_attr,
    70							    struct led_mc_color_entry,
    71							      intensity_attr);
    72	
    73		return sprintf(buf, "%d\n", priv->intensity);
    74	}
    75	
    76	static ssize_t max_intensity_show(struct device *dev,
    77					   struct device_attribute *max_intensity_attr,
    78					   char *buf)
    79	{
    80		struct led_mc_color_entry *priv = container_of(max_intensity_attr,
    81							    struct led_mc_color_entry,
    82							      max_intensity_attr);
    83	
    84		return sprintf(buf, "%d\n", priv->max_intensity);
    85	}
    86	
    87	static struct attribute *led_color_attrs[] = {
    88		NULL,
    89	};
    90	
    91	static struct attribute_group led_color_group = {
    92		.name = "colors",
    93		.attrs = led_color_attrs,
    94	};
    95	
    96	static int led_multicolor_init_color(struct led_classdev_mc *mcled_cdev,
    97					     int color_id)
    98	{
    99		struct led_classdev *led_cdev = mcled_cdev->led_cdev;
   100		struct led_mc_color_entry *mc_priv;
   101		char *intensity_file_name;
   102		char *max_intensity_file_name;
   103		size_t len;
   104		int ret;
   105	
   106		mc_priv = devm_kzalloc(led_cdev->dev, sizeof(*mc_priv), GFP_KERNEL);
   107		if (!mc_priv)
   108			return -ENOMEM;
   109	
   110		mc_priv->led_color_id = color_id;
   111		mc_priv->mcled_cdev = mcled_cdev;
   112	
   113		sysfs_attr_init(&mc_priv->intensity_attr.attr);
   114		len = strlen(led_colors[color_id]) + strlen(INTENSITY_NAME) + 1;
   115		intensity_file_name = kzalloc(len, GFP_KERNEL);
   116		if (!intensity_file_name)
   117			return -ENOMEM;
   118	
   119		snprintf(intensity_file_name, len, "%s%s",
   120			 led_colors[color_id], INTENSITY_NAME);
   121		mc_priv->intensity_attr.attr.name = intensity_file_name;
   122		mc_priv->intensity_attr.attr.mode = 0644;
   123		mc_priv->intensity_attr.store = intensity_store;
   124		mc_priv->intensity_attr.show = intensity_show;
   125		ret = sysfs_add_file_to_group(&led_cdev->dev->kobj,
   126					      &mc_priv->intensity_attr.attr,
   127					      led_color_group.name);
   128		if (ret)
   129			goto intensity_err_out;
   130	
   131		sysfs_attr_init(&mc_priv->max_intensity_attr.attr);
   132		len = strlen(led_colors[color_id]) + strlen(MAX_INTENSITY_NAME) + 1;
   133		max_intensity_file_name = kzalloc(len, GFP_KERNEL);
   134		if (!max_intensity_file_name) {
   135			ret = -ENOMEM;
   136			goto intensity_err_out;
   137		}
   138	
   139		snprintf(max_intensity_file_name, len, "%s%s",
   140			 led_colors[color_id], MAX_INTENSITY_NAME);
   141		mc_priv->max_intensity_attr.attr.name = max_intensity_file_name;
   142		mc_priv->max_intensity_attr.attr.mode = 0444;
   143		mc_priv->max_intensity_attr.show = max_intensity_show;
   144		ret = sysfs_add_file_to_group(&led_cdev->dev->kobj,
   145					      &mc_priv->max_intensity_attr.attr,
   146					      led_color_group.name);
   147		if (ret)
   148			goto max_intensity_err_out;
   149	
   150		mc_priv->max_intensity = LED_FULL;
   151		list_add_tail(&mc_priv->list, &mcled_cdev->color_list);
   152	
   153	max_intensity_err_out:
   154		kfree(max_intensity_file_name);
   155	intensity_err_out:
   156		kfree(intensity_file_name);
   157		return ret;
   158	}
   159	
   160	static int led_multicolor_init_color_dir(struct led_classdev_mc *mcled_cdev)
   161	{
   162		struct led_classdev *led_cdev = mcled_cdev->led_cdev;
   163		int ret;
   164		int i;
   165	
   166		ret = sysfs_create_group(&led_cdev->dev->kobj, &led_color_group);
   167		if (ret)
   168			return ret;
   169	
   170		for (i = 0; i < LED_COLOR_ID_MAX; i++) {
   171			if (test_bit(i, &mcled_cdev->available_colors)) {
   172				ret = led_multicolor_init_color(mcled_cdev, i);
   173				if (ret)
   174					break;
   175	
   176			}
   177		}
   178	
   179		return ret;
   180	}
   181	
 > 182	int led_classdev_multicolor_register_ext(struct device *parent,
   183					     struct led_classdev_mc *mcled_cdev,
   184					     struct led_init_data *init_data)
   185	{
   186		struct led_classdev *led_cdev;
   187		int ret;
   188	
   189		if (!mcled_cdev)
   190			return -EINVAL;
   191	
   192		led_cdev = mcled_cdev->led_cdev;
   193		INIT_LIST_HEAD(&mcled_cdev->color_list);
   194	
   195		/* Register led class device */
   196		ret = led_classdev_register_ext(parent, led_cdev, init_data);
   197		if (ret)
   198			return ret;
   199	
   200		return led_multicolor_init_color_dir(mcled_cdev);
   201	}
   202	EXPORT_SYMBOL_GPL(led_classdev_multicolor_register_ext);
   203	
 > 204	void led_classdev_multicolor_unregister(struct led_classdev_mc *mcled_cdev)

205 {
206 struct led_mc_color_entry *priv, *next;
207
208 if (!mcled_cdev)
209 return;
210
211 list_for_each_entry_safe(priv, next, &mcled_cdev->color_list, list)
212 list_del(&priv->list);
213
214 sysfs_remove_group(&mcled_cdev->led_cdev->dev->kobj, &led_color_group);
215 led_classdev_unregister(mcled_cdev->led_cdev);
216 }
217 EXPORT_SYMBOL_GPL(led_classdev_multicolor_unregister);
218

---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation

author
#7 lore raw

PATCH v12 5/16 dt: bindings: lp50xx: Introduce the lp50xx family of RGB drivers

In reply to Dan Murphy

Introduce 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
new file mode 100644
index 000000000000..8a0a21f1056c
@@ -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
author
#8 lore raw

PATCH v12 6/16 leds: lp50xx: Add the LP50XX family of the RGB LED driver

In reply to Dan Murphy

Introduce 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
index a1ede89afc9e..fb614a6b9afa 100644
@@ -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
index 841038cfe35b..7a208a0f7b84 100644
@@ -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
#9 lore raw

Re: [PATCH v12 06/16] leds: lp50xx: Add the LP50XX family of the RGB LED driver

Dan,

Quoted 58 lines · Dan Murphy

Introduce 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
index a1ede89afc9e..fb614a6b9afa 100644
@@ -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
index 841038cfe35b..7a208a0f7b84 100644
@@ -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 +0 -0

[...]

Quoted 10 lines
drivers/leds/leds-lp50xx.c +10 -0
+		fwnode_for_each_child_node(child, led_node) {
+			ret = fwnode_property_read_u32(led_node, "color",
+						       &color_id);
+			if (ret)
+				dev_err(&priv->client->dev,
+				"Cannot read color\n");
+
+			set_bit(color_id, &led->mc_cdev.available_colors);
+			num_colors++;
+

drivers/leds/leds-lp50xx.c line 680

Quoted 10 lines
drivers/leds/leds-lp50xx.c +10 -0
+		}
+
+		led->priv = priv;
+		led->mc_cdev.num_leds = num_colors;
+		led->mc_cdev.led_cdev = &led->led_dev;
+		led->led_dev.brightness_set_blocking = lp50xx_brightness_set;
+		led->led_dev.brightness_get = lp50xx_brightness_get;
+		ret = led_classdev_multicolor_register_ext(&priv->client->dev,
+						       &led->mc_cdev,
+						       &init_data);

s/led_classdev/devm_led_classdev/

Quoted 13 lines
drivers/leds/leds-lp50xx.c +13 -0
+		if (ret) {
+			dev_err(&priv->client->dev, "led register err: %d\n",
+				ret);
+			fwnode_handle_put(child);
+			goto child_out;
+		}
+		i++;
+	}
+
+child_out:
+	return ret;
+}
+
Signature · 2 lines
Best regards,
Jacek Anaszewski
#10 lore raw

Re: [PATCH v12 06/16] leds: lp50xx: Add the LP50XX family of the RGB LED driver

In reply to Dan Murphy
I love your patch! Yet something to improve:

Hi Dan,

I love your patch! Yet something to improve:

[auto build test ERROR on j.anaszewski-leds/for-next]
[cannot apply to v5.4-rc3 next-20191011]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Dan-Murphy/Multicolor-Framework-v12/20191014-103058
base:   https://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git for-next
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.4.0

reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=sparc64

If you fix the issue, kindly add following tag

All errors (new ones prefixed by >>):

>> drivers//leds/leds-lp50xx.c:360:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5012_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:360:27: note: (near initialization for 'lp50xx_chip_info_tbl[0].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:371:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5012_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:371:27: note: (near initialization for 'lp50xx_chip_info_tbl[1].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:382:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5024_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:382:27: note: (near initialization for 'lp50xx_chip_info_tbl[2].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:393:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5024_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:393:27: note: (near initialization for 'lp50xx_chip_info_tbl[3].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:404:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5036_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:404:27: note: (near initialization for 'lp50xx_chip_info_tbl[4].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:415:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5036_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~

drivers//leds/leds-lp50xx.c:415:27: note: (near initialization for 'lp50xx_chip_info_tbl[5].lp50xx_regmap_config')

vim +360 drivers//leds/leds-lp50xx.c

349
350 static const struct lp50xx_chip_info lp50xx_chip_info_tbl[] = {
351 [LP5009] = {
352 .model_id = LP5009,
353 .max_modules = LP5009_MAX_LED_MODULES,
354 .num_leds = LP5009_MAX_LEDS,
355 .led_brightness0_reg = LP5012_LED0_BRT,
356 .mix_out0_reg = LP5012_OUT0_CLR,
357 .bank_brt_reg = LP5012_BNK_BRT,
358 .bank_mix_reg = LP5012_BNKA_CLR,
359 .reset_reg = LP5012_RESET,

 > 360			.lp50xx_regmap_config = lp5012_regmap_config,

361 },
362 [LP5012] = {
363 .model_id = LP5012,
364 .max_modules = LP5012_MAX_LED_MODULES,
365 .num_leds = LP5012_MAX_LEDS,
366 .led_brightness0_reg = LP5012_LED0_BRT,
367 .mix_out0_reg = LP5012_OUT0_CLR,
368 .bank_brt_reg = LP5012_BNK_BRT,
369 .bank_mix_reg = LP5012_BNKA_CLR,
370 .reset_reg = LP5012_RESET,
371 .lp50xx_regmap_config = lp5012_regmap_config,
372 },
373 [LP5018] = {
374 .model_id = LP5018,
375 .max_modules = LP5018_MAX_LED_MODULES,
376 .num_leds = LP5018_MAX_LEDS,
377 .led_brightness0_reg = LP5024_LED0_BRT,
378 .mix_out0_reg = LP5024_OUT0_CLR,
379 .bank_brt_reg = LP5024_BNK_BRT,
380 .bank_mix_reg = LP5024_BNKA_CLR,
381 .reset_reg = LP5024_RESET,
382 .lp50xx_regmap_config = lp5024_regmap_config,
383 },
384 [LP5024] = {
385 .model_id = LP5024,
386 .max_modules = LP5024_MAX_LED_MODULES,
387 .num_leds = LP5024_MAX_LEDS,
388 .led_brightness0_reg = LP5024_LED0_BRT,
389 .mix_out0_reg = LP5024_OUT0_CLR,
390 .bank_brt_reg = LP5024_BNK_BRT,
391 .bank_mix_reg = LP5024_BNKA_CLR,
392 .reset_reg = LP5024_RESET,
393 .lp50xx_regmap_config = lp5024_regmap_config,
394 },
395 [LP5030] = {
396 .model_id = LP5030,
397 .max_modules = LP5030_MAX_LED_MODULES,
398 .num_leds = LP5030_MAX_LEDS,
399 .led_brightness0_reg = LP5036_LED0_BRT,
400 .mix_out0_reg = LP5036_OUT0_CLR,
401 .bank_brt_reg = LP5036_BNK_BRT,
402 .bank_mix_reg = LP5036_BNKA_CLR,
403 .reset_reg = LP5036_RESET,
404 .lp50xx_regmap_config = lp5036_regmap_config,
405 },
406 [LP5036] = {
407 .model_id = LP5036,
408 .max_modules = LP5036_MAX_LED_MODULES,
409 .num_leds = LP5036_MAX_LEDS,
410 .led_brightness0_reg = LP5036_LED0_BRT,
411 .mix_out0_reg = LP5036_OUT0_CLR,
412 .bank_brt_reg = LP5036_BNK_BRT,
413 .bank_mix_reg = LP5036_BNKA_CLR,
414 .reset_reg = LP5036_RESET,
415 .lp50xx_regmap_config = lp5036_regmap_config,
416 },
417 };
418

---
0-DAY kernel test infrastructure Open Source Technology Center
https://lists.01.org/pipermail/kbuild-all Intel Corporation

#11 lore raw

Re: [PATCH v12 06/16] leds: lp50xx: Add the LP50XX family of the RGB LED driver

Dan,

Below compilation errors are occurring also for v14. Did you compile-test it at least?

Quoted 50 lines · kbuild test robot

Hi Dan,

I love your patch! Yet something to improve:

[auto build test ERROR on j.anaszewski-leds/for-next]
[cannot apply to v5.4-rc3 next-20191011]
[if your patch is applied to the wrong git tree, please drop us a note to help improve the system. BTW, we also suggest to use '--base' option to specify the base tree in git format-patch, please see https://stackoverflow.com/a/37406982]

url:    https://github.com/0day-ci/linux/commits/Dan-Murphy/Multicolor-Framework-v12/20191014-103058
base:   https://git.kernel.org/pub/scm/linux/kernel/git/j.anaszewski/linux-leds.git for-next
config: sparc64-allmodconfig (attached as .config)
compiler: sparc64-linux-gcc (GCC) 7.4.0

reproduce:
wget https://raw.githubusercontent.com/intel/lkp-tests/master/sbin/make.cross -O ~/bin/make.cross chmod +x ~/bin/make.cross
# save the attached .config to linux build tree
GCC_VERSION=7.4.0 make.cross ARCH=sparc64

If you fix the issue, kindly add following tag

All errors (new ones prefixed by >>):

Quoted 1 line
Quoted 1 line

drivers//leds/leds-lp50xx.c:360:27: error: initializer element is not constant

      .lp50xx_regmap_config = lp5012_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:360:27: note: (near initialization for 'lp50xx_chip_info_tbl[0].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:371:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5012_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:371:27: note: (near initialization for 'lp50xx_chip_info_tbl[1].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:382:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5024_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:382:27: note: (near initialization for 'lp50xx_chip_info_tbl[2].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:393:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5024_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:393:27: note: (near initialization for 'lp50xx_chip_info_tbl[3].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:404:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5036_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~
   drivers//leds/leds-lp50xx.c:404:27: note: (near initialization for 'lp50xx_chip_info_tbl[4].lp50xx_regmap_config')
   drivers//leds/leds-lp50xx.c:415:27: error: initializer element is not constant
      .lp50xx_regmap_config = lp5036_regmap_config,
                              ^~~~~~~~~~~~~~~~~~~~

drivers//leds/leds-lp50xx.c:415:27: note: (near initialization for 'lp50xx_chip_info_tbl[5].lp50xx_regmap_config')

Signature · 2 lines
Best regards,
Jacek Anaszewski
author
#12 lore raw

Re: [PATCH v12 06/16] leds: lp50xx: Add the LP50XX family of the RGB LED driver

Jacek

Quoted 4 lines · Jacek Anaszewski

Dan,

Below compilation errors are occurring also for v14. Did you compile-test it at least?

Compile tested and board tested.

Dan

author
#13 lore raw

PATCH v12 7/16 dt: bindings: lp55xx: Be consistent in the document with LED acronym

In reply to Dan Murphy

Update 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
index 1b66a413fb9d..bfe2805c5534 100644
@@ -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
author
#14 lore raw

PATCH v12 8/16 dt: bindings: lp55xx: Update binding for Multicolor Framework

In reply to Dan Murphy

Update the DT binding to include the properties to use the multicolor framework for the devices that use the LP55xx framework.

CC Tony Lindgren <[email protected]>
CC "Benoît Cousson" <[email protected]>
CC Linus Walleij <[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]>
---
 .../devicetree/bindings/leds/leds-lp55xx.txt  | 149 +++++++++++++++---
 1 file changed, 124 insertions(+), 25 deletions(-)
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +124 -25
index bfe2805c5534..736a2e1538be 100644
@@ -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:
+lp5523: lp5523@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
#15 lore raw

Re: [PATCH v12 08/16] dt: bindings: lp55xx: Update binding for Multicolor Framework

Dan,

Quoted 50 lines · Dan Murphy

Update the DT binding to include the properties to use the multicolor framework for the devices that use the LP55xx framework.

CC Tony Lindgren <[email protected]>
CC "Benoît Cousson" <[email protected]>
CC Linus Walleij <[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]>
---
 .../devicetree/bindings/leds/leds-lp55xx.txt  | 149 +++++++++++++++---
 1 file changed, 124 insertions(+), 25 deletions(-)
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +14 -0
index bfe2805c5534..736a2e1538be 100644
@@ -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

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 1) LP5521 · line 51

Quoted 3 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
@@ -35,23 +49,28 @@ example 1) LP5521
 on channel 0.
 
 lp5521@32 {

While at it let's fix node prefix to led-controller. It will not break anyone and yet it will adapt the node naming to what is now recommended.

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 1) LP5521 · line 59

Quoted 9 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +3 -1
+	#address-cells = <1>;
+	#size-cells = <0>;
 	compatible = "national,lp5521";
 	reg = <0x32>;
 	label = "lp5521_pri";
 	clock-mode = /bits/ 8 <2>;
 
-	chan0 {
+	chan@0 {

Similarly in case of every child node:

s/chan/led/

Quoted 20 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +5 -2
+		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>;
 	};

Documentation/devicetree/bindings/leds/leds-lp55xx.txt ASEL1 ASEL0 Address · line 91

Quoted 3 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
@@ -70,59 +89,70 @@ ASEL1    ASEL0    Address
  VEN      VEN       35h
 
 lp5523@32 {

s/lp5523/led-controller/

Quoted 77 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +20 -9
+	#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>;

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 3) LP5562 · line 165

Quoted 3 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
@@ -133,29 +163,35 @@ example 3) LP5562
 4 channels are defined.
 
 lp5562@30 {

s/lp5562/led-controller/

Quoted 37 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +10 -4
+	#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>;

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 4) LP8501 · line 205

Quoted 3 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
@@ -167,62 +203,125 @@ example 4) LP8501
 Others are same as LP5523.
 
 lp8501@32 {

s/lp8501/led-controller/

Quoted 85 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +26 -9
+	#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
+

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 4) LP8501 · line 291

Quoted 10 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +10 -0
+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:
+lp5523: lp5523@32 {

Do you really need "lp5523:" node label ?

Besides:

s/lp5523@32/led-controller@32/

Quoted 37 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +36 -0
+	#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 · 2 lines
Best regards,
Jacek Anaszewski
author
#16 lore raw

Re: [PATCH v12 08/16] dt: bindings: lp55xx: Update binding for Multicolor Framework

Jacek

Quoted 55 lines · Jacek Anaszewski

Dan,

Quoted 52 lines · Dan Murphy

Update the DT binding to include the properties to use the multicolor framework for the devices that use the LP55xx framework.

CC Tony Lindgren <[email protected]>
CC "Benoît Cousson" <[email protected]>
CC Linus Walleij <[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]>
---
  .../devicetree/bindings/leds/leds-lp55xx.txt  | 149 +++++++++++++++---
  1 file changed, 124 insertions(+), 25 deletions(-)
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +14 -0
index bfe2805c5534..736a2e1538be 100644
@@ -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.
 
Quoted 4 lines

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 1) LP5521 · line 51

Quoted 1 line
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
  lp5521@32 {

While at it let's fix node prefix to led-controller. It will not break anyone and yet it will adapt the node naming to what is now recommended.

I would love to do that but honestly I prefer to fix that in a different patch series and not add more changes to this patch review.

Quoted 260 lines

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 1) LP5521 · line 59

Quoted 10 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +3 -1
+	#address-cells = <1>;
+	#size-cells = <0>;
  	compatible = "national,lp5521";
  	reg = <0x32>;
  	label = "lp5521_pri";
  	clock-mode = /bits/ 8 <2>;
 
-	chan0 {
+	chan@0 {

Similarly in case of every child node:

s/chan/led/

Quoted 20 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +5 -2
+		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>;
  	};

Documentation/devicetree/bindings/leds/leds-lp55xx.txt ASEL1 ASEL0 Address · line 91

Quoted 3 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
@@ -70,59 +89,70 @@ ASEL1    ASEL0    Address
   VEN      VEN       35h
 
  lp5523@32 {

s/lp5523/led-controller/

Quoted 77 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +20 -9
+	#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>;

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 3) LP5562 · line 165

Quoted 3 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
@@ -133,29 +163,35 @@ example 3) LP5562
  4 channels are defined.
 
  lp5562@30 {

s/lp5562/led-controller/

Quoted 37 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +10 -4
+	#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>;

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 4) LP8501 · line 205

Quoted 3 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
@@ -167,62 +203,125 @@ example 4) LP8501
  Others are same as LP5523.
 
  lp8501@32 {

s/lp8501/led-controller/

Quoted 85 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +26 -9
+	#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
+

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 4) LP8501 · line 291

Quoted 10 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +10 -0
+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:
+lp5523: lp5523@32 {

Do you really need "lp5523:" node label ?

Quoted 3 lines

Besides:

s/lp5523@32/led-controller@32/

This change I will make since I added this.

Dan

#17 lore raw

Re: [PATCH v12 08/16] dt: bindings: lp55xx: Update binding for Multicolor Framework

Dan,

Quoted 63 lines · Dan Murphy

Jacek

Quoted 51 lines · Jacek Anaszewski

Dan,

Quoted 48 lines · Dan Murphy

Update the DT binding to include the properties to use the multicolor framework for the devices that use the LP55xx framework.

CC Tony Lindgren <[email protected]>
CC "Benoît Cousson" <[email protected]>
CC Linus Walleij <[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]>

---
  .../devicetree/bindings/leds/leds-lp55xx.txt  | 149 +++++++++++++++---

  1 file changed, 124 insertions(+), 25 deletions(-)
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
index bfe2805c5534..736a2e1538be 100644
@@ -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

Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
@@ -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

Quoted 8 lines
Quoted 5 lines

    Optional properties:
  - enable-gpio: GPIO attached to the chip's enable pin

Documentation/devicetree/bindings/leds/leds-lp55xx.txt +0 -0
@@ -35,23 +49,28 @@ example 1) LP5521

  on channel 0.
    lp5521@32 {

While at it let's fix node prefix to led-controller. It will not break anyone and yet it will adapt the node naming to what is now recommended.

Quoted 2 lines

I would love to do that but honestly I prefer to fix that in a different patch series and not add more changes to this patch review.

ack

Quoted 15 lines
Quoted 15 lines
Quoted 8 lines

+    #address-cells = <1>;
+    #size-cells = <0>;
      compatible = "national,lp5521";
      reg = <0x32>;
      label = "lp5521_pri";
      clock-mode = /bits/ 8 <2>;
  -    chan0 {
+    chan@0 {

Similarly in case of every child node:

Documentation/devicetree/bindings/leds/leds-lp55xx.txt example 4) LP8501 · line 291

Quoted 2 lines
Documentation/devicetree/bindings/leds/leds-lp55xx.txt +2 -0
+Multicolor LED example:
+lp5523: lp5523@32 {

Do you really need "lp5523:" node label ?

Quoted 5 lines
Quoted 3 lines

Besides:

s/lp5523@32/led-controller@32/

This change I will make since I added this.

Good, it was the first thing that struck me - if we're adding new bindings they should conform to the current standards.

Signature · 2 lines
Best regards,
Jacek Anaszewski
author
#18 lore raw

PATCH v12 9/16 ARM: dts: n900: Add reg property to the LP5523 channel node

In reply to 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.

CC Tony Lindgren <[email protected]>
CC "Benoît Cousson" <[email protected]>

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
index 84a5ade1e865..643f35619246 100644
@@ -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
author
#19 lore raw

PATCH v12 10/16 ARM: dts: imx6dl-yapp4: Add reg property to the lp5562 channel node

In reply to 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.

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 +10 -4
index e8d800fec637..efc466ed1fea 100644
@@ -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
author
#20 lore raw

PATCH v12 11/16 ARM: dts: ste-href: Add reg property to the LP5521 channel nodes

In reply to 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.

CC Linus Walleij <[email protected]>
---
 arch/arm/boot/dts/ste-href.dtsi | 22 ++++++++++++++++------
 1 file changed, 16 insertions(+), 6 deletions(-)
arch/arm/boot/dts/ste-href.dtsi +16 -6
index 4f6acbd8c040..8a873da102d3 100644
@@ -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
author
#21 lore raw

PATCH v12 12/16 leds: lp55xx: Add multicolor framework support to lp55xx

In reply to Dan Murphy

Add multicolor framework support for the lp55xx family.

---
 drivers/leds/Kconfig                      |   1 +
 drivers/leds/leds-lp55xx-common.c         | 176 +++++++++++++++++++---
 drivers/leds/leds-lp55xx-common.h         |   9 ++
 include/linux/platform_data/leds-lp55xx.h |   7 +
 4 files changed, 169 insertions(+), 24 deletions(-)
drivers/leds/Kconfig +1 -0
index fb614a6b9afa..5706bf8d8bd1 100644
@@ -377,6 +377,7 @@ 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
 	help
drivers/leds/leds-lp55xx-common.c +152 -24

236 lines not on this page · raw message

drivers/leds/leds-lp55xx-common.h +9 -0
index 783ed5103ce5..75d57fb835c3 100644
@@ -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);
 
+	/* access specific brightness register */
+	int (*color_intensity_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
index 96a787100fda..0f9b88019c18 100644
@@ -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
#22 lore raw

Re: [PATCH v12 12/16] leds: lp55xx: Add multicolor framework support to lp55xx

Dan,

Quoted 138 lines · Dan Murphy

Add multicolor framework support for the lp55xx family.

---
 drivers/leds/Kconfig                      |   1 +
 drivers/leds/leds-lp55xx-common.c         | 176 +++++++++++++++++++---
 drivers/leds/leds-lp55xx-common.h         |   9 ++
 include/linux/platform_data/leds-lp55xx.h |   7 +
 4 files changed, 169 insertions(+), 24 deletions(-)
drivers/leds/Kconfig +1 -0
index fb614a6b9afa..5706bf8d8bd1 100644
@@ -377,6 +377,7 @@ 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
 	help
drivers/leds/leds-lp55xx-common.c +68 -8
index 44ced02b49f9..1417df6df8a7 100644
@@ -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) {
+			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;
+	int i;
 
-	led->brightness = (u8)brightness;
-	return cfg->brightness_fn(led);
+	if (led->mc_cdev.num_leds > 1) {
+		if (!cfg->color_intensity_fn)
+			return -EINVAL;
+
+		led_mc_calc_color_components(&led->mc_cdev, brightness,
+					     color_component);
+
+		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->color_intensity_fn(led);
+		if (ret)
+			return ret;
+	} else {
+		led->brightness = (u8)brightness;
+		ret = cfg->brightness_fn(led);
+	}
+
+	return ret;
 }
 
 static int lp55xx_init_led(struct lp55xx_led *led,
@@ -147,9 +187,9 @@ static int lp55xx_init_led(struct lp55xx_led *led,
 	struct lp55xx_platform_data *pdata = chip->pdata;
 	struct lp55xx_device_config *cfg = chip->cfg;
 	struct device *dev = &chip->cl->dev;
+	int max_channel = cfg->max_channel;
 	char name[32];
 	int ret;
-	int max_channel = cfg->max_channel;
 
 	if (chan >= max_channel) {
 		dev_err(dev, "invalid channel: %d / %d\n", chan, max_channel);
@@ -159,10 +199,34 @@ static int lp55xx_init_led(struct lp55xx_led *led,
 	if (pdata->led_config[chan].led_current == 0)
 		return 0;
 
+	if (pdata->led_config[chan].name) {
+		led->cdev.name = pdata->led_config[chan].name;
+	} else {
+		snprintf(name, sizeof(name), "%s:channel%d",
+			pdata->label ? : chip->cl->name, chan);
+		led->cdev.name = name;
+	}
+
+	if (pdata->led_config[chan].num_colors > 1) {
+		led->mc_cdev.led_cdev = &led->cdev;
+		led->cdev.brightness_set_blocking = lp55xx_set_brightness;
+		led->cdev.groups = lp55xx_led_groups;
+		led->mc_cdev.num_leds = pdata->led_config[chan].num_colors;
+		led->mc_cdev.available_colors =
+			pdata->led_config[chan].available_colors;
+		memcpy(led->color_component,
+		       pdata->led_config[chan].color_component,
+		       sizeof(led->color_component));
+	} else {
+
+		led->cdev.default_trigger =
+			pdata->led_config[chan].default_trigger;
+		led->cdev.brightness_set_blocking = lp55xx_set_brightness;
+	}	led->cdev.groups = lp55xx_led_groups;
+
 	led->led_current = pdata->led_config[chan].led_current;
 	led->max_current = pdata->led_config[chan].max_current;
 	led->chan_nr = pdata->led_config[chan].chan_nr;
-	led->cdev.default_trigger = pdata->led_config[chan].default_trigger;
 
 	if (led->chan_nr >= max_channel) {
 		dev_err(dev, "Use channel numbers between 0 and %d\n",
@@ -170,18 +234,11 @@ static int lp55xx_init_led(struct lp55xx_led *led,
 		return -EINVAL;
 	}
 
-	led->cdev.brightness_set_blocking = lp55xx_set_brightness;
-	led->cdev.groups = lp55xx_led_groups;
-
-	if (pdata->led_config[chan].name) {

drivers/leds/leds-lp55xx-common.c static int lp55xx_init_led(struct lp55xx_led *led, · line 240

Quoted 10 lines
drivers/leds/leds-lp55xx-common.c +4 -6
-		led->cdev.name = pdata->led_config[chan].name;
-	} else {
-		snprintf(name, sizeof(name), "%s:channel%d",
-			pdata->label ? : chip->cl->name, chan);
-		led->cdev.name = name;
-	}
+	if (pdata->led_config[chan].num_colors > 1)
+		ret = led_classdev_multicolor_register(dev, &led->mc_cdev);
+	else
+		ret = led_classdev_register(dev, &led->cdev);

Why not devm versions?

drivers/leds/leds-lp55xx-common.c int lp55xx_register_leds(struct lp55xx_led *led, struct lp55xx_chip *chip) · line 469

Quoted 9 lines
drivers/leds/leds-lp55xx-common.c +0 -2
-	ret = led_classdev_register(dev, &led->cdev);
 	if (ret) {
 		dev_err(dev, "led register err: %d\n", ret);
 		return ret;
@@ -466,7 +523,6 @@ int lp55xx_register_leds(struct lp55xx_led *led, struct lp55xx_chip *chip)
 		dev_err(&chip->cl->dev, "empty brightness configuration\n");
 		return -EINVAL;
 	}
-

This empty line removal was not intended I suppose.

Quoted 126 lines
drivers/leds/leds-lp55xx-common.c +80 -8
 	for (i = 0; i < num_channels; i++) {
 
 		/* do not initialize channels that are not connected */
@@ -538,6 +594,82 @@ 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)
+{
+	u32 led_number;
+	int ret;
+
+	of_property_read_string(np, "chan-name",
+				&cfg[chan_num].name);
+	of_property_read_u8(np, "led-cur",
+			    &cfg[chan_num].led_current);
+	of_property_read_u8(np, "max-cur",
+			    &cfg[chan_num].max_current);
+
+	ret = of_property_read_u32(np, "reg", &led_number);
+	if (ret)
+		return ret;
+
+	if (led_number < 0 || led_number > 6)
+		return -EINVAL;
+
+	if (is_multicolor)
+		cfg[chan_num].color_component[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)
+{
+	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);
+
+	ret = of_property_read_u32(np, "color", &channel_color);
+	if (ret)
+		channel_color = 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;
+
+			ret = of_property_read_u32(child, "color", &color_id);
+			if (ret)
+				return ret;
+
+			cfg[child_number].color_component[num_colors].color_id =
+						color_id;
+			set_bit(color_id, &cfg[child_number].available_colors);
+			num_colors++;
+		}
+
+		cfg[child_number].num_colors = num_colors;
+	} else {
+		return lp5xx_parse_common_child(np, cfg, child_number, false,
+						num_colors);
+	}
+
+	return 0;
+}
+
 struct lp55xx_platform_data *lp55xx_of_populate_pdata(struct device *dev,
 						      struct device_node *np)
 {
@@ -546,6 +678,7 @@ struct lp55xx_platform_data *lp55xx_of_populate_pdata(struct device *dev,
 	struct lp55xx_led_config *cfg;
 	int num_channels;
 	int i = 0;
+	int ret;
 
 	pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
 	if (!pdata)
@@ -565,14 +698,9 @@ struct lp55xx_platform_data *lp55xx_of_populate_pdata(struct device *dev,
 	pdata->num_channels = num_channels;
 
 	for_each_child_of_node(np, child) {
-		cfg[i].chan_nr = i;
-
-		of_property_read_string(child, "chan-name", &cfg[i].name);
-		of_property_read_u8(child, "led-cur", &cfg[i].led_current);
-		of_property_read_u8(child, "max-cur", &cfg[i].max_current);
-		cfg[i].default_trigger =
-			of_get_property(child, "linux,default-trigger", NULL);
-
+		ret = lp5xx_parse_channel_child(child, cfg, i);
+		if (ret)
+			return ERR_PTR(-EINVAL);
 		i++;
 	}
 
drivers/leds/leds-lp55xx-common.h +2 -0
index 783ed5103ce5..75d57fb835c3 100644
@@ -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,

drivers/leds/leds-lp55xx-common.h struct lp55xx_device_config { · line 115

Quoted 5 lines
drivers/leds/leds-lp55xx-common.h +2 -0
@@ -109,6 +111,9 @@ struct lp55xx_device_config {
 	/* access brightness register */
 	int (*brightness_fn)(struct lp55xx_led *led);
 
+	/* access specific brightness register */
+	int (*color_intensity_fn)(struct lp55xx_led *led);

Wouldn't multicolor_brightness_fn be more accurate now ?

It is vital to reduce possibility of confusing mc framework intensity with brightness level that is set on each grouped monochrome LED channel.

Quoted 52 lines
drivers/leds/leds-lp55xx-common.h +5 -0
+
 	/* 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
index 96a787100fda..0f9b88019c18 100644
@@ -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 · 2 lines
Best regards,
Jacek Anaszewski
author
#23 lore raw

Re: [PATCH v12 12/16] leds: lp55xx: Add multicolor framework support to lp55xx

Jacek

Quoted 137 lines · Jacek Anaszewski

Dan,

Quoted 134 lines · Dan Murphy

Add multicolor framework support for the lp55xx family.

---
  drivers/leds/Kconfig                      |   1 +
  drivers/leds/leds-lp55xx-common.c         | 176 +++++++++++++++++++---
  drivers/leds/leds-lp55xx-common.h         |   9 ++
  include/linux/platform_data/leds-lp55xx.h |   7 +
  4 files changed, 169 insertions(+), 24 deletions(-)
drivers/leds/Kconfig +1 -0
index fb614a6b9afa..5706bf8d8bd1 100644
@@ -377,6 +377,7 @@ 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
  	help
drivers/leds/leds-lp55xx-common.c +68 -4
index 44ced02b49f9..1417df6df8a7 100644
@@ -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) {
+			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;
+	int i;
 
-	led->brightness = (u8)brightness;
-	return cfg->brightness_fn(led);
+	if (led->mc_cdev.num_leds > 1) {
+		if (!cfg->color_intensity_fn)
+			return -EINVAL;
+
+		led_mc_calc_color_components(&led->mc_cdev, brightness,
+					     color_component);
+
+		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->color_intensity_fn(led);
+		if (ret)
+			return ret;
+	} else {
+		led->brightness = (u8)brightness;
+		ret = cfg->brightness_fn(led);
+	}
+
+	return ret;
  }
 
  static int lp55xx_init_led(struct lp55xx_led *led,
@@ -147,9 +187,9 @@ static int lp55xx_init_led(struct lp55xx_led *led,
  	struct lp55xx_platform_data *pdata = chip->pdata;
  	struct lp55xx_device_config *cfg = chip->cfg;
  	struct device *dev = &chip->cl->dev;
+	int max_channel = cfg->max_channel;
  	char name[32];
  	int ret;
-	int max_channel = cfg->max_channel;
 
  	if (chan >= max_channel) {
  		dev_err(dev, "invalid channel: %d / %d\n", chan, max_channel);
@@ -159,10 +199,34 @@ static int lp55xx_init_led(struct lp55xx_led *led,
  	if (pdata->led_config[chan].led_current == 0)
  		return 0;
 
+	if (pdata->led_config[chan].name) {
+		led->cdev.name = pdata->led_config[chan].name;
+	} else {
+		snprintf(name, sizeof(name), "%s:channel%d",
+			pdata->label ? : chip->cl->name, chan);
+		led->cdev.name = name;
+	}
+
+	if (pdata->led_config[chan].num_colors > 1) {
+		led->mc_cdev.led_cdev = &led->cdev;
+		led->cdev.brightness_set_blocking = lp55xx_set_brightness;
+		led->cdev.groups = lp55xx_led_groups;
+		led->mc_cdev.num_leds = pdata->led_config[chan].num_colors;
+		led->mc_cdev.available_colors =
+			pdata->led_config[chan].available_colors;
+		memcpy(led->color_component,
+		       pdata->led_config[chan].color_component,
+		       sizeof(led->color_component));
+	} else {
+
+		led->cdev.default_trigger =
+			pdata->led_config[chan].default_trigger;
+		led->cdev.brightness_set_blocking = lp55xx_set_brightness;
+	}	led->cdev.groups = lp55xx_led_groups;
+
  	led->led_current = pdata->led_config[chan].led_current;
  	led->max_current = pdata->led_config[chan].max_current;
  	led->chan_nr = pdata->led_config[chan].chan_nr;
-	led->cdev.default_trigger = pdata->led_config[chan].default_trigger;
 
  	if (led->chan_nr >= max_channel) {
  		dev_err(dev, "Use channel numbers between 0 and %d\n",
@@ -170,18 +234,11 @@ static int lp55xx_init_led(struct lp55xx_led *led,
  		return -EINVAL;
  	}
 
Quoted 15 lines
Quoted 4 lines
drivers/leds/leds-lp55xx-common.c +0 -4
-	led->cdev.brightness_set_blocking = lp55xx_set_brightness;
-	led->cdev.groups = lp55xx_led_groups;
-
-	if (pdata->led_config[chan].name) {

drivers/leds/leds-lp55xx-common.c static int lp55xx_init_led(struct lp55xx_led *led, · line 240

Quoted 10 lines
drivers/leds/leds-lp55xx-common.c +4 -6
-		led->cdev.name = pdata->led_config[chan].name;
-	} else {
-		snprintf(name, sizeof(name), "%s:channel%d",
-			pdata->label ? : chip->cl->name, chan);
-		led->cdev.name = name;
-	}
+	if (pdata->led_config[chan].num_colors > 1)
+		ret = led_classdev_multicolor_register(dev, &led->mc_cdev);
+	else
+		ret = led_classdev_register(dev, &led->cdev);

Why not devm versions?

I will change the multicolor but not the led_classdev

Quoted 11 lines

drivers/leds/leds-lp55xx-common.c int lp55xx_register_leds(struct lp55xx_led *led, struct lp55xx_chip *chip) · line 469

Quoted 10 lines
drivers/leds/leds-lp55xx-common.c +0 -2
-	ret = led_classdev_register(dev, &led->cdev);
  	if (ret) {
  		dev_err(dev, "led register err: %d\n", ret);
  		return ret;
@@ -466,7 +523,6 @@ int lp55xx_register_leds(struct lp55xx_led *led, struct lp55xx_chip *chip)
  		dev_err(&chip->cl->dev, "empty brightness configuration\n");
  		return -EINVAL;
  	}
-

This empty line removal was not intended I suppose.

I can put it back

Quoted 130 lines
Quoted 130 lines
drivers/leds/leds-lp55xx-common.c +80 -8
  	for (i = 0; i < num_channels; i++) {
 
  		/* do not initialize channels that are not connected */
@@ -538,6 +594,82 @@ 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)
+{
+	u32 led_number;
+	int ret;
+
+	of_property_read_string(np, "chan-name",
+				&cfg[chan_num].name);
+	of_property_read_u8(np, "led-cur",
+			    &cfg[chan_num].led_current);
+	of_property_read_u8(np, "max-cur",
+			    &cfg[chan_num].max_current);
+
+	ret = of_property_read_u32(np, "reg", &led_number);
+	if (ret)
+		return ret;
+
+	if (led_number < 0 || led_number > 6)
+		return -EINVAL;
+
+	if (is_multicolor)
+		cfg[chan_num].color_component[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)
+{
+	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);
+
+	ret = of_property_read_u32(np, "color", &channel_color);
+	if (ret)
+		channel_color = 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;
+
+			ret = of_property_read_u32(child, "color", &color_id);
+			if (ret)
+				return ret;
+
+			cfg[child_number].color_component[num_colors].color_id =
+						color_id;
+			set_bit(color_id, &cfg[child_number].available_colors);
+			num_colors++;
+		}
+
+		cfg[child_number].num_colors = num_colors;
+	} else {
+		return lp5xx_parse_common_child(np, cfg, child_number, false,
+						num_colors);
+	}
+
+	return 0;
+}
+
  struct lp55xx_platform_data *lp55xx_of_populate_pdata(struct device *dev,
  						      struct device_node *np)
  {
@@ -546,6 +678,7 @@ struct lp55xx_platform_data *lp55xx_of_populate_pdata(struct device *dev,
  	struct lp55xx_led_config *cfg;
  	int num_channels;
  	int i = 0;
+	int ret;
 
  	pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
  	if (!pdata)
@@ -565,14 +698,9 @@ struct lp55xx_platform_data *lp55xx_of_populate_pdata(struct device *dev,
  	pdata->num_channels = num_channels;
 
  	for_each_child_of_node(np, child) {
-		cfg[i].chan_nr = i;
-
-		of_property_read_string(child, "chan-name", &cfg[i].name);
-		of_property_read_u8(child, "led-cur", &cfg[i].led_current);
-		of_property_read_u8(child, "max-cur", &cfg[i].max_current);
-		cfg[i].default_trigger =
-			of_get_property(child, "linux,default-trigger", NULL);
-
+		ret = lp5xx_parse_channel_child(child, cfg, i);
+		if (ret)
+			return ERR_PTR(-EINVAL);
  		i++;
  	}
 
drivers/leds/leds-lp55xx-common.h +2 -0
index 783ed5103ce5..75d57fb835c3 100644
@@ -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);
 
Quoted 3 lines

drivers/leds/leds-lp55xx-common.h struct lp55xx_device_config { · line 115

Quoted 2 lines
drivers/leds/leds-lp55xx-common.h +2 -0
+	/* access specific brightness register */
+	int (*color_intensity_fn)(struct lp55xx_led *led);

Wouldn't multicolor_brightness_fn be more accurate now ?

So just change the name to multicolor_brightness_fn?

Dan

#24 lore raw

Re: [PATCH v12 12/16] leds: lp55xx: Add multicolor framework support to lp55xx

Dan,

Quoted 154 lines · Dan Murphy

Jacek

Quoted 142 lines · Jacek Anaszewski

Dan,

Quoted 139 lines · Dan Murphy

Add multicolor framework support for the lp55xx family.

---
  drivers/leds/Kconfig                      |   1 + drivers/leds/leds-lp55xx-common.c         | 176 +++++++++++++++++++--- drivers/leds/leds-lp55xx-common.h         |   9 ++ include/linux/platform_data/leds-lp55xx.h |   7 +

  4 files changed, 169 insertions(+), 24 deletions(-)
drivers/leds/Kconfig +0 -0
index fb614a6b9afa..5706bf8d8bd1 100644
@@ -377,6 +377,7 @@ 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
      help

drivers/leds/leds-lp55xx-common.c +66 -9
index 44ced02b49f9..1417df6df8a7 100644
@@ -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) {
+            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;
+    int i;
   -    led->brightness = (u8)brightness;
-    return cfg->brightness_fn(led);
+    if (led->mc_cdev.num_leds > 1) {
+        if (!cfg->color_intensity_fn)
+            return -EINVAL;
+
+        led_mc_calc_color_components(&led->mc_cdev, brightness,
+                         color_component);
+
+        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->color_intensity_fn(led);
+        if (ret)
+            return ret;
+    } else {
+        led->brightness = (u8)brightness;
+        ret = cfg->brightness_fn(led);
+    }
+
+    return ret;
   }
     static int lp55xx_init_led(struct lp55xx_led *led,
@@ -147,9 +187,9 @@ static int lp55xx_init_led(struct lp55xx_led *led,
       struct lp55xx_platform_data *pdata = chip->pdata;
       struct lp55xx_device_config *cfg = chip->cfg;
       struct device *dev = &chip->cl->dev;
+    int max_channel = cfg->max_channel;
       char name[32];
       int ret;
-    int max_channel = cfg->max_channel;
         if (chan >= max_channel) {
           dev_err(dev, "invalid channel: %d / %d\n", chan, max_channel);
@@ -159,10 +199,34 @@ static int lp55xx_init_led(struct lp55xx_led *led,
       if (pdata->led_config[chan].led_current == 0)
           return 0;
   +    if (pdata->led_config[chan].name) {
+        led->cdev.name = pdata->led_config[chan].name;
+    } else {
+        snprintf(name, sizeof(name), "%s:channel%d",
+            pdata->label ? : chip->cl->name, chan);
+        led->cdev.name = name;
+    }
+
+    if (pdata->led_config[chan].num_colors > 1) {
+        led->mc_cdev.led_cdev = &led->cdev;
+        led->cdev.brightness_set_blocking = lp55xx_set_brightness;
+        led->cdev.groups = lp55xx_led_groups;
+        led->mc_cdev.num_leds = pdata->led_config[chan].num_colors;
+        led->mc_cdev.available_colors =
+            pdata->led_config[chan].available_colors;
+        memcpy(led->color_component,
+               pdata->led_config[chan].color_component,
+               sizeof(led->color_component));
+    } else {
+
+        led->cdev.default_trigger =
+            pdata->led_config[chan].default_trigger;
+        led->cdev.brightness_set_blocking = lp55xx_set_brightness;
+    }    led->cdev.groups = lp55xx_led_groups;
+
       led->led_current = pdata->led_config[chan].led_current;
       led->max_current = pdata->led_config[chan].max_current;
       led->chan_nr = pdata->led_config[chan].chan_nr;
-    led->cdev.default_trigger =
 pdata->led_config[chan].default_trigger;
         if (led->chan_nr >= max_channel) {
           dev_err(dev, "Use channel numbers between 0 and %d\n",
@@ -170,18 +234,11 @@ static int lp55xx_init_led(struct lp55xx_led *led,
           return -EINVAL;
       }
   -    led->cdev.brightness_set_blocking = lp55xx_set_brightness;
-    led->cdev.groups = lp55xx_led_groups;
-
-    if (pdata->led_config[chan].name) {
-        led->cdev.name = pdata->led_config[chan].name;
-    } else {
-        snprintf(name, sizeof(name), "%s:channel%d",
Quoted 8 lines

drivers/leds/leds-lp55xx-common.c static int lp55xx_init_led(struct lp55xx_led *led, · line 240

Quoted 7 lines
drivers/leds/leds-lp55xx-common.c +4 -3
-            pdata->label ? : chip->cl->name, chan);
-        led->cdev.name = name;
-    }
+    if (pdata->led_config[chan].num_colors > 1)
+        ret = led_classdev_multicolor_register(dev, &led->mc_cdev);
+    else
+        ret = led_classdev_register(dev, &led->cdev);

Why not devm versions?

Quoted 1 line

I will change the multicolor but not the led_classdev

Having one devm and the other not will look awkward.
This does not seem to be a big effort. I propose to add a preceding patch that will first switch monochrome led_classdev_register to devm, and of course clean up error paths (remove lp55xx_unregister_leds()), and update error paths in all callers which will be just removing the calls to lp55xx_unregister_leds().

Quoted 148 lines
Quoted 12 lines

drivers/leds/leds-lp55xx-common.c int lp55xx_register_leds(struct lp55xx_led *led, · line 470

Quoted 11 lines
drivers/leds/leds-lp55xx-common.c +0 -2
-    ret = led_classdev_register(dev, &led->cdev);
       if (ret) {
           dev_err(dev, "led register err: %d\n", ret);
           return ret;
@@ -466,7 +523,6 @@ int lp55xx_register_leds(struct lp55xx_led *led,
 struct lp55xx_chip *chip)
           dev_err(&chip->cl->dev, "empty brightness configuration\n");
           return -EINVAL;
       }
-

This empty line removal was not intended I suppose.

I can put it back

Quoted 123 lines
Quoted 123 lines
drivers/leds/leds-lp55xx-common.c +75 -0
       for (i = 0; i < num_channels; i++) {
             /* do not initialize channels that are not connected */
@@ -538,6 +594,82 @@ 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)
+{
+    u32 led_number;
+    int ret;
+
+    of_property_read_string(np, "chan-name",
+                &cfg[chan_num].name);
+    of_property_read_u8(np, "led-cur",
+                &cfg[chan_num].led_current);
+    of_property_read_u8(np, "max-cur",
+                &cfg[chan_num].max_current);
+
+    ret = of_property_read_u32(np, "reg", &led_number);
+    if (ret)
+        return ret;
+
+    if (led_number < 0 || led_number > 6)
+        return -EINVAL;
+
+    if (is_multicolor)
+        cfg[chan_num].color_component[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)
+{
+    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);
+
+    ret = of_property_read_u32(np, "color", &channel_color);
+    if (ret)
+        channel_color = 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;
+
+            ret = of_property_read_u32(child, "color", &color_id);
+            if (ret)
+                return ret;
+
+            cfg[child_number].color_component[num_colors].color_id =
+                        color_id;
+            set_bit(color_id, &cfg[child_number].available_colors);
+            num_colors++;
+        }
+
+        cfg[child_number].num_colors = num_colors;
+    } else {
+        return lp5xx_parse_common_child(np, cfg, child_number, false,
+                        num_colors);
+    }
+
+    return 0;
+}
+

  struct lp55xx_platform_data *lp55xx_of_populate_pdata(struct device *dev,
                                struct device_node *np)
  {

drivers/leds/leds-lp55xx-common.c +4 -8
@@ -546,6 +678,7 @@ struct lp55xx_platform_data
 *lp55xx_of_populate_pdata(struct device *dev,
       struct lp55xx_led_config *cfg;
       int num_channels;
       int i = 0;
+    int ret;
         pdata = devm_kzalloc(dev, sizeof(*pdata), GFP_KERNEL);
       if (!pdata)
@@ -565,14 +698,9 @@ struct lp55xx_platform_data
 *lp55xx_of_populate_pdata(struct device *dev,
       pdata->num_channels = num_channels;
         for_each_child_of_node(np, child) {
-        cfg[i].chan_nr = i;
-
-        of_property_read_string(child, "chan-name", &cfg[i].name);
-        of_property_read_u8(child, "led-cur", &cfg[i].led_current);
-        of_property_read_u8(child, "max-cur", &cfg[i].max_current);
-        cfg[i].default_trigger =
-            of_get_property(child, "linux,default-trigger", NULL);
-
+        ret = lp5xx_parse_channel_child(child, cfg, i);
+        if (ret)
+            return ERR_PTR(-EINVAL);
           i++;
       }

  diff --git a/drivers/leds/leds-lp55xx-common.h
b/drivers/leds/leds-lp55xx-common.h
index 783ed5103ce5..75d57fb835c3 100644

drivers/leds/leds-lp55xx-common.h +0 -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 {

Quoted 8 lines
Quoted 7 lines

      LP55XX_ENGINE_INVALID,
      LP55XX_ENGINE_1,

drivers/leds/leds-lp55xx-common.h +0 -0
@@ -109,6 +111,9 @@ struct lp55xx_device_config {
       /* access brightness register */
       int (*brightness_fn)(struct lp55xx_led *led);

  +    /* access specific brightness register */ +    int (*color_intensity_fn)(struct lp55xx_led *led);

Wouldn't multicolor_brightness_fn be more accurate now ?

Quoted 1 line

So just change the name to multicolor_brightness_fn?

And the op implementations in the clients, like:

s/lp5521_led_intensity/lp5521_led_mc_brightness/

Signature · 2 lines
Best regards,
Jacek Anaszewski
author
#25 lore raw

PATCH v12 13/16 leds: lp5523: Update the lp5523 code to add intensity function

In reply to Dan Murphy

Add the intensity function call back to support the multicolor framework. This function allows setting a specific brightness on a specific channel.

---
 drivers/leds/leds-lp5523.c | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
drivers/leds/leds-lp5523.c +20 -0
index d0b931a136b9..5d6002e4d657 100644
@@ -791,6 +791,25 @@ static ssize_t store_master_fader_leds(struct device *dev,
 	return ret;
 }
 
+static int lp5523_led_intensity(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,
+	.color_intensity_fn = lp5523_led_intensity,
 	.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
author
#26 lore raw

PATCH v12 14/16 leds: lp5521: Add multicolor framework intensity support

In reply to Dan Murphy

Add the intensity function call back to support the multicolor framework. This function allows setting a specific brightness on a specific channel.

---
 drivers/leds/leds-lp5521.c | 20 ++++++++++++++++++++
 1 file changed, 20 insertions(+)
drivers/leds/leds-lp5521.c +20 -0
index 6f0272249dc8..05731f405c9a 100644
@@ -349,6 +349,25 @@ static int lp5521_run_selftest(struct lp55xx_chip *chip, char *buf)
 	return 0;
 }
 
+static int lp5521_led_intensity(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,
+	.color_intensity_fn = lp5521_led_intensity,
 	.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
author
#27 lore raw

PATCH v12 15/16 leds: lp55xx: Fix checkpatch file permissions issues

In reply to Dan Murphy

Fix 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
index 1417df6df8a7..0d8d1824ea7e 100644
@@ -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
author
#28 lore raw

PATCH v12 16/16 leds: lp5523: Fix checkpatch issues in the code

In reply to Dan Murphy

Fix 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
index 5d6002e4d657..3c7c2e68e137 100644
@@ -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
#29 lore raw
In reply to Dan Murphy

Dan,

Quoted 10 lines · Dan Murphy

Hello

Minor changes per review comments.
https://lore.kernel.org/patchwork/project/lkml/list/?series=413385

Rebased the series on top of Pavel's next branch.

Multicolor changes:
Rename led_mc_calc_brightness to led_mc_calc_color_components Updated the binding example for the function from STATUS to CHARGING

I see STATUS is still there, as well ass "Child".

Quoted 57 lines

LP50xx changes:
None

LP55xx changes:
Changed color_component array allocation from COLOR_MAX_ID to MAX_GROUPED_CHANNELS Updated MC API to call led_mc_calc_color_components

Dan

Dan Murphy (16):
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: Add multicolor framework support to lp55xx
leds: lp5523: Update the lp5523 code to add intensity function
leds: lp5521: Add multicolor framework intensity support
leds: lp55xx: Fix checkpatch file permissions issues
leds: lp5523: Fix checkpatch issues in the code

 .../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  | 155 +++-
 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                          |  22 +
 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             | 198 ++++-
 drivers/leds/leds-lp55xx-common.h             |   9 +
 include/dt-bindings/leds/common.h             |   3 +-
 include/linux/led-class-multicolor.h          | 143 ++++
 include/linux/platform_data/leds-lp55xx.h     |   7 +
 21 files changed, 2020 insertions(+), 93 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 · 2 lines
Best regards,
Jacek Anaszewski
author
#30 lore raw

Jacek

Quoted 8 lines · Jacek Anaszewski

Dan,

Quoted 5 lines · Dan Murphy

Hello

Minor changes per review comments.
https://lore.kernel.org/patchwork/project/lkml/list/?series=413385

Quoted 6 lines
Quoted 5 lines

Rebased the series on top of Pavel's next branch.

Multicolor changes:
Rename led_mc_calc_brightness to led_mc_calc_color_components Updated the binding example for the function from STATUS to CHARGING

I see STATUS is still there, as well ass "Child".

I fixed them they are just in the wrong patch as you pointed out.

Dan