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] [thread-next>] [day] [month] [year] [list]
Message-ID: <20060824162034.GB19753@srcf.ucam.org>
Date:	Thu, 24 Aug 2006 17:20:34 +0100
From:	Matthew Garrett <mjg59@...f.ucam.org>
To:	Richard Purdie <rpurdie@...ys.net>
Cc:	moreau francis <francis_moreau2000@...oo.fr>,
	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

On Thu, Aug 24, 2006 at 11:12:05AM +0100, Richard Purdie wrote:

> It would be nice to move that to some arch independent generic
> implementation of these things and to leave the APM emulation behind.
> The battery information should be a sysfs class (see the backlight/led
> classes as examples of sysfs classes). The suspend/resume event handling
> would be something new as far as I know and ideally should support
> suspending/resuming individual sections of device hardware as well as
> the whole system.

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 
certainly one or two moderately compelling reasons to avoid the APM 
emulation limitations.

-- 
Matthew Garrett | mjg59@...f.ucam.org
-
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/

Powered by blists - more mailing lists

Powered by Openwall GNU/*/Linux Powered by OpenVZ