From: Johnathan Hicks <thetech-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
To: acpi-devel
<acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org>
Subject: Re: An embedded-Linux power-management framework
Date: Fri, 02 Aug 2002 20:48:15 -0400 [thread overview]
Message-ID: <3D4B284F.20402@folkwolf.net> (raw)
In-Reply-To: 1028330951.31733.5.camel@irongate.swansea.linux.org.uk
Alan Cox wrote:
> On Fri, 2002-08-02 at 19:20, Hollis Blanchard wrote:
>
>>There are situations (especially in dedicated-purpose devices running
>>only a few hand-written applications) in which it helps to change some
>>of these values without changing the others. Changing them all according
>>to a single variable (CPU core frequency) could be very limiting. To my
>>knowledge the cpufreq code also does not allow for this flexibility, but
>>certainly it would be nice to add it.
>
>
> So improve the cpufreq code to be a bit more controllable. Its the right
> framework. It also needs a littlw tweaking for the cases where we change
> STPCLK on x86's.
Are you sure that cpufreq should be tweaked to manage STPCLK? Would it not
make more sence to suck cpufreq into ACPI and call it during Tx (throttling)
states if applicable? Of course I realise that might not be allowed by the
ACPI spec, but some combination of cqufreq and the Tx states is a good idea...
and optional for the user.
--John
--John
-------------------------------------------------------
This sf.net email is sponsored by:ThinkGeek
Welcome to geek heaven.
http://thinkgeek.com/sf
next prev parent reply other threads:[~2002-08-03 0:48 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2002-08-02 17:28 An embedded-Linux power-management framework Robert C. Paulsen Jr.
[not found] ` <20020802172802.GA32612-o5m52qS82XggC06IV0sn5h2eb7JE58TQ@public.gmane.org>
2002-08-02 19:11 ` Alan Cox
[not found] ` <1028315477.18635.113.camel-MMxVpc8zpTQVh3rx8e9g/fyykp6/JSeS3vcXtXqGYxw@public.gmane.org>
2002-08-02 18:20 ` Hollis Blanchard
[not found] ` <1028312475.23390.63.camel-j9xLUTenKzJXsEFxtoW7CMxtgHpCUUYS@public.gmane.org>
2002-08-02 23:29 ` Alan Cox
2002-08-03 0:48 ` Johnathan Hicks [this message]
[not found] ` <3D4B284F.20402-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
2002-08-03 13:47 ` Alan Cox
2002-08-03 14:50 ` Johnathan Hicks
2002-08-02 23:31 ` Alan Cox
2002-08-03 8:58 ` Pavel Machek
-- strict thread matches above, loose matches on Subject: below --
2002-08-03 1:28 Bishop Brock
[not found] ` <OF94EF243F.A49E95B4-ON86256C09.00716EF4-yJlKWOkj9xhBDgjK7y7TUQ@public.gmane.org>
2002-08-03 13:40 ` Alan Cox
2002-08-03 2:29 Bishop Brock
[not found] ` <OF4415334C.6C7486B8-ON86256C0A.00081BB4-yJlKWOkj9xhBDgjK7y7TUQ@public.gmane.org>
2002-08-03 13:32 ` Alan Cox
[not found] <3D4BEDA4.4030908-Pn2JTpibVOrk1uMJSBkQmQ@public.gmane.org>
2002-08-06 14:55 ` Alan Cox
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=3D4B284F.20402@folkwolf.net \
--to=thetech-pn2jtpibvork1umjsbkqmq@public.gmane.org \
--cc=acpi-devel-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.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