linux-arm-kernel.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: rjw@sisk.pl (Rafael J. Wysocki)
To: linux-arm-kernel@lists.infradead.org
Subject: [suspend/resume] Re: userspace notification from module
Date: Sat, 16 Jan 2010 23:31:15 +0100	[thread overview]
Message-ID: <201001162331.15405.rjw@sisk.pl> (raw)
In-Reply-To: <20100116222529.GA8618@elf.ucw.cz>

On Saturday 16 January 2010, Pavel Machek wrote:
> > > IMHO it should just plain shutdown in that case.  Suspending doesn't really
> > > solve the problem, because the battery is going to drain still.  Unless you
> > > mean suspend=hibernate, but I guess you don't.
> 
> BTW I was talking spitz before, but there's collie, too. It was
> shipped in configuration where all user data was in RAM and RAMdisk --
> no writable flash. On such machine, shutdown is never option. (And
> yes, such design was very common in windowsCE days).
> 
> Spitz got disk, but inherited that powermanagement design; and it
> works very well.
> 
> And now, if you want collie for a year (or two), you can have
> mine... it still works and battery still lasted for 5 hours 2 years
> ago -- not bad for 10 year old battery. You'll note that it is very
> different design from PC.

Well, I guess I wouldn't have the time to study it anyway, so thanks. :-)

All in all, it looks like these particular platforms are just specific design
having special requirements.  And even on these platforms sending a battery
critical notification to the user space before the kernel emergency suspends
(or shuts down or whatever) the system seems to be a good idea in general.

Rafael

  reply	other threads:[~2010-01-16 22:31 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 [this message]
2010-01-16 22:26                     ` Rafael J. Wysocki
2010-01-17 13:07                       ` Pavel Machek
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=201001162331.15405.rjw@sisk.pl \
    --to=rjw@sisk.pl \
    --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).