[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <aXVT8AzgHbr8tbsT@ucw.cz>
Date: Sun, 25 Jan 2026 00:21:20 +0100
From: Pavel Machek <pavel@....cz>
To: 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>,
Niklas Cassel <cassel@...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>,
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
Hi!
> Extend the disk trigger
> - to allow configuration of the blinking delays
> and whether the led should be kept on, on idle.
> - to allow an individual led to be mapped to an ata port
I have used led trigger before, and it annoyed me than "constant disk
activity" resulted in "constant LED blinking" instead of "LED
constantly on". I would not mind if that was fixed.
Thanks and best regards,
Pavel
Powered by blists - more mailing lists