From: Olaf Hering <olaf@aepfle.de>
To: linux-pm@vger.kernel.org
Subject: Re: adjusting broken ACPI thermal trip points
Date: Sun, 4 Oct 2015 08:36:56 +0200 [thread overview]
Message-ID: <20151004063656.GA4202@aepfle.de> (raw)
In-Reply-To: <20151001161622.GA21024@aepfle.de>
On Thu, Oct 01, Olaf Hering wrote:
> Initially I reported https://bugzilla.kernel.org/show_bug.cgi?id=67101
And related to this:
why would the first command enable the fan after boot only sometimes,
while the second one will succeed every time? Is this a kernel or
firmware bug?
# while :;do for i in 2 4 ; do echo 1 > /sys/class/thermal/cooling_device$i/cur_state ; cat /sys/class/thermal/cooling_device$i/cur_state > /dev/null ; done ; sleep 2 ; done
# while :;do for i in 2 4 ; do echo 1 > /sys/class/thermal/cooling_device$i/cur_state ; done ; sleep 2 ; done
Appearently cur_state must be read right after writing to it to have an
effect when selecting fan speeds for 0, 1 or 2.
Olaf
prev parent reply other threads:[~2015-10-04 6:37 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-10-01 16:16 adjusting broken ACPI thermal trip points Olaf Hering
2015-10-02 7:23 ` Olaf Hering
2015-10-04 6:36 ` Olaf Hering [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=20151004063656.GA4202@aepfle.de \
--to=olaf@aepfle.de \
--cc=linux-pm@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;
as well as URLs for NNTP newsgroup(s).