On 2/16/07, Len Brown <[EMAIL PROTECTED]> wrote:
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
Now I'm playing around with 2.6.20. If I don't set the polling
frequency at boot time then cat
/proc/acpi/thermal_zone/polling_frequency gives me:
<polling disabled>
I also tried setting the polling frequency to 0 but doesn't help. ls
/proc/acpi/fan gives me:
FAN0 FAN1
and ls /proc/acpi/fan/FAN0 and ls /proc/acpi/fan/FAN1 give me:
state
-
To unsubscribe from this list: send the line "unsubscribe linux-acpi" in
the body of a message to [EMAIL PROTECTED]
More majordomo info at http://vger.kernel.org/majordomo-info.html
