From: Reinhard Meyer Date: Tue, 21 Sep 2010 14:12:23 +0200 Subject: [U-Boot] RFC: get_ticks() + get_tbclk() In-Reply-To: <20100921071310.30201157D71@gemini.denx.de> References: <4C98482F.7040508@emk-elektronik.de> <201009210208.55367.vapier@gentoo.org> <4C98536C.6010003@emk-elektronik.de> <20100921071310.30201157D71@gemini.denx.de> Message-ID: <4C98A127.8030107@emk-elektronik.de> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Dear Wolfgang Denk, > In message <4C98536C.6010003@emk-elektronik.de> you wrote: >> For me it seems useful to keep both functions and have ticks >> increment at a hardware-convenient rate. >> If the hardware timer can be prescaled to increment at 1000 Hz that >> is fine, but I see no immediate need for that. If the hardware cannot >> be prescaled, and software would need to do a 64 bit multiply/divide >> on each timer read, that would really be overkill. > > Just FYI: the origin of these functions is (like usual) in the > implementation for the Power Architecture. > > There we have a 64 bit timebase register (split into two 32 bit > registers, the upper half in tbu and the lower half in tbl). The > timebase register gets incremented at a pretty high rate, usually > every 4 or 16 system clocks). > > get_ticks() just returns the content of the 64 bit timebase register. Yes, of course. So the current ARM926EJS/AT91 implementation is actually in the right direction, although not perfected yet. I am going to look into that. Reinhard