public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Lucas Levrel <lucas.levrel@free.fr>
To: linux-acpi@vger.kernel.org
Subject: Re: Help/info request (in re trip points)
Date: Tue, 26 Jul 2016 23:01:55 +0200 (CEST)	[thread overview]
Message-ID: <alpine.LNX.2.20.13.1607262256590.2759@localhost> (raw)
In-Reply-To: <alpine.LSU.2.20.13.1607221012230.4463@coulomb.u-pec.fr>


Hi (once more),

Isn't there anyone who could spare a few minutes to guide me on this?

I found some references to trip_point_?_hyst files, which seem promising, 
but they aren't there in my sysfs, and I cannot create them (e.g. "touch: 
cannot touch `trip_point_4_hyst': No such file or directory").

Thanks.

Lucas Levrel

Le 22 juillet 2016, Lucas Levrel a écrit :

> Hi,
>
> Is this the right place to request for help and/or information about thermal 
> zones? If not, please point me to the right place.
>
> I browsed through thermal.c but couldn't find an answer to my question (it 
> goes without saying I'm not an expert), namely:
> how are trip point temperatures set at boot, and how are they reset when 
> crossed?
>
> I'm aiming at changing the temperatures at which the fan starts and stops. 
> The kernel parameter thermal.act=XXX did change the "fan on" temperature, but 
> not the "fan off" one. I expected the hysteresis T(on)-T(off) to be constant, 
> and thus I thought T(off) would raise as much as I raised T(on), but this is 
> not the case.
>
> Any help is greatly appreciated.
>
> Lucas Levrel
--
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at  http://vger.kernel.org/majordomo-info.html

  reply	other threads:[~2016-07-26 21:09 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-07-22  8:22 Help/info request (in re trip points) Lucas Levrel
2016-07-26 21:01 ` Lucas Levrel [this message]
2016-07-27  1:29   ` Zhang Rui
2016-07-27 10:12     ` lucas.levrel

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=alpine.LNX.2.20.13.1607262256590.2759@localhost \
    --to=lucas.levrel@free.fr \
    --cc=linux-acpi@vger.kernel.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