From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 3 00:36:58 2005 Return-Path: X-Original-To: acpi@FreeBSD.ORG Delivered-To: freebsd-acpi@FreeBSD.ORG Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id 099D316A429; Sun, 3 Jul 2005 00:36:58 +0000 (GMT) (envelope-from ps@mu.org) Received: from elvis.mu.org (elvis.mu.org [192.203.228.196]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9463F44098; Sun, 3 Jul 2005 00:20:15 +0000 (GMT) (envelope-from ps@mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id B9309623F1; Sat, 2 Jul 2005 17:19:56 -0700 (PDT) X-Original-To: ps@mu.org Delivered-To: ps@mu.org Received: from mx2.freebsd.org (mx2.freebsd.org [216.136.204.119]) by elvis.mu.org (Postfix) with ESMTP id 3F9F15C955; Thu, 24 Feb 2005 15:09:37 -0800 (PST) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id DAE9356104; Thu, 24 Feb 2005 23:09:20 +0000 (GMT) (envelope-from owner-freebsd-current@freebsd.org) Received: from hub.freebsd.org (localhost [127.0.0.1]) by hub.freebsd.org (Postfix) with ESMTP id E71CC16A53E; Thu, 24 Feb 2005 23:09:12 +0000 (GMT) Delivered-To: freebsd-current@freebsd.org Received: from mx1.FreeBSD.org (mx1.freebsd.org [216.136.204.125]) by hub.freebsd.org (Postfix) with ESMTP id E7B8416A4CE; Thu, 24 Feb 2005 23:08:55 +0000 (GMT) Received: from pi.codefab.com (pi.codefab.com [199.103.21.227]) by mx1.FreeBSD.org (Postfix) with ESMTP id 9AEE243D31; Thu, 24 Feb 2005 23:08:55 +0000 (GMT) (envelope-from cswiger@mac.com) Received: from localhost (localhost [127.0.0.1]) by pi.codefab.com (Postfix) with ESMTP id 085CB5D61; Thu, 24 Feb 2005 18:08:55 -0500 (EST) Received: from pi.codefab.com ([127.0.0.1]) by localhost (pi.codefab.com [127.0.0.1]) (amavisd-new, port 10024) with ESMTP id 53528-06; Thu, 24 Feb 2005 18:08:54 -0500 (EST) Received: from [192.168.1.3] (pool-68-161-75-250.ny325.east.verizon.net [68.161.75.250]) by pi.codefab.com (Postfix) with ESMTP id AD4075D39; Thu, 24 Feb 2005 18:08:53 -0500 (EST) Message-ID: <421E5E7B.5040104@mac.com> From: Chuck Swiger Organization: The Courts of Chaos User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.7.5) Gecko/20041217 X-Accept-Language: en-us, en MIME-Version: 1.0 To: Maxim Sobolev References: <20050224011924.992A65D07@ptavv.es.net> <421DA0B5.4060705@portaone.com> <421E42F2.6010105@root.org> <421E49D9.60803@portaone.com> In-Reply-To: <421E49D9.60803@portaone.com> X-Enigmail-Version: 0.90.0.0 X-Enigmail-Supports: pgp-inline, pgp-mime Content-Type: text/plain; charset=us-ascii; format=flowed Content-Transfer-Encoding: 7bit X-Virus-Scanned: amavisd-new at codefab.com X-BeenThere: freebsd-current@freebsd.org X-Mailman-Version: 2.1.1 Precedence: list Sender: owner-freebsd-current@freebsd.org Errors-To: owner-freebsd-current@freebsd.org X-Spam-Checker-Version: SpamAssassin 3.0.2 (2004-11-16) on elvis.mu.org X-Spam-Status: No, score=-1.8 required=5.0 tests=AWL, BAYES_00, J_CHICKENPOX_13, RCVD_IN_SORBS autolearn=no version=3.0.2 X-Spam-Level: Cc: acpi@FreeBSD.ORG, current@FreeBSD.ORG Subject: Re: patch: p4tcc and speedstep cpufreq drivers X-BeenThere: freebsd-acpi@freebsd.org List-Id: ACPI and power management development List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Date: Sun, 03 Jul 2005 00:36:58 -0000 X-Original-Date: Thu, 24 Feb 2005 18:08:43 -0500 X-List-Received-Date: Sun, 03 Jul 2005 00:36:58 -0000 Maxim Sobolev wrote: > Nate Lawson wrote: [ ... ] >> "On-Demand mode may be used at the same time Automatic mode is >> enabled, however, if the system (tries to enable the TCC via On-Demand >> mode[1]) at the same time (automatic mode is enabled[2]) AND (a high temperature >> condition exists [3]), the duty cycle of the automatic mode will override >> the duty cycle selected by the On-Demand mode." >> >> Since automatic mode is set by the BIOS before we even boot, things >> should be fine. > > Well, this is quite tricky part of the spec. My reading is that the > paragraph above applies only to situation if you are (trying to set > on-demand mode [1]) when both (automatic mode is in effect [2]) *and* (high > temperature condition already exists [3]), in that case automatic mode will > win and override any manual settings. I suspect you'd read your paragraph with [1] and [2] joined together, but they can be read seperately just as the spec can. :-) > However, in the case when you have on-demand mode already on and high > temperature condition emerges it will have no effect on duty cycle until > THERMTRIP# kicks in. > > That's in my view explains why there is big AND in the text above. I think the spec is advising developers who try to control TCC that if PROCHOT gets asserted, the CPU may override the programmed settings in favor of the automatic ones. I don't think the spec is asserting that the CPU is forbidden from reducing power usage if PROCHOT condition is detected, regardless of what automatic mode is set to. A reasonable processor would drop to a known minimal power usage state-- hopefully one low enough to keep the CPU from completely overheating even if a fan has failed-- if PROCHOT is seen. [ It may also be the case that a CPU does not do so, in which case the ACPI driver code ought to try to pay attention to PROCHOT and reduce power consumption regardless and not just depend on CPU failsafes to work. If that is your position, well, I would agree with this. :-) ] -- -Chuck _______________________________________________ freebsd-current@freebsd.org mailing list http://lists.freebsd.org/mailman/listinfo/freebsd-current To unsubscribe, send any mail to "freebsd-current-unsubscribe@freebsd.org"