All of lore.kernel.org
 help / color / mirror / Atom feed
From: Russell King <rmk+lkml@arm.linux.org.uk>
To: moreau francis <francis_moreau2000@yahoo.fr>
Cc: linux-pm@lists.osdl.org, linux-kernel@vger.kernel.org
Subject: Re: Re : Re : Re : [HELP] Power management for embedded system
Date: Fri, 25 Aug 2006 14:46:26 +0100	[thread overview]
Message-ID: <20060825134625.GD2287@flint.arm.linux.org.uk> (raw)
In-Reply-To: <20060825133925.47842.qmail@web25810.mail.ukl.yahoo.com>

On Fri, Aug 25, 2006 at 01:39:25PM +0000, moreau francis wrote:
> Russell King wrote:
> > We have some folk who want a method to trigger emergency suspends when
> > batteries got low, or if you move the battery cover, etc.  These are
> > events which require fast reactions from the system, and coding up some
> > additional interface to pass such events to userland, have some daemon
> > running to monitor for those events, and issue a PM event is completely
> > overkill and, actually, unreliable.
> > 
> 
> I'm not sure to understand why a daemon is needed. Could you explain ?

Consider how you would make a connection between an interrupt being
triggered and a suspend occuring, bearing in mind that you require
a process context to perform a suspend.

You essentially have three options:

1. a kernel thread, to which you pass an event or trigger condition.
2. a userland daemon which waits for the interrupt via some special
   kernel interface and triggers a suspend via normal userspace
   channels.
3. some hotplug-triggered userspace method.

Note that both 2 and 3 have the same limitation - since they use normal
userspace channels which have no concept of "emergency suspend", it's
quite possible for (eg) a busy X server to inappropriately delay such a
suspend.

Therefore, I chose (1) as being the most appropriate solution.

-- 
Russell King
 Linux kernel    2.6 ARM Linux   - http://www.arm.linux.org.uk/
 maintainer of:  2.6 Serial core

  reply	other threads:[~2006-08-25 13:46 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 [this message]
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
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=20060825134625.GD2287@flint.arm.linux.org.uk \
    --to=rmk+lkml@arm.linux.org.uk \
    --cc=francis_moreau2000@yahoo.fr \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-pm@lists.osdl.org \
    /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.