On Thu, 8 Mar 2007 10:13:23 -0300, Henrique de Moraes Holschuh wrote: > On Thu, 08 Mar 2007, Zhang Rui wrote: > > First, ACPI thermal zone can be used to set different cooling policies, > > i.e. passive cooling mode and active cooling mode. > > In passive mode, just as Matthew Garrett described, ACPI thermal may > > throttle the CPU if the passive trip point is triggered, i.e. cool a > > thermal zone by decreasing the performance of the devices(always CPU > > now) in the zone. > > The active cooling mode will use one or more active devices(usually fan) > > to decrease the temperature, which consume extra power. And this is > > really like the way that the hwmon is doing. > > So we can only map the active cooling policy to hwmon, right? > > Right, which is not to say we can't extend hwmon to also cover passive. Correct. The hwmon interface had no reason to mention passive cooling as hardware monitoring chips have no control over CPU speed. So far this kind of passive cooling was implemented in user-space, using the temperature as one of the decision factor for CPU frequency in cpufreqd or similar. Of course, if the ACPI virtual hardware monitoring device can control the speed, it might be convenient to extend the interface to let the user do it. But I have no idea what it would look like. > > Second, one ACPI thermal zone may have more than one fan devices, even > > one active trip point may associate with several fan devices. And this > > seems to be different from the sensors, doesn't it? > > No, a LM85 does that too. I don't recall if the current interface allows > for that mapping easily, but if it doesn't, it needs to be modified. It does, see item pwm[1-*]_auto_channels_temp in Documentation/hwmon/sysfs-interface. Whether it qualifies as "easily" is another problem ;) -- Jean Delvare - To unsubscribe from this list: send the line "unsubscribe linux-acpi" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
