From: Borislav Petkov <bp@alien8.de>
To: Tero Keski-Valkama <tero.keski-valkama@neter.fi>
Cc: linux-kernel@vger.kernel.org, peter@piie.net
Subject: Re: [PATCH 1/1] x86: Added support for Acer Aspire 5755G fan control.
Date: Wed, 26 Sep 2012 00:24:17 +0200 [thread overview]
Message-ID: <20120925222417.GA31780@liondog.tnic> (raw)
In-Reply-To: <CABGkUugOvWCSfXvLW33jmntGYAAiPP9fStXbdRAozx3bEoKBOA@mail.gmail.com>
Adding Peter.
On Tue, Sep 25, 2012 at 12:41:11PM +0300, Tero Keski-Valkama wrote:
> 2012/9/25 Borislav Petkov <bp@alien8.de>:
> > On Tue, Sep 25, 2012 at 10:34:13AM +0300, Tero Keski-Valkama wrote:
> >
> > But before we go with this any further: you mentioned some issues still
> > with acerhdf - you don't want to turn off your fan but to turn it to
> > full?
> >
> > I think in this case, you want to simply not load the driver and use the
> > BIOS settings, no?
> >
> > --
> > Regards/Gruss,
> > Boris.
>
> Technically I think my original issue is about thermal zones, and BIOS
> control doesn't solve it as is. However, the patch should be valid,
> even if it doesn't solve my original issue.
>
> The thing is that passive cooling thermal zones throttle all the cores
> to stone age, to 800 MHz, before the fan even really starts powering
> up from the low default level.
I don't understand: you want the thermal zones to not throttle your cpu
to 800 Mhz and/or the fan to start sooner?
> So, my original problem would be solved
> by:
> a) Direct control of the fan, to be able to put it on full for example
> through userspace control,
That's always a bad idea, especially if userspace dies on you.
> b) Changing the active cooling thermal zones, so that the fan speeds
> up earlier, or
Ok, I see, here's what you want.
> c) Changing the passive cooling (CPU throttling) thermal zones, so
> that it doesn't prevent fan from speeding up in the first place.
>
> At the moment, I don't see any way to change the thermal zones through
> existing interfaces for this laptop, and I don't see any potential
> thermal zone controls, or manual fan control option in the Embedded
> Controller registry.
I'll let Peter have a look at the patch too.
@Peter, it is at: http://lkml.org/lkml/2012/9/25/92
Btw, the commit message starts with "x86:... " and it should be
"acerhdf:.. " Peter, please change that when handling the patch further.
Also, you've added yourself to the copyright - this means that you're
pretty much going to get all future email about acerhdf. Do you really
want that?
--
Regards/Gruss,
Boris.
next prev parent reply other threads:[~2012-09-25 22:24 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1348433304-28320-1-git-send-email-tero.keski-valkama@neter.fi>
2012-09-25 7:34 ` Tero Keski-Valkama
2012-09-25 9:01 ` Borislav Petkov
2012-09-25 9:41 ` Tero Keski-Valkama
2012-09-25 22:24 ` Borislav Petkov [this message]
2012-09-25 23:10 ` Tero Keski-Valkama
2012-09-26 20:00 ` Tero Keski-Valkama
2012-09-26 20:47 ` Tero Keski-Valkama
2012-09-29 13:32 ` Tero Keski-Valkama
2012-09-29 14:25 ` Peter Feuerer
2013-03-07 9:41 ` Tero Keski-Valkama
2013-03-07 10:35 ` Borislav Petkov
2013-03-07 10:50 ` Tero Keski-Valkama
2013-03-07 11:03 ` Borislav Petkov
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=20120925222417.GA31780@liondog.tnic \
--to=bp@alien8.de \
--cc=linux-kernel@vger.kernel.org \
--cc=peter@piie.net \
--cc=tero.keski-valkama@neter.fi \
/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
all inboxes | Powered by JetHome®