From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: from gate.crashing.org (gate.crashing.org [63.228.1.57]) (using TLSv1 with cipher DHE-RSA-AES256-SHA (256/256 bits)) (Client did not present a certificate) by ozlabs.org (Postfix) with ESMTP id F0D00DDE06 for ; Thu, 29 Nov 2007 22:32:26 +1100 (EST) Date: Thu, 29 Nov 2007 14:31:59 +0300 From: Vitaly Bordug To: "Alan Bennett" Subject: Re: Timers on mpc8248 etc... Message-ID: <20071129143159.2538786d@kernel.crashing.org> In-Reply-To: References: <474DFD15.603@freescale.com> Mime-Version: 1.0 Content-Type: text/plain; charset=US-ASCII Cc: linuxppc-dev@ozlabs.org List-Id: Linux on PowerPC Developers Mail List List-Unsubscribe: , List-Archive: List-Post: List-Help: List-Subscribe: , On Wed, 28 Nov 2007 21:06:36 -0700 Alan Bennett wrote: > It comes from uboot. Can you point me in the right direction to make > sure its right? > PowerPC,8248@0 { > device_type = "cpu"; > reg = <0>; > d-cache-line-size = ; > i-cache-line-size = ; > d-cache-size = ; > i-cache-size = ; > timebase-frequency = <0>; > clock-frequency = <0>; > }; > if your u-boot is up to date, it will have fdt command, and by fdt boardsetup fdt print / inspect what u-boot did. Of course you should have dtb preloaded to memory and fdt addr should be said to let u-boot know where dtb resides. > > On 11/28/07, Scott Wood wrote: > > Alan Bennett wrote: > > > I've got a routine that needs to delay for X microseconds, this > > > is a must. The command after schedule_timeout must has to wait > > > for the HW to complete a task that takes X microseconds. > > > > > > I would think that one way to do this is with a simple > > > schedule_timeout. But in the example below, the time that passes > > > from run1() to dontrun() is far less than 3.2 msecs. Infact, > > > sometimes its ~ 800 micros according the a analyzer looking at > > > points triggered in run1() and donrun(). Could this be a > > > configuration problem with the timer/interrupt that generates the > > > jiffies? > > > > Are you sure the timebase frequency is set correctly in the device > > tree? > > > > -Scott > > > _______________________________________________ > Linuxppc-dev mailing list > Linuxppc-dev@ozlabs.org > https://ozlabs.org/mailman/listinfo/linuxppc-dev -- Sincerely, Vitaly