From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott McNutt Date: Thu, 02 Apr 2009 09:09:36 -0400 Subject: [U-Boot] core ticks/timer code In-Reply-To: References: <200903272130.26825.vapier@gentoo.org> <49CDCCC1.5050503@googlemail.com> <200903302110.06020.vapier@gentoo.org> <49D2014F.4070802@psyent.com> <20090331154801.73E3283797DC@gemini.denx.de> <20090331212514.GA19920@ld0162-tx32.am.freescale.net> <20090331212740.6684983797DC@gemini.denx.de> Message-ID: <49D4B910.20102@psyent.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de >> In message <20090331212514.GA19920@ld0162-tx32.am.freescale.net> you wrote: >>> On Tue, Mar 31, 2009 at 05:48:01PM +0200, Wolfgang Denk wrote: >>>> We still need some hint that the timer works in millisecond >>>> resolution, though - no matter what you call it. >>> How about just calling it HZ (or something more verbose like TIMER_HZ, >>> but the former makes it easier to share code with Linux) and declaring it >>> in a non-board header? >> It's OK with me. Other opinions? > > Obviously only like-minded people around. I'm not particular ... and please don't mistake my sometimes dry sense of humor as complaining ... that's rarely my intent .... but please don't use a name that implies it is configurable. I learned the hard way that it is not. ;-) If the value truly represents clocks per tick, or milliseconds per tick, and the value is always fixed, something along those lines would certainly be appropriate. Best Regards, --Scott