From: Pavel Machek <pavel@ucw.cz>
To: Steffen Trumtrar <s.trumtrar@pengutronix.de>
Cc: Lee Jones <lee@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Steffen Trumtrar <kernel@pengutronix.de>,
linux-leds@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/4] LED: Add basic LP5860 LED matrix driver
Date: Fri, 23 May 2025 13:53:35 +0200 [thread overview]
Message-ID: <aDBhv2fhMVUXNaqV@duo.ucw.cz> (raw)
In-Reply-To: <20250514-v6-14-topic-ti-lp5860-v2-0-72ecc8fa4ad7@pengutronix.de>
[-- Attachment #1: Type: text/plain, Size: 514 bytes --]
Hi!
> The lp5860 is a LED matrix driver with 18 constant current sinks and 11
> scan switches which allows controlling up to 198 LED dots.
200 points. Is it likely to be used as individual LEDs?
> Documentation/ABI/testing/sysfs-class-spi-lp5860 | 73 ++++
I'm not big fan of new ABI. Should currents / per channel dimming be
configured from dts (and not sysfs)?
Best regards,
Pavel
--
I don't work for Nazis and criminals, and neither should you.
Boycott Putin, Trump, and Musk!
[-- Attachment #2: signature.asc --]
[-- Type: application/pgp-signature, Size: 195 bytes --]
prev parent reply other threads:[~2025-05-23 11:53 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-14 10:36 [PATCH v2 0/4] LED: Add basic LP5860 LED matrix driver Steffen Trumtrar
2025-05-14 10:36 ` [PATCH v2 1/4] dt-bindings: leds: add lp5860 LED controller Steffen Trumtrar
2025-05-21 9:02 ` Krzysztof Kozlowski
2025-05-14 10:36 ` [PATCH v2 2/4] leds: add support for TI LP5860 LED driver chip Steffen Trumtrar
2025-05-23 10:28 ` Lee Jones
2025-07-14 8:26 ` Steffen Trumtrar
2025-07-18 13:18 ` Lee Jones
2025-05-14 10:36 ` [PATCH v2 3/4] leds: lp5860: save count of multi_leds Steffen Trumtrar
2025-06-12 13:52 ` Lee Jones
2025-05-14 10:36 ` [PATCH v2 4/4] leds: lp5860: detect and report fault state Steffen Trumtrar
2025-05-23 11:53 ` Pavel Machek [this message]
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=aDBhv2fhMVUXNaqV@duo.ucw.cz \
--to=pavel@ucw.cz \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=kernel@pengutronix.de \
--cc=krzk+dt@kernel.org \
--cc=lee@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-leds@vger.kernel.org \
--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).