From: Pavel Machek <pavel@suse.cz>
To: "Gross, Mark" <mark.gross@intel.com>
Cc: linux-pm@osdl.org, PMWG@LIST.CELINUXFORUM.ORG,
mli_tech@groups.osdl.org, celinux-dev@tree.celinuxforum.org
Subject: Re: CE Linux Forum PM Requierments WiKi is available for review and comment.
Date: Tue, 21 Mar 2006 21:36:21 +0100 [thread overview]
Message-ID: <20060321203621.GH3929@elf.ucw.cz> (raw)
In-Reply-To: <5389061B65D50446B1783B97DFDB392D13D1B6@orsmsx411.amr.corp.intel.com>
[-- Attachment #1: Type: text/plain, Size: 1797 bytes --]
Hi!
> >4. device power management seems to be missing. What is "OS
> >throttling"?
> >
>
> I'll add some stuff on device power management.
>
> OS throttling is the pacing of work the OS is allowed to do to maintain
> some power or thermal budget constraints.
Hmm, okay, yes, that would be useful for machines that can't do
throttling in hardware.
> >7.1 if your hardware can damage itself or hurt user *FIX YOUR
> >HARDWARE*! Will you argue that overcharging li-ion to explosion is also
> ok?
>
> Having your hardware catch on fire or exploding is not ok. I'll
> re-write this a bit to avoid the inference of buggy hardware. The
> point is that software support is needed to do a good job for some of
> these applications.
>
> However; Having the OS help avoid deep discharging your cell phone or
> I-Pod battery because of some bug would not be unreasonable.
Do li-ion batteries really care about deep discharging in
cellphone/ipod applications? I thought single-li-ion solutions don't
mind being deeply discharged.
(In fact, that's what I'm now doing with li-ion in sharp sl-5500 --
collie; I'm running without any powermanagement, so it dies when
battery can no longer support CPU. I guess that's counts as deep discharge.)
> Neither is having OS support running on hardware that is built without
> active cooling that avoids the HW doing an emergency power off and
> loosing the users data.
NMI watchdog / SMM comes to mind. But SMM is unlikely to be option on
Arm machines.
> >--
> >Thanks, Sharp!
>
> Who the heck is Sharp, and why do you always thank him?
That's a signature... Sharp is Japaneese firm, maybe you've heard
about them :-). Send me handheld computer, and that line becomes
"Thanks, Intel" ;-).
Pavel
--
Picture of sleeping (Linux) penguin wanted...
[-- Attachment #2: Type: text/plain, Size: 0 bytes --]
next prev parent reply other threads:[~2006-03-21 20:36 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2006-03-21 20:09 CE Linux Forum PM Requierments WiKi is available for review and comment Gross, Mark
2006-03-21 20:36 ` Pavel Machek [this message]
-- strict thread matches above, loose matches on Subject: below --
2006-03-21 23:49 Gross, Mark
2006-03-22 9:41 ` Pavel Machek
2006-03-16 16:01 Gross, Mark
2006-03-19 19:22 ` Pavel Machek
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=20060321203621.GH3929@elf.ucw.cz \
--to=pavel@suse.cz \
--cc=PMWG@LIST.CELINUXFORUM.ORG \
--cc=celinux-dev@tree.celinuxforum.org \
--cc=linux-pm@osdl.org \
--cc=mark.gross@intel.com \
--cc=mli_tech@groups.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox