lists.openwall.net | lists / announce owl-users owl-dev john-users john-dev passwdqc-users yescrypt popa3d-users / oss-security kernel-hardening musl sabotage tlsify passwords / crypt-dev xvendor / Bugtraq Full-Disclosure linux-kernel linux-netdev linux-ext4 linux-hardening PHC | |
Open Source and information security mailing list archives
| ||
|
Date: Sat, 4 Jul 2020 14:17:37 +0200 From: Ondřej Jirman <megous@...ous.com> To: Pavel Machek <pavel@....cz> Cc: linux-kernel@...r.kernel.org, Jacek Anaszewski <jacek.anaszewski@...il.com>, Dan Murphy <dmurphy@...com>, "open list:LED SUBSYSTEM" <linux-leds@...r.kernel.org> Subject: Re: [PATCH RFC] leds: Add support for per-LED device triggers Hello, On Sat, Jul 04, 2020 at 02:04:59PM +0200, Pavel Machek wrote: > Hi! > > > Add support for registering per-LED device trigger. > > > > Names of private triggers need to be globally unique, but may clash > > with other private triggers. This is enforced during trigger > > Globally unique name is going to be a problem, no? If you have two > keyboards with automatical backlight support... Only globally unique in a sense that they must not clash with non per-LED trigger names. So you can have two keyboards with 'self-working' trigger on their LED devices in sysfs. This requirement only comes from the fact that this shares the same sysfs configuration interface as regular non-private triggers. regards, o. > Otherwise... yes, we need something like this. > > Best regards, > Pavel > -- > DENX Software Engineering GmbH, Managing Director: Wolfgang Denk > HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
Powered by blists - more mailing lists