devicetree.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Steffen Trumtrar <s.trumtrar@pengutronix.de>
To: Pavel Machek <pavel@ucw.cz>
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 0/2] LED: Add basic LP5860 LED matrix driver
Date: Thu, 20 Feb 2025 15:11:22 +0100	[thread overview]
Message-ID: <87zfigaeph.fsf@pengutronix.de> (raw)
In-Reply-To: <20250220-v6-14-topic-ti-lp5860-v1-0-42874bdc7513@pengutronix.de> (Steffen Trumtrar's message of "Thu, 20 Feb 2025 13:57:55 +0100")


Hi,

On 2025-02-20 at 13:57 +01, Steffen Trumtrar <s.trumtrar@pengutronix.de> wrote:

> The lp5860 is a LED matrix driver with 18 constant current sinks and 11
> scan switches which allows controlling up to 198 LED dots.
>
> This series adds just the basic support for the device on the SPI bus.
> It is also possible to use it on I2C. The interface can be
> switched/selected via an interface select pin.
>
> Next step for this driver will be adding open and short detection of the
> LEDs.

for this next step I wonder what would be the best way to propagate the failure states of the LED to the userspace? As far as I can tell, there are already TI LED drivers (lp55xx) that check open and short failures. These drivers only emit failures via sysfs_emit.
I need to be able to tell from userspace if an LED that is supposed to show some state info isn't broken in hardware.

Any ideas welcome,

Thanks,
Steffen

--
Pengutronix e.K.                | Dipl.-Inform. Steffen Trumtrar |
Steuerwalder Str. 21            | https://www.pengutronix.de/    |
31137 Hildesheim, Germany       | Phone: +49-5121-206917-0       |
Amtsgericht Hildesheim, HRA 2686| Fax:   +49-5121-206917-5555    |

      parent reply	other threads:[~2025-02-20 14:11 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-02-20 12:57 [PATCH 0/2] LED: Add basic LP5860 LED matrix driver Steffen Trumtrar
2025-02-20 12:57 ` [PATCH 1/2] dt-bindings: leds: add lp5860 LED controller Steffen Trumtrar
2025-02-20 17:03   ` Conor Dooley
2025-02-20 12:57 ` [PATCH 2/2] leds: add support for TI LP5860 LED driver chip Steffen Trumtrar
2025-02-21  8:42   ` Krzysztof Kozlowski
2025-02-20 14:11 ` Steffen Trumtrar [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=87zfigaeph.fsf@pengutronix.de \
    --to=s.trumtrar@pengutronix.de \
    --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=pavel@ucw.cz \
    --cc=robh@kernel.org \
    /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).