From: Pavel Machek <pavel@ucw.cz>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: moreau francis <francis_moreau2000@yahoo.fr>,
Russell King <rmk+lkml@arm.linux.org.uk>,
linux-kernel@vger.kernel.org, linux-pm@lists.osdl.org
Subject: Re: Re : [HELP] Power management for embedded system
Date: Mon, 4 Sep 2006 23:56:47 +0200 [thread overview]
Message-ID: <20060904215647.GA1975@elf.ucw.cz> (raw)
In-Reply-To: <20060824162034.GB19753@srcf.ucam.org>
Hi!
> > 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
suspend requests into input layer.. No, I do not think Dmitry will
allow us to do that.
Yes, we definitely want some kind of "generic battery" layer.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
WARNING: multiple messages have this Message-ID (diff)
From: Pavel Machek <pavel@ucw.cz>
To: Matthew Garrett <mjg59@srcf.ucam.org>
Cc: Richard Purdie <rpurdie@rpsys.net>,
moreau francis <francis_moreau2000@yahoo.fr>,
Russell King <rmk+lkml@arm.linux.org.uk>,
linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: [linux-pm] Re : [HELP] Power management for embedded system
Date: Mon, 4 Sep 2006 23:56:47 +0200 [thread overview]
Message-ID: <20060904215647.GA1975@elf.ucw.cz> (raw)
In-Reply-To: <20060824162034.GB19753@srcf.ucam.org>
Hi!
> > 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
suspend requests into input layer.. No, I do not think Dmitry will
allow us to do that.
Yes, we definitely want some kind of "generic battery" layer.
Pavel
--
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html
next prev parent reply other threads:[~2006-09-04 21:56 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-08-24 8:44 [HELP] Power management for embedded system moreau francis
2006-08-24 9:04 ` Russell King
2006-08-24 9:37 ` Re : " moreau francis
2006-08-24 10:11 ` Russell King
2006-08-24 10:57 ` Re : " moreau francis
2006-08-24 21:56 ` Russell King
2006-08-25 13:39 ` Re : " moreau francis
2006-08-25 13:46 ` Russell King
2006-08-24 10:12 ` Richard Purdie
2006-08-24 14:42 ` Re : " moreau francis
2006-08-24 16:20 ` Matthew Garrett
2006-08-25 13:18 ` Re : " moreau francis
2006-08-25 13:29 ` Matthew Garrett
2006-08-25 13:29 ` Matthew Garrett
2006-09-04 21:56 ` Pavel Machek [this message]
2006-09-04 21:56 ` [linux-pm] " Pavel Machek
2006-08-24 10:28 ` Ralf Baechle
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20060904215647.GA1975@elf.ucw.cz \
--to=pavel@ucw.cz \
--cc=francis_moreau2000@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.org \
--cc=mjg59@srcf.ucam.org \
--cc=rmk+lkml@arm.linux.org.uk \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.