public inbox for linux-acpi@vger.kernel.org
 help / color / mirror / Atom feed
From: Len Brown <lenb@kernel.org>
To: Andras Lorincz <andras.lorincz@gmail.com>
Cc: linux-acpi@vger.kernel.org
Subject: Re: Help with fan on fujitsu siemens
Date: Fri, 16 Feb 2007 12:02:43 -0500	[thread overview]
Message-ID: <200702161202.43455.lenb@kernel.org> (raw)
In-Reply-To: <a21d779b0702152346l35b83cadw2d2b4e9f3939da7e@mail.gmail.com>

On Friday 16 February 2007 02:46, Andras Lorincz wrote:

> and the output of cat /proc/acpi/thermal_zone/*/* is:
> 
> cooling mode:   active
> polling frequency:       30 seconds
> state:                   ok
> temperature:             49 C
> critical (S5):           105 C
> passive:                 79 C: tc1=3 tc2=1 tsp=80
> devices=0xf7e9c720
> active[0]:               65 C: devices=0xc17e4d9c
> active[1]:               55 C: devices=0xc17e4d38
> 
> Some remarks:
> 
>  - the polling frequency is not set by default so I
> run a script on startup which sets the polling
> frequency to 30 secs

if you don't set polling frequency it is 0?
Does anything not work in that case?

That is the ideal case -- as polling frequency 0
means that the system is event-driven.

If you need to enable polling b/c something isn't working,
3 seconds may be more prudent than 30 seconds.

>  - the state reported by
> /proc/acpi/thermal_zone/THRM/state changes correctly
> according to changing temperatures but it is not in
> accordance with the real state of the cooler.

Do you have /proc/acpi/fan/*/* files?
What do they say?

-Len

  reply	other threads:[~2007-02-16 17:04 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-02-16  7:46 Help with fan on fujitsu siemens Andras Lorincz
2007-02-16 17:02 ` Len Brown [this message]
2007-02-16 18:25   ` Andras Lorincz
2007-02-16 21:58     ` Len Brown
2007-02-17  8:12       ` Andras Lorincz
2007-02-17  8:33         ` Andras Lorincz

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=200702161202.43455.lenb@kernel.org \
    --to=lenb@kernel.org \
    --cc=andras.lorincz@gmail.com \
    --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