From mboxrd@z Thu Jan  1 00:00:00 1970
From: Timur Tabi <timur@freescale.com>
Date: Fri, 04 Sep 2009 10:30:59 -0500
Subject: [U-Boot] Odd value for I2C_TIMEOUT in fsl_i2c.c
In-Reply-To: <1252078092.6005.63.camel@localhost.localdomain>
References: <4A9FDF1E.4090908@freescale.com> <4AA0BEC5.3010505@denx.de>	
	<20090904092503.058A0832E8DE@gemini.denx.de>	
	<ed82fe3e0909040709u16adec47id77693ed53193db5@mail.gmail.com>	
	<20090904150135.E88CB832E8DE@gemini.denx.de>	
	<4AA12E52.2080403@freescale.com>
	<1252078092.6005.63.camel@localhost.localdomain>
Message-ID: <4AA132B3.3050004@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

Peter Tyser wrote:
> If this is the case, the timeout should be the maximum (or reasonable
> maximum) time an I2C transaction could take.

How long is that?  Is one millisecond good enough?

-- 
Timur Tabi
Linux kernel developer at Freescale