From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dave Jones Subject: Re: [PATCH][DOCUMENTATION BUGFIX] latency in micro-, not nanoseconds Date: Mon, 10 Nov 2003 17:22:46 +0000 Sender: cpufreq-bounces@www.linux.org.uk Message-ID: <20031110172246.GT10144@redhat.com> References: <20031104160816.GA9187@brodo.de> <20031110163209.GP10144@redhat.com> <20031110171533.GS21970@poupinou.org> Mime-Version: 1.0 Return-path: Content-Disposition: inline In-Reply-To: <20031110171533.GS21970@poupinou.org> List-Id: List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , Errors-To: cpufreq-bounces@www.linux.org.uk Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: Ducrot Bruno Cc: cpufreq@www.linux.org.uk, Dominik Brodowski On Mon, Nov 10, 2003 at 06:15:33PM +0100, Ducrot Bruno wrote: > > The 'latency' we read from the BIOS is in microseconds, but the hardware > > wants it in units of 10ns. We do the necessary maths, and everything is fine. > > But we're also storing that result in .. > > > > policy->cpuinfo.transition_latency = latency; > > > > Which is possibly not the right thing to be doing. > > I think we want to be storing the 'pre 10ns munging' value here correct? > > > > Well, maybe we have to double it as well (there is actually 2 steps, the > VID change and the FID change, each having 'latency' 1e(-8) second)... > > something like: > policy->cpuinfo.transition_latency = latency / 50; Actually, I'm wondering why we need this at all anyway.. Dave