From: Lee Jones <lee@kernel.org>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: Pavel Machek <pavel@ucw.cz>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Steffen Trumtrar <kernel@pengutronix.de>,
Pavel Machek <pavel@kernel.org>, Mark Brown <broonie@kernel.org>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-spi@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v3 2/3] leds: add support for TI LP5860 LED driver chip
Date: Thu, 9 Oct 2025 13:44:27 +0100 [thread overview]
Message-ID: <20251009124427.GC2796410@google.com> (raw)
In-Reply-To: <875xd0jslv.fsf@pengutronix.de>
On Tue, 30 Sep 2025, Steffen Trumtrar wrote:
>
> Hi,
>
> On 2025-09-16 at 16:34 +01, Lee Jones <lee@kernel.org> wrote:
>
> > > +#include <linux/gpio.h>
> > > +#include <linux/led-class-multicolor.h>
> > > +#include <linux/module.h>
> > > +#include <linux/of_gpio.h>
> > > +#include <linux/of_platform.h>
> > > +#include <linux/regmap.h>
> > > +
> > > +#include <linux/platform_data/leds-lp5860.h>
> > > +
> > > +static struct lp5860_led *mcled_cdev_to_led(struct led_classdev_mc *mc_cdev)
> > > +{
> > > + return container_of(mc_cdev, struct lp5860_led, mc_cdev);
> > > +}
> > > +
> > > +LP5860_SHOW_MODE(r_global_brightness_set, LP5860_REG_R_CURRENT_SET, LP5860_CC_GROUP_MASK, 0)
> > > +LP5860_STORE_MODE(r_global_brightness_set, LP5860_REG_R_CURRENT_SET, LP5860_CC_GROUP_MASK, 0)
> > > +DEVICE_ATTR_RW(r_global_brightness_set);
> >
> > How is this different to /sys/class/leds/<led>/multi_intensity?
> >
> > # echo 43 226 138 > /sys/class/leds/multicolor:status/multi_intensity
> > red -
> > intensity = 138
> > max_brightness = 255
> > green -
> > intensity = 43
> > max_brightness = 255
> > blue -
> > intensity = 226
> > max_brightness = 255
> >
>
> the LP5860 has a register for setting the maximal brightness that holds for all LEDs in the matrix. multi_intensity and max_brightness is only for that one multicolor LED, right? And I can only manipulate the max_brightness of that one multicolor LED instance.
> If I'm wrong, I'd be happy to not have to add the sysfs files.
Does group_multicolor help? Or can it be expanded for future similar use-cases?
--
Lee Jones [李琼斯]
next prev parent reply other threads:[~2025-10-09 12:44 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-11 6:59 [PATCH v3 0/3] LED: Add basic LP5860 LED matrix driver Steffen Trumtrar
2025-09-11 6:59 ` [PATCH v3 1/3] dt-bindings: leds: add lp5860 LED controller Steffen Trumtrar
2025-09-15 0:42 ` Rob Herring (Arm)
2025-09-11 6:59 ` [PATCH v3 2/3] leds: add support for TI LP5860 LED driver chip Steffen Trumtrar
2025-09-16 15:34 ` Lee Jones
2025-09-30 7:40 ` Steffen Trumtrar
2025-10-09 12:44 ` Lee Jones [this message]
2025-10-11 13:09 ` Jacek Anaszewski
2025-11-06 7:43 ` Steffen Trumtrar
2025-09-11 6:59 ` [PATCH v3 3/3] Documentation: ABI: add lp5860 led matrix controller Steffen Trumtrar
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=20251009124427.GC2796410@google.com \
--to=lee@kernel.org \
--cc=broonie@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--cc=linux-spi@vger.kernel.org \
--cc=pavel@kernel.org \
--cc=pavel@ucw.cz \
--cc=robh@kernel.org \
--cc=s.trumtrar@pengutronix.de \
/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;
as well as URLs for NNTP newsgroup(s).