From: Jonathan Brophy <professorjonny98@gmail.com>
To: lee Jones <lee@kernel.org>, Pavel Machek <pavel@kernel.org>,
Jonathan Brophy <professor_jonny@hotmail.com>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Radoslav Tsvetkov <rtsvetkov@gradotech.eu>
Cc: devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-leds@vger.kernel.org
Subject: [PATCH v3 2/4] dt-bindings: leds: Add virtualcolor group dt bindings documentation.
Date: Sun, 19 Oct 2025 22:23:25 +1300 [thread overview]
Message-ID: <20251019092331.49531-3-professorjonny98@gmail.com> (raw)
In-Reply-To: <20251019092331.49531-1-professorjonny98@gmail.com>
From: Jonathan Brophy <professor_jonny@hotmail.com>
Add device tree binding documentation for the virtual LED group driver
that implements virtual LED groups by aggregating multiple monochromatic
LEDs
Bindings for the virtual driver are not describing hardware LEDs they
describe virtual devices made from groups of hardware LEDs created from an array
of LED phandles.
Normally the device tree is used to describe hardware not virtual hardware
but it is particularly useful in situations where you require an LED to be a
specific color by mixing primary colors, such as multi element multi color LEDs
to be operated from a device tree binding.
It also becomes useful with multiple LEDs operating the same indicator such as
ring of light indicators where the LEDs are driven From different GPIO outputs
unifying the control that can give basic indication during system startup,
shutdown upgrade etc...
co-developed-by: Radoslav Tsvetkov <rtsvetkov@gradotech.eu>
Signed-off-by: Radoslav Tsvetkov <rtsvetkov@gradotech.eu>
Signed-off-by: Jonathan Brophy <professor_jonny@hotmail.com>
---
.../leds/leds-group-virtualcolor.yaml | 110 ++++++++++++++++++
1 file changed, 110 insertions(+)
create mode 100644 Documentation/devicetree/bindings/leds/leds-group-virtualcolor.yaml
diff --git a/Documentation/devicetree/bindings/leds/leds-group-virtualcolor.yaml b/Documentation/devicetree/bindings/leds/leds-group-virtualcolor.yaml
new file mode 100644
index 000000000000..f638bdd4d65e
--- /dev/null
+++ b/Documentation/devicetree/bindings/leds/leds-group-virtualcolor.yaml
@@ -0,0 +1,110 @@
+# SPDX-License-Identifier: (GPL-2.0-only OR BSD-2-Clause)
+%YAML 1.2
+---
+$id: http://devicetree.org/schemas/leds/leds-group-virtualcolor.yaml#
+$schema: http://devicetree.org/meta-schemas/core.yaml#
+title: virtualcolor LED group driver
+maintainers:
+ - Radoslav Tsvetkov <rtsvetkov@gradotech.eu>
+description: |
+ Implements virtual LED groups by aggregating multiple monochromatic LEDs.
+ Provides priority-based control for managing concurrent LED activation requests,
+ ensuring only the highest-priority LED state is active at any given time.
+properties:
+ compatible:
+ const: leds-group-virtualcolor
+ '#address-cells':
+ const: 1
+ '#size-cells':
+ const: 0
+patternProperties:
+ "^virtual":
+ $ref: leds-class-virtualcolor.yaml#
+required:
+ - compatible
+additionalProperties: false
+examples:
+ - |
+ #include <dt-bindings/leds/common.h>
+ #include <dt-bindings/gpio/gpio.h>
+
+ led-controller {
+ compatible = "gpio-leds";
+ led_red: led_red {
+ gpios = <&gpio0 10 GPIO_ACTIVE_HIGH>;
+ default-state = "off";
+ };
+ led_green: led_green {
+ gpios = <&gpio0 11 GPIO_ACTIVE_HIGH>;
+ default-state = "off";
+ };
+ led_blue: led_blue {
+ gpios = <&gpio0 12 GPIO_ACTIVE_HIGH>;
+ default-state = "off";
+ };
+ };
+
+ pwm-led-controller {
+ compatible = "pwm-leds";
+
+ led_1: led-1 {
+ color = <LED_COLOR_ID_RED>;
+ pwms = <&twl_pwm 0 7812500>;
+ };
+
+ led_2: led-2 {
+ color = <LED_COLOR_ID_GREEN>;
+ pwms = <&twl_pwmled 0 7812500>;
+ };
+
+ led_3: led-3 {
+ color = <LED_COLOR_ID_RED>;
+ pwms = <&twl_pwm 0 7812500>;
+ };
+
+ led_4: led-4 {
+ color = <LED_COLOR_ID_GREEN>;
+ pwms = <&twl_pwmled 0 7812500>;
+ };
+
+ };
+
+ virtual-led-controller {
+ compatible = "leds-group-virtualcolor";
+ #address-cells = <1>;
+ #size-cells = <0>;
+
+ virtual_red@0 {
+ reg = <0>;
+ function = LED_FUNCTION_VIRTUAL_STATUS;
+ color = <LED_COLOR_ID_RED>;
+ leds = <&led_red>;
+ priority = <2>;
+ };
+
+ virtual_yellow_mix@1 {
+ reg = <1>;
+ function = LED_FUNCTION_VIRTUAL_STATUS;
+ color = <LED_COLOR_ID_YELLOW>;
+ leds = <&led_green &led_red>;
+ pwm-leds-red = <&led_1 &led_2>;
+ pwm-leds-green = <&led_1 &led_3>;
+ priority = <1>;
+ };
+
+ virtual_white@2 {
+ reg = <2>;
+ function = LED_FUNCTION_VIRTUAL_STATUS;
+ color = <LED_COLOR_ID_WHITE>;
+ leds = <&led_red &led_green &led_blue>;
+ priority = <15>;
+ };
+
+ virtual_pwm_red@3 {
+ reg = <3>;
+ function = LED_FUNCTION_VIRTUAL_STATUS;
+ color = <LED_COLOR_ID_RED>;
+ pwm-leds-red = <&led_1 &led_3>;
+ priority = <1>;
+ };
+ };
--
2.43.0
next prev parent reply other threads:[~2025-10-19 9:24 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-19 9:23 [PATCH v3 0/4] leds: Add a virtual LED driver for groups of Jonathan Brophy
2025-10-19 9:23 ` [PATCH v3 1/4] dt: bindings: Add virtualcolor class dt bindings documentation Jonathan Brophy
2025-10-19 10:39 ` Krzysztof Kozlowski
2025-10-19 9:23 ` Jonathan Brophy [this message]
2025-10-19 10:43 ` [PATCH v3 2/4] dt-bindings: leds: Add virtualcolor group " Krzysztof Kozlowski
2025-10-20 11:35 ` Rob Herring (Arm)
2025-10-20 18:00 ` jonathan brophy
2025-10-19 9:23 ` [PATCH v3 3/4] ABI: Add sysfs documentation for leds-group-virtualcolor Jonathan Brophy
2025-10-19 9:23 ` [PATCH v3 4/4] leds: Add virtualcolor LED group driver Jonathan Brophy
2025-10-20 3:29 ` kernel test robot
2025-10-22 16:19 ` Nathan Chancellor
2025-10-20 7:13 ` Dan Carpenter
2025-10-20 17:40 ` Jonathan Brophy
2025-11-30 22:46 ` Jonathan Brophy
2025-10-19 14:24 ` [PATCH v3 0/4] leds: Add a virtual LED driver for groups of Jacek Anaszewski
2025-10-20 8:40 ` Alexander Dahl
2025-10-20 18:56 ` jonathan brophy
[not found] ` <DS0PR84MB37465DFAA8E8994B503A69829FF4A@DS0PR84MB3746.NAMPRD84.PROD.OUTLOOK.COM>
2025-10-20 18:57 ` Jacek Anaszewski
2025-10-20 21:45 ` professorjonny98
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20251019092331.49531-3-professorjonny98@gmail.com \
--to=professorjonny98@gmail.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=professor_jonny@hotmail.com \
--cc=robh@kernel.org \
--cc=rtsvetkov@gradotech.eu \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox