From: Benjamin Herrenschmidt <benh@kernel•crashing.org>
To: Kevin Diggs <kevdig@hypersurf•com>
Cc: linuxppc-dev@ozlabs•org
Subject: Re: preliminary 750GX PLL control patch
Date: Sat, 30 Jul 2005 18:18:03 +0200 [thread overview]
Message-ID: <1122740284.18835.87.camel@gaston> (raw)
In-Reply-To: <42E672B1.7050709@hypersurf.com>
On Tue, 2005-07-26 at 10:28 -0700, Kevin Diggs wrote:
> Hi,
>
> I've attached a patch that adds preliminary access to the HID1
> register in the 750GX (aka the PLL config register). The patch is
> against 2.4.30. It has been lightly tested on a PowerMac 8600 with a
> PowerLogix PowerForce 750GX cpu card.
>
> Depending on the values for the pllx_cfg field, this should
> work on the 750FX as well ... except for the stuff in idle_6xx.S. Since
> there are plenty of people on this list way more smarterer than me I was
> hoping someone could answer a question about the powersave modes that
> some of the PowerPC processors have:
>
> Since, as I understand it, the clock is shut off to much of the
> chip when a powersave mode is engaged does it really buy you that much
> to switch to a lower clock speed? Wouldn't you be better off shutting
> off the unused PLL?
>
> Also, please note that I am not very experienced creating
> patches so please use a backup of your source tree.
Well... I replicated what darwin does here. I don't remember completely
but it's possible that there is some kind of CPU errata related to nap
and clock speed... or maybe it still makes a difference :)
You want to wakeup fast from nap too, so switching off/on the unused PLL
might not be that a good idea. But heh, you are welcome to try &
measure.
Ben.
prev parent reply other threads:[~2005-07-30 16:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2005-07-26 17:28 preliminary 750GX PLL control patch Kevin Diggs
2005-07-30 16:18 ` 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=1122740284.18835.87.camel@gaston \
--to=benh@kernel$(echo .)crashing.org \
--cc=kevdig@hypersurf$(echo .)com \
--cc=linuxppc-dev@ozlabs$(echo .)org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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