public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Lee Jones <lee@kernel.org>
To: Jonathan Brophy <professorjonny98@gmail.com>
Cc: Pavel Machek <pavel@kernel.org>,
	Andriy Shevencho <andriy.shevchenko@linux.intel.com>,
	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>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-leds@vger.kernel.org
Subject: Re: [PATCH v5 0/7] leds: Add virtual LED group driver with priority arbitration
Date: Tue, 13 Jan 2026 11:57:01 +0000	[thread overview]
Message-ID: <20260113115701.GG1902656@google.com> (raw)
In-Reply-To: <20251230082336.3308403-1-professorjonny98@gmail.com>

On Tue, 30 Dec 2025, Jonathan Brophy wrote:

> From: Jonathan Brophy <professor_jonny@hotmail.com>
> 
> This patch series introduces a new LED driver that implements virtual LED
> groups with priority-based arbitration for shared physical LEDs. The driver
> provides a multicolor LED interface while solving the problem of multiple
> subsystems needing to control the same physical LEDs.
> 
> Key features:
> - Winner-takes-all priority-based arbitration
> - Full multicolor LED ABI compliance
> - Two operating modes (multicolor and standard/fixed-color)
> - Deterministic channel ordering by LED_COLOR_ID
> - Comprehensive debugfs telemetry (when CONFIG_DEBUG_FS enabled)
> - Optimized memory footprint (~200 bytes per LED in production builds)
> 
> Use cases:
> - System status indicators with boot/error/update priority levels
> - RGB lighting with coordinated control
> - Multi-element LED arrays unified into single logical controls
> 
> The series includes:
> 1. New LED function identifier for virtual LEDs
> 2. Device tree bindings for virtual LED class
> 3. Device tree bindings for virtual LED group controller
> 4. ABI documentation for sysfs interface
> 5. Comprehensive driver documentation
> 6. fwnode_led_get() helper for firmware-agnostic LED resolution
> 7. Complete driver implementation
> 
> Changes since v3 commit
> - convert driver to pure fwnode
> - +Multicolor LED ABI compliance - standard multi_intensity/multi_index attributes
> - Winner-takes-all arbitration - deterministic control with sequence-based tie-breaking
> - Proper LED reference management - fwnode_led_get() + led_put() prevents leaks
> - 30% memory reduction - conditional debug compilation
> - Global ownership tracking - prevents conflicts between multiple controllers
> - Hierarchical locking - documented 3-tier lock order prevents deadlocks
> - Lock-free hardware I/O - concurrent vLED updates during physical LED access
> - Dual operating modes - multicolor (dynamic) and standard (fixed-color) modes
> - Pre-allocated arbitration buffers - zero allocations in hot path
> - Comprehensive power management - suspend/resume with runtime PM support
> 
> Changes since v4 commit
> - fix yaml validation errors after feedback from maintainers from LKML
> 
> Additional highlights:
> - Update batching for software PWM workloads
> - Gamma correction for perceptual brightness
> - Rate limiting for runaway updates
> - Extensive debugfs telemetry with stress testing
> - Deferred probe handling for late-probing LEDs
> - Removal race prevention with atomic flags
> 
> Future enhancements planned:
> - dynamic led creation Chardev Interface like uleds
> - ubus/ dbus wrapper for linux and openwrt (out of tree)
> - addressable rgb support WS2812B/SK6812
> - readonly leds for important kernel/ functions
> 
> Testing:
> - Tested on ARM64 platform with GPIO and PWM LEDs
> - Stress tested with 10,000 iterations
> - Validated suspend/resume cycles
> - Memory leak detection passes
> 
> Jonathan Brophy (7):
>   dt-bindings: leds: Add LED_FUNCTION_VIRTUAL_STATUS identifier
>   dt-bindings: leds: Add virtual LED class bindings
>   dt-bindings: leds: Add virtual LED group controller bindings
>   ABI: Add sysfs documentation for leds-group-virtualcolor
>   leds: Add driver documentation for leds-group-virtualcolor
>   leds: Add fwnode_led_get() for firmware-agnostic LED resolution
>   leds: Add virtual LED group driver with priority arbitration
> 
>  .../sysfs-class-led-driver-virtualcolor       |  168 +
>  .../leds/leds-class-virtualcolor.yaml         |  197 +
>  .../leds/leds-group-virtualcolor.yaml         |  170 +
>  .../leds/leds-group-virtualcolor.rst          |  641 ++++
>  drivers/leds/led-class.c                      |  136 +-
>  drivers/leds/leds.h                           |  758 +++-
>  drivers/leds/rgb/Kconfig                      |   17 +
>  drivers/leds/rgb/Makefile                     |    1 +
>  drivers/leds/rgb/leds-group-virtualcolor.c    | 3360 +++++++++++++++++

This is an unreasonable request to ask of any reviewer.  I certainly
don't have the time to go through this in any level of detail.

-- 
Lee Jones [李琼斯]

  parent reply	other threads:[~2026-01-13 11:57 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-12-30  8:23 [PATCH v5 0/7] leds: Add virtual LED group driver with priority arbitration Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 1/7] dt-bindings: leds: add function virtual_status to led common properties Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 2/7] dt-bindings: leds: Add virtual LED class bindings Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 3/7] dt-bindings: leds: Add virtual LED group controller bindings Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 4/7] ABI: Add sysfs documentation for leds-group-virtualcolor Jonathan Brophy
2025-12-30 11:52   ` Andriy Shevencho
2025-12-30  8:23 ` [PATCH v5 5/7] leds: Add driver " Jonathan Brophy
2025-12-30  8:23 ` [PATCH v5 6/7] leds: Add fwnode_led_get() for firmware-agnostic LED resolution Jonathan Brophy
2025-12-30 12:00   ` Andriy Shevencho
2025-12-31  2:30   ` kernel test robot
2025-12-31 23:37   ` kernel test robot
2025-12-31 23:45   ` kernel test robot
2026-01-02 12:20   ` kernel test robot
2026-01-02 15:07   ` kernel test robot
2026-01-02 16:29   ` kernel test robot
2025-12-30  8:23 ` [PATCH v5 7/7] leds: Add virtual LED group driver with priority arbitration Jonathan Brophy
2025-12-30 12:19   ` Andriy Shevencho
2026-01-03  8:22     ` [PATCH v5 7/7] leds: Add virtual LED group driver Jonathan Brophy
2026-01-03 12:56       ` Andriy Shevencho
2026-01-06 16:59 ` [PATCH v5 0/7] leds: Add virtual LED group driver with priority arbitration Rob Herring
2026-01-13 11:52   ` Lee Jones
2026-01-13 11:57 ` Lee Jones [this message]
2026-01-13 20:35   ` Jonathan Brophy
2026-01-15 15:07     ` Lee Jones
2026-01-15 16:58       ` Andriy Shevencho

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=20260113115701.GG1902656@google.com \
    --to=lee@kernel.org \
    --cc=andriy.shevchenko@linux.intel.com \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-leds@vger.kernel.org \
    --cc=pavel@kernel.org \
    --cc=professor_jonny@hotmail.com \
    --cc=professorjonny98@gmail.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