From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: clemej@alum.rpi.edu
Cc: cpufreq@www.linux.org.uk
Subject: Re: scaling_available_frequenies support for pmac_cpufreq
Date: Thu, 29 Jul 2004 08:58:34 +1000 [thread overview]
Message-ID: <1091055513.9879.28.camel@gaston> (raw)
In-Reply-To: <Pine.LNX.4.58.0407241508110.24401@pianoman.cluster.toy>
On Sun, 2004-07-25 at 05:19, John Clemens wrote:
> Hi Ben and list..
>
> apologies if this has already been done, i haven't been following for a
> while. Here's a little patch to add scaling_available_frequencies to
> pmac_cpufreq, seems to work well on my iBook G3...
>
> ~# cat /sys/devices/system/cpu/cpu0/cpufreq/scaling_available_frequencies
> 900000 400000
>
> but some double checking would be welcome.
>
> I also cleaned up the use of PMAC_CPU_*_SPEED and standardized on
> CPUFREQ_*, etc.., which point to the same thing. Apply part or all at
> your whim..
Looks good, I'll test as soon as I have some time...
Ben.
prev parent reply other threads:[~2004-07-28 22:58 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-07-24 19:19 scaling_available_frequenies support for pmac_cpufreq John Clemens
2004-07-28 22:58 ` Benjamin Herrenschmidt [this message]
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=1091055513.9879.28.camel@gaston \
--to=benh@kernel.crashing.org \
--cc=clemej@alum.rpi.edu \
--cc=cpufreq@www.linux.org.uk \
/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