linux-kernel - 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-next>] [day] [month] [year] [list]

Message-ID: <20091111180718.GH3495@enneenne.com>
Date:	Wed, 11 Nov 2009 19:07:18 +0100
From:	Rodolfo Giometti <giometti@...eenne.com>
To:	Richard Purdie <rpurdie@...ys.net>
Cc:	linux-kernel@...r.kernel.org
Subject: Defining led's triggers as separate class

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.

Thanks for your suggestions,

Rodolfo

-- 

GNU/Linux Solutions                  e-mail: giometti@...eenne.com
Linux Device Driver                          giometti@...ux.it
Embedded Systems                     phone:  +39 349 2432127
UNIX programming                     skype:  rodolfo.giometti
Freelance ICT Italia - Consulente ICT Italia - www.consulenti-ict.it
--
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/