From mboxrd@z Thu Jan 1 00:00:00 1970 From: Scott Wood Date: Fri, 04 Sep 2009 14:28:01 -0500 Subject: [U-Boot] Odd value for I2C_TIMEOUT in fsl_i2c.c In-Reply-To: <20090904192320.34250832E8DE@gemini.denx.de> References: <4A9FDF1E.4090908@freescale.com> <4AA0BEC5.3010505@denx.de> <20090904092503.058A0832E8DE@gemini.denx.de> <20090904150135.E88CB832E8DE@gemini.denx.de> <4AA12E52.2080403@freescale.com> <20090904152948.BB4A6832E8DE@gemini.denx.de> <20090904183437.GA20066@b07421-ec1.am.freescale.net> <20090904192320.34250832E8DE@gemini.denx.de> Message-ID: <4AA16A41.30107@freescale.com> List-Id: MIME-Version: 1.0 Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit To: u-boot@lists.denx.de Wolfgang Denk wrote: > Dear Scott Wood, > > In message <20090904183437.GA20066@b07421-ec1.am.freescale.net> you wrote: >>> milliseconds, i. e. a time. "(CONFIG_SYS_HZ / 4)" is a frequency, >>> i. e. not a time, but the inverse of it. >>> >>> It is plain wront to write "250 per second" when you mean "250 milliseconds" >> It is not a frequency, it is a number of ticks. This is a very common >> idiom. > > CONFIG_SYS_HZ _is_ a frequenzy. It is the number of ticks _per_ > _second_. That is the _inverse_ of a time unit, not a time unit. Yes, CONFIG_SYS_HZ is a frequency. And when you multiply a _frequency_, which is _ticks_ per _second_, by a number _seconds_ (in this case, 1/4 sec), you get a number of _ticks_. -Scott