linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: pavel@ucw.cz (Pavel Machek)
To: linux-arm-kernel@lists.infradead.org
Subject: [suspend/resume] Re: userspace notification from module
Date: Sun, 17 Jan 2010 14:07:39 +0100	[thread overview]
Message-ID: <20100117130739.GA2035@ucw.cz> (raw)
In-Reply-To: <201001162326.09092.rjw@sisk.pl>


> > That was not the point I was trying to discuss. Yes, we need
> > kernel<->user notification of battery critical. 
> > 
> > But on zaurus, correct action is to suspend (not hibernate and not
> > poweroff) when battery is no longer able to supply enough power to
> > keep system alive.
> 
> Why not to poweroff (just asking, I don't know that hardware)?

Those machines basically have no poweroff.

> I guess we should at least do our best to keep filesystems in a consistent
> state and suspend doesn't really guarantee this if the system remains on
> battery power afterwards.

I'm not sure if I ever had battery run so low that it could not keep
RAM running. Collie has even separate (small) battery just for
RAM. (And it also has all the filesystems in ramdisk -- you really do
not want to power it off, even if it could.)

AFAICT following message would be nice.

1) battery is critical, userspace please do something

On zaurus and similar, you could add

2) oh and btw we had power failure so we suspended (or maybe -- so
hardware suspended itself -- rmk's examples and old apm systems); we
are now back and running

notification... but... ideally those power failures should never
happen anyway, so... having this notification is in no way neccessary.

								Pavel
-- 
(english) http://www.livejournal.com/~pavelmachek
(cesky, pictures) http://atrey.karlin.mff.cuni.cz/~pavel/picture/horses/blog.html

  reply	other threads:[~2010-01-17 13:07 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <686edb2c.6263643a.4b3f4a3b.b60b3@o2.pl>
     [not found] ` <201001022201.04281.rjw@sisk.pl>
     [not found]   ` <20100109103212.GA1429@ucw.cz>
     [not found]     ` <201001091440.46434.rjw@sisk.pl>
2010-01-15 20:03       ` [suspend/resume] Re: userspace notification from module Pavel Machek
2010-01-15 22:14         ` Rafael J. Wysocki
2010-01-16  3:00           ` Eric Miao
2010-01-16 17:00             ` Stanislav Brabec
2010-01-16 18:12               ` Pavel Machek
2010-01-16 22:05                 ` Rafael J. Wysocki
2010-01-16 22:19                   ` Pavel Machek
2010-01-16 22:25                     ` Pavel Machek
2010-01-16 22:31                       ` Rafael J. Wysocki
2010-01-16 22:26                     ` Rafael J. Wysocki
2010-01-17 13:07                       ` Pavel Machek [this message]
2010-01-17 13:26                         ` Russell King - ARM Linux
2010-01-19  5:15                           ` Pavel Machek
2010-01-16 22:32                   ` Russell King - ARM Linux
2010-01-16 18:12             ` Pavel Machek
2010-01-16 18:12           ` Pavel Machek
2010-01-16 22:07             ` Rafael J. Wysocki
2010-01-16 22:14               ` Pavel Machek
2010-01-16 22:21                 ` Rafael J. Wysocki

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=20100117130739.GA2035@ucw.cz \
    --to=pavel@ucw.cz \
    --cc=linux-arm-kernel@lists.infradead.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).