[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <03a91568-d1a0-4779-a465-2788f4765a42@gmail.com>
Date: Mon, 26 Jan 2026 10:19:07 -0600
From: Ian Pilcher <arequipeno@...il.com>
To: Niklas Cassel <cassel@...nel.org>, Markus Probst <markus.probst@...teo.de>
Cc: Lee Jones <lee@...nel.org>, Pavel Machek <pavel@...nel.org>,
Rob Herring <robh@...nel.org>, Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Damien Le Moal <dlemoal@...nel.org>, John Garry <john.g.garry@...cle.com>,
Jason Yan <yanaijie@...wei.com>,
"James E.J. Bottomley" <James.Bottomley@...senpartnership.com>,
"Martin K. Petersen" <martin.petersen@...cle.com>,
Pavel Machek <pavel@....cz>, linux-leds@...r.kernel.org,
devicetree@...r.kernel.org, linux-kernel@...r.kernel.org,
linux-ide@...r.kernel.org, linux-scsi@...r.kernel.org
Subject: Re: [PATCH RFC 0/4] leds: extend disk trigger
On 1/26/26 3:00 AM, Niklas Cassel wrote:
> But I'm not a fan of making the driver more complex.
> If we want something more complex than what is already there, then it
> is probably much better handled in user space, considering the amount
> of possible configuration options.
>
> Basically the same argument as used in:
> https://lore.kernel.org/linux-nvme/20220227234258.24619-1-ematsumiya@suse.de/T/#u
Niklas -
Can you provide some links on how this might be done in userspace?
I've been maintaining my out-of-tree block device trigger for years, to
make the LEDs on my NAS work.
https://github.com/ipilcher/ledtrig-blkdev/blob/v6.9%2B/drivers/leds/trigger/ledtrig-blkdev.c
I'd love to be able to replace it with something in-tree.
--
========================================================================
If your user interface is intuitive in retrospect ... it isn't intuitive
========================================================================
Powered by blists - more mailing lists