On Wednesday 14 May 2008, Matthew Garrett wrote: > On Tue, May 13, 2008 at 11:30:20PM -0400, Len Brown wrote: > > > An entire new handheld product line will ship this year > > where the assumption that the processor is the primary > > contributor to heat may simply be _false_, thermal > > zones may be totally unrelated to the processor, > > and throttling the processor may be exactly the > > wrong way to handle a thermal issue. > > That's fine. In the ACPI code, we currently have no support for managing > thermal conditions through anything other than the processor. Once that > changes, it's easy to fix this up so it doesn't interfere with thermal > zones that are handled by throttling other devices. No. ACPI thermal zones with no passive trip points can be used to simply report interesting temperature events to user-space (via the spiffy new generic thermal class). User-space then invokes corrective action -- which may be something _other_ than throttling the CPU. > Menlow has a more complex thermal model than machines we've seen up to > now, but I was under the impression that this was to be handled by the > new generic thermal class rather than the existing ACPI code. I don't > see this patch as being in conflict with supporting that. No. It is a direct conflict. Say the thermal zone is related to the communications chip. If we create a phantom passive trip point for that zone and throttle the CPU when it fires, we're shooting ourselves in the head (when we should be poking ourselves in the ear, or some such:-) -Len -- 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
