From owner-freebsd-acpi@FreeBSD.ORG Sun Jul 3 00:37:13 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 9E33C16A448; Sun, 3 Jul 2005 00:37:12 +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 3F516443E5; Sun, 3 Jul 2005 00:20:29 +0000 (GMT) (envelope-from ps@mu.org) Received: by elvis.mu.org (Postfix, from userid 1000) id 57A3E623E0; Sat, 2 Jul 2005 17:19:58 -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 D71605C87A; Fri, 25 Feb 2005 01:00:52 -0800 (PST) Received: from hub.freebsd.org (hub.freebsd.org [216.136.204.18]) by mx2.freebsd.org (Postfix) with ESMTP id 762E95644F; Fri, 25 Feb 2005 09:00:00 +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 0B7C216A4F5; Fri, 25 Feb 2005 08:59:59 +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 1305716A4CE; Fri, 25 Feb 2005 08:59:55 +0000 (GMT) Received: from www.portaone.com (web.portaone.com [195.70.151.35]) by mx1.FreeBSD.org (Postfix) with ESMTP id 2A40C43D48; Fri, 25 Feb 2005 08:59:54 +0000 (GMT) (envelope-from sobomax@portaone.com) Received: from [192.168.0.128] ([192.168.2.2]) (authenticated bits=0) by www.portaone.com (8.12.11/8.12.11) with ESMTP id j1P8u1Fx078798 (version=TLSv1/SSLv3 cipher=DHE-RSA-AES256-SHA bits=256 verify=NO); Fri, 25 Feb 2005 09:56:02 +0100 (CET) (envelope-from sobomax@portaone.com) Message-ID: <421EE81C.3040204@portaone.com> From: Maxim Sobolev Organization: Porta Software Ltd User-Agent: Mozilla Thunderbird 1.0 (Windows/20041206) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Chuck Swiger References: <20050224011924.992A65D07@ptavv.es.net> <421DA0B5.4060705@portaone.com> <421E42F2.6010105@root.org> <421E49D9.60803@portaone.com> <421E5E7B.5040104@mac.com> In-Reply-To: <421E5E7B.5040104@mac.com> Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 8bit X-Virus-Scanned: ClamAV 0.80/685/Wed Jan 26 10:08:24 2005 clamav-milter version 0.80j on www.portaone.com X-Virus-Status: Clean 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=-2.2 required=5.0 tests=AWL, BAYES_00, J_CHICKENPOX_13 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:37:14 -0000 X-Original-Date: Fri, 25 Feb 2005 10:55:56 +0200 X-List-Received-Date: Sun, 03 Jul 2005 00:37:14 -0000 Chuck Swiger wrote: > 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. :-) ] Check the original spec, there is a note at the end of the respective paragraph (particularly the first sentence): If automatic mode is disabled the processor will be operating out of specification and cannot be guaranteed to provide reliable results. Regardless of enabling of the automatic or On-Demand modes, in the event of a catastrophic cooling failure, the processor will automatically shut down when the silicon has reached a temperature of approximately 135 °C. At this point the system bus signal THERMTRIP# will go active and stay active until RESET# has been initiated. THERMTRIP# activation is independent of processor activity and does not generate any bus cycles. If THERMTRIP# is asserted, processor core voltage (Vcc) must be removed within the timeframe defined in Table 16. -Maxim _______________________________________________ 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"