From: Matthew Garrett <mjg59@srcf.ucam.org>
To: moreau francis <francis_moreau2000@yahoo.fr>
Cc: linux-pm@lists.osdl.org, Russell King <rmk+lkml@arm.linux.org.uk>,
linux-kernel@vger.kernel.org
Subject: Re: Re : Re : [HELP] Power management for embedded system
Date: Fri, 25 Aug 2006 14:29:19 +0100 [thread overview]
Message-ID: <20060825132919.GA12370@srcf.ucam.org> (raw)
In-Reply-To: <20060825131843.87416.qmail@web25803.mail.ukl.yahoo.com>
On Fri, Aug 25, 2006 at 01:18:43PM +0000, moreau francis wrote:
> 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 ?
You mean passing those events out to userspace? Not that I know of.
--
Matthew Garrett | mjg59@srcf.ucam.org
WARNING: multiple messages have this Message-ID (diff)
From: Matthew Garrett <mjg59@srcf.ucam.org>
To: moreau francis <francis_moreau2000@yahoo.fr>
Cc: Richard Purdie <rpurdie@rpsys.net>,
Russell King <rmk+lkml@arm.linux.org.uk>,
linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Re : Re : [HELP] Power management for embedded system
Date: Fri, 25 Aug 2006 14:29:19 +0100 [thread overview]
Message-ID: <20060825132919.GA12370@srcf.ucam.org> (raw)
In-Reply-To: <20060825131843.87416.qmail@web25803.mail.ukl.yahoo.com>
On Fri, Aug 25, 2006 at 01:18:43PM +0000, moreau francis wrote:
> 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 ?
You mean passing those events out to userspace? Not that I know of.
--
Matthew Garrett | mjg59@srcf.ucam.org
next prev parent reply other threads:[~2006-08-25 13:29 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 [this message]
2006-08-25 13:29 ` Matthew Garrett
2006-09-04 21:56 ` Pavel Machek
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=20060825132919.GA12370@srcf.ucam.org \
--to=mjg59@srcf.ucam.org \
--cc=francis_moreau2000@yahoo.fr \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@lists.osdl.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.