linux-kernel - Re: Defining led's triggers as separate class

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 linux-cve-announce PHC
Open Source and information security mailing list archives

Hash Suite: Windows password security audit tool. GUI, reports in PDF.

[<prev] [next>] [<thread-prev] [day] [month] [year] [list]

Message-ID: <20091121191319.GD2444@ucw.cz>
Date:	Sat, 21 Nov 2009 20:13:19 +0100
From:	Pavel Machek <pavel@....cz>
To:	Richard Purdie <rpurdie@...ys.net>, linux-kernel@...r.kernel.org
Subject: Re: Defining led's triggers as separate class

On Wed 2009-11-11 19:07:18, Rodolfo Giometti wrote:
> Hello,
> 
> it could be sane moving triggers core from leds directory and defining
> them as a separate class in order to be used by other subsystem?
> 
> For instance I have a voltage regulator (which should be logically
> implemented into current regulator class) who must be enabled/disabled
> when the LCD is turned on/off... if the driver was implemented as led
> class then I can use the trigger ledtrig-backlight.c but as regulator
> I can not.

Well, and then user does echo 'hddactivity' > trigger, and your
voltage regulator will have some fun?
								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
--
To unsubscribe from this list: send the line "unsubscribe linux-kernel" in
the body of a message to majordomo@...r.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html
Please read the FAQ at  http://www.tux.org/lkml/