linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Andreas Schwab <schwab@linux-m68k.org>
Cc: khali@linux-fr.org, linuxppc-dev@ozlabs.org
Subject: Re: [PATCH 00/15] PowerMac i2c API conversions & windfarm updates
Date: Thu, 26 Apr 2012 07:14:25 +1000	[thread overview]
Message-ID: <1335388465.21961.35.camel@pasglop> (raw)
In-Reply-To: <m2sjfs85pv.fsf@igel.home>

On Wed, 2012-04-25 at 12:29 +0200, Andreas Schwab wrote:
> Benjamin Herrenschmidt <benh@kernel.crashing.org> writes:
> 
> > Also, does the new driver properly react to load ?
> 
> The old driver keeps the cpu fans running at 300 rpm (lowest speed?)
> for much longer when the cpus are put busy.  Only when the cpus are back
> idle it speeds them up to 1200 rpm or more for some time depending on
> how long the cpus were busy.  The new driver is faster at speeding up
> the fans to around 800 rpm when cpus get busy, and keeps them running
> longer at that speed, but doesn't appear to select much higher speeds.
> 
> The old driver appears to be better suited to desktops, whereas the new
> driver is probably better for servers.

That's odd... as I said, the algorithm is supposed to be the same...

> But the most annoying sound appears to be coming from the slots fan.

Constant or changing ? The slots fan is set to a fixed speed, which I
thought was constant (well, I "tickle" it a bit but roughly it's
constant). Or is that not the case for you ?

Darwin has an algorithm for it based on getting some data from the video
driver in the AGP slot, but I don't have that.

Cheers,
Ben.

  reply	other threads:[~2012-04-25 21:14 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <1334823416-9138-1-git-send-email-benh__1987.51832726902$1334826600$gmane$org@kernel.crashing.org>
2012-04-25  8:00 ` [PATCH 00/15] PowerMac i2c API conversions & windfarm updates Andreas Schwab
2012-04-25  8:38   ` Benjamin Herrenschmidt
2012-04-25 10:29     ` Andreas Schwab
2012-04-25 21:14       ` Benjamin Herrenschmidt [this message]
2012-04-25 21:54         ` Andreas Schwab
2012-04-25 21:58           ` Benjamin Herrenschmidt
2012-04-26  9:13             ` Andreas Schwab
2012-04-26  9:19               ` Benjamin Herrenschmidt
2012-04-26 11:41                 ` Andreas Schwab
2012-04-26 22:06                   ` Benjamin Herrenschmidt
2012-04-27  7:59                     ` Andreas Schwab
2012-04-26 11:43                 ` Andreas Schwab
2012-04-26 11:46         ` Andreas Schwab
2012-04-19  8:16 Benjamin Herrenschmidt
2012-04-19  9:37 ` Jean Delvare
2012-04-19  9:36   ` Christian Kujau
2012-04-19 20:59   ` Benjamin Herrenschmidt
     [not found] ` <20120419113723.03a24d46__2279.25503063506$1334829915$gmane$org@endymion.delvare>
2012-04-19 10:11   ` Andreas Schwab
2012-04-19 11:02     ` Jean Delvare
     [not found]   ` <m27gxc2fqq.fsf__16075.0973890119$1334830355$gmane$org@igel.home>
2012-04-19 10:14     ` Andreas Schwab
     [not found]     ` <m239802flw.fsf__48316.0902433612$1334830569$gmane$org@igel.home>
2012-04-19 10:19       ` Andreas Schwab

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=1335388465.21961.35.camel@pasglop \
    --to=benh@kernel.crashing.org \
    --cc=khali@linux-fr.org \
    --cc=linuxppc-dev@ozlabs.org \
    --cc=schwab@linux-m68k.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;
as well as URLs for NNTP newsgroup(s).