[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20190901172323.GB1005@bug>
Date: Sun, 1 Sep 2019 19:23:23 +0200
From: Pavel Machek <pavel@....cz>
To: Akinobu Mita <akinobu.mita@...il.com>
Cc: linux-leds@...r.kernel.org, linux-kernel@...r.kernel.org,
Jacek Anaszewski <jacek.anaszewski@...il.com>,
Dan Murphy <dmurphy@...com>
Subject: Re: [PATCH] leds: remove PAGE_SIZE limit of
/sys/class/leds/<led>/trigger
Hi!
> Reading /sys/class/leds/<led>/trigger returns all available LED triggers.
> However, the size of this file is limited to PAGE_SIZE because of the
> limitation for sysfs attribute.
>
> Enabling LED CPU trigger on systems with thousands of CPUs easily hits
> PAGE_SIZE limit, and makes it impossible to see all available LED triggers
> and which trigger is currently activated.
>
> This converts /sys/class/leds/<led>/trigger to bin attribute and removes
> the PAGE_SIZE limitation.
>
> Cc: Jacek Anaszewski <jacek.anaszewski@...il.com>
Nothing obviously wrong from a quick look...
Acked-by: Pavel Machek <pavel@....cz>
Thanks a lot for doing this!
I believe we should cc Greg here.
BTW if you care about cpuled trigger... it would be cool to turn it into one trigger and pass
a cpu number as a parameter. It is good to see this limit fixed, but real solution is to
register one trigger per driver.
Best regards,
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
Powered by blists - more mailing lists