linux-kernel - Re : Re : [HELP] Power management for embedded system

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 for Android: free password hash cracker in your pocket

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

Message-ID: <20060825131843.87416.qmail@web25803.mail.ukl.yahoo.com>
Date:	Fri, 25 Aug 2006 13:18:43 +0000 (GMT)
From:	moreau francis <francis_moreau2000@...oo.fr>
To:	Matthew Garrett <mjg59@...f.ucam.org>,
	Richard Purdie <rpurdie@...ys.net>
Cc:	Russell King <rmk+lkml@....linux.org.uk>, linux-pm@...ts.osdl.org,
	linux-kernel@...r.kernel.org
Subject: Re : Re : [HELP] Power management for embedded system

Matthew Garrett wrote:
> Triggering suspend/resume is already generic in the form of the 
> /sys/power/state interface. There's been discussion of producing a 
> generic battery class lately. There's some trend towards tying suspend 
> requests into the input layer, but how appropriate that is may depend on 
> the hardware in question. I think most of the pieces are in place to 
> provide an interface that isn't tied to looking like APM, and there's

what about suspend/resume event handling ? Is there something already in
place ?
 
Francis



-
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/