From: Benjamin Herrenschmidt <benh@kernel.crashing.org>
To: Aaro Koskinen <aaro.koskinen@iki.fi>
Cc: Jan Engelhardt <jengelh@inai.de>,
linuxppc-dev <linuxppc-dev@lists.ozlabs.org>
Subject: Re: therm_pm72 units, interface
Date: Sun, 21 Jul 2013 09:42:29 +1000 [thread overview]
Message-ID: <1374363749.19894.568.camel@pasglop> (raw)
In-Reply-To: <20130720203346.GM14385@blackmetal.musicnaut.iki.fi>
On Sat, 2013-07-20 at 23:33 +0300, Aaro Koskinen wrote:
> Hi,
>
> On Sat, Jul 20, 2013 at 09:16:49AM +1000, Benjamin Herrenschmidt wrote:
> > On Fri, 2013-07-19 at 20:43 +0300, Aaro Koskinen wrote:
> > > I booted a Xserve today with 3.11-rc1, and noticed the noise is coming
> > > from slots-fan (PCI fan?) which is always 99%, although the slots-temp is
> > > just 33. Is it on purpose the rm31 slots PID params are totally different
> > > from therm_pm72 slots params? It seems like they have been copied from
> > > pm72 "drive bay" PID params instead.
> >
> > Could be my mistake. What happens if you change them to match the old code ?
>
> I tried the change below (use SLOTS_PID_* values from therm_pm72.h),
> and the noise level is considerably lower. The slots-fan stays at 19%,
> and slots-temp rises to 42'C but not higher after running couple of hours.
Thanks. I'll give it a quick dbl check asap (about to head out of town
now), in the meantime, can you send it with the appropriate
Signed-off-by: etc... ?
Thanks,
Ben.
> diff --git a/drivers/macintosh/windfarm_rm31.c b/drivers/macintosh/windfarm_rm31.c
> index 0b9a79b..82fc86a 100644
> --- a/drivers/macintosh/windfarm_rm31.c
> +++ b/drivers/macintosh/windfarm_rm31.c
> @@ -439,15 +439,15 @@ static void backside_setup_pid(void)
>
> /* Slots fan */
> static const struct wf_pid_param slots_param = {
> - .interval = 5,
> - .history_len = 2,
> - .gd = 30 << 20,
> - .gp = 5 << 20,
> - .gr = 0,
> - .itarget = 40 << 16,
> - .additive = 1,
> - .min = 300,
> - .max = 4000,
> + .interval = 1,
> + .history_len = 20,
> + .gd = 0,
> + .gp = 0,
> + .gr = 0x00100000,
> + .itarget = 3200000,
> + .additive = 0,
> + .min = 20,
> + .max = 100,
> };
>
> static void slots_fan_tick(void)
next prev parent reply other threads:[~2013-07-20 23:42 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-08-15 17:53 therm_pm72 units, interface Jan Engelhardt
2012-08-15 21:35 ` Benjamin Herrenschmidt
2012-08-16 15:24 ` Jan Engelhardt
2012-08-16 20:51 ` Benjamin Herrenschmidt
2012-08-17 13:51 ` Jan Engelhardt
2012-08-17 20:17 ` Benjamin Herrenschmidt
2012-08-17 14:23 ` Jan Engelhardt
2012-08-15 21:36 ` Benjamin Herrenschmidt
2013-01-17 14:38 ` Jan Engelhardt
2013-01-17 23:38 ` Benjamin Herrenschmidt
2013-07-19 17:43 ` Aaro Koskinen
2013-07-19 23:16 ` Benjamin Herrenschmidt
2013-07-20 20:33 ` Aaro Koskinen
2013-07-20 23:42 ` Benjamin Herrenschmidt [this message]
2013-08-02 10:03 ` Michel Dänzer
2013-08-02 12:51 ` Benjamin Herrenschmidt
2013-08-02 14:47 ` Michel Dänzer
2013-08-02 15:58 ` Aaro Koskinen
2013-08-02 16:52 ` Michel Dänzer
2013-08-02 21:02 ` Benjamin Herrenschmidt
2013-08-05 9:13 ` Michel Dänzer
2013-08-05 9:22 ` Benjamin Herrenschmidt
2013-08-05 10:32 ` Michel Dänzer
2013-08-05 10:53 ` Benjamin Herrenschmidt
2013-09-27 15:44 ` Michel Dänzer
2013-08-02 20:47 ` Benjamin Herrenschmidt
2013-08-02 20:56 ` Ben Hutchings
2013-08-02 21:04 ` Benjamin Herrenschmidt
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=1374363749.19894.568.camel@pasglop \
--to=benh@kernel.crashing.org \
--cc=aaro.koskinen@iki.fi \
--cc=jengelh@inai.de \
--cc=linuxppc-dev@lists.ozlabs.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.