From mboxrd@z Thu Jan  1 00:00:00 1970
From: Timur Tabi <timur@freescale.com>
Date: Fri, 04 Sep 2009 10:12:18 -0500
Subject: [U-Boot] Odd value for I2C_TIMEOUT in fsl_i2c.c
In-Reply-To: <20090904150135.E88CB832E8DE@gemini.denx.de>
References: <4A9FDF1E.4090908@freescale.com> <4AA0BEC5.3010505@denx.de>
	<20090904092503.058A0832E8DE@gemini.denx.de>
	<ed82fe3e0909040709u16adec47id77693ed53193db5@mail.gmail.com>
	<20090904150135.E88CB832E8DE@gemini.denx.de>
Message-ID: <4AA12E52.2080403@freescale.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

Wolfgang Denk wrote:

> Wrong Question. I don't know enough about the I2C protocol. Why is
> i2c_wait4bus necessary?

Ok, why is it necessary?

> 
>> Kumar, any thoughts?  Is there something sneaky going on here, or did
>> you just misinterpret the value of I2C_TIMEOUT?
> 
> I guess I2C_TIMEOUT might always have been misinterpeted.

I think the original code was correct, because it was counting clock ticks.

-- 
Timur Tabi
Linux kernel developer at Freescale