From: Andrew Morton <akpm@osdl.org>
To: Todd Poynor <tpoynor@mvista.com>
Cc: zwane@linuxpower.ca, kenneth.w.chen@intel.com,
linux-ia64@vger.kernel.org, linux-kernel@vger.kernel.org,
cpufreq@www.linux.org.uk
Subject: Re: add lowpower_idle sysctl
Date: Fri, 19 Mar 2004 00:09:13 +0000 [thread overview]
Message-ID: <20040318160913.5915281d.akpm@osdl.org> (raw)
In-Reply-To: <405A29EA.6000400@mvista.com>
Todd Poynor <tpoynor@mvista.com> wrote:
>
> Zwane Mwaikambo wrote:
>
> >>Set some system-wide integer via a sysctl and let the particular
> >>architecture decide how best to implement the currently-selected idle mode?
> >
> > I'm wondering whether the setting of these magic numbers can't be done
> > using cpufreq infrastructure.
>
> I'd vote for using Patrick Mochel's PM subsystem and use a standard set
> of identifiers that are mapped to a platform-specific idle behavior, in
> much the same way as platform suspend modes are handled today. For
> example, strings echoed to /sys/power/idle could be an interface. If
> folks are amenable to this I'd be happy to supply a (generic) patch for it.
That sounds suitable, thanks.
next prev parent reply other threads:[~2004-03-19 0:09 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-03-18 0:31 add lowpower_idle sysctl Kenneth Chen
2004-03-18 1:04 ` Andrew Morton
2004-03-18 3:18 ` Kenneth Chen
2004-03-18 3:28 ` Andrew Morton
2004-03-18 3:40 ` Zwane Mwaikambo
2004-03-18 9:05 ` Dominik Brodowski
2004-03-18 22:59 ` Todd Poynor
2004-03-19 0:09 ` Andrew Morton [this message]
2004-03-19 0:43 ` Zwane Mwaikambo
2004-03-18 18:29 ` Kenneth Chen
2004-03-18 21:59 ` Kenneth Chen
2004-03-18 22:35 ` Andrew Morton
2004-03-24 9:54 ` Pavel Machek
2004-03-23 9:56 ` Pavel Machek
2004-03-25 19:04 ` Chen, Kenneth W
2004-03-25 19:20 ` Chen, Kenneth W
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=20040318160913.5915281d.akpm@osdl.org \
--to=akpm@osdl.org \
--cc=cpufreq@www.linux.org.uk \
--cc=kenneth.w.chen@intel.com \
--cc=linux-ia64@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=tpoynor@mvista.com \
--cc=zwane@linuxpower.ca \
/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