From mboxrd@z Thu Jan  1 00:00:00 1970
From: Wolfgang Grandegger <wg@denx.de>
Date: Mon, 14 Sep 2009 18:01:23 +0200
Subject: [U-Boot] fsl_i2c: increase I2C timeout values and make
	them	configurable
In-Reply-To: <4AAE55FA.4070702@freescale.com>
References: <OF1352D3EB.F09B59F9-ONC125762C.0032A95A-C125762C.00333D4F@transmode.se>	<ed82fe3e0909090724q5b4dc622yaf0325ea4b0c24ca@mail.gmail.com>	<OFF1E33A19.F4EB95A4-ONC125762C.004F9266-C125762C.004FEE7D@transmode.se>	<OF50645EAC.EE2D33E5-ONC125762D.002C17DA-C125762D.002D6101@transmode.se>	<4AA8FA18.20103@freescale.com>	<OF65C14DE7.4464DC3C-ONC125762D.00488AFB-C125762D.00494875@transmode.se>	<4AA8FF3F.4010105@freescale.com>	<OFDF088E3C.0D2E024D-ONC125762D.0051E213-C125762D.00522472@transmode.se>	<4AA91AA5.3090707@freescale.com>	<OF4C79B629.D9D25607-ONC125762D.0056B7D9-C125762D.00574EF9@transmode.se>	<4AA9258F.8070402@freescale.com>	<OF60555086.5127475C-ONC125762D.005E3DC8-C125762D.005EA80A@transmode.se>	<OF4571178E.FE66A74F-ONC125762E.002E9C06-C125762E.003007EB@transmode.se>	<4AAA6ACD.9040905@freescale.com>
	<m2vdjlfxa0.fsf@ohwell.denx.de> <4AAE50AF.3090403@grandegger.com>
	<4AAE55FA.4070702@freescale.com>
Message-ID: <4AAE68D3.8010900@denx.de>
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

Timur Tabi wrote:
> Wolfgang Grandegger wrote:
> 
>> I did not follow the thread yet, sorry. I implemented AN2819 for Linux
>> (see http://lxr.linux.no/#linux+v2.6.31/drivers/i2c/busses/i2c-mpc.c)
>> some time ago using Timur's table approach. But there is no difference
>> between the table and the algorithm to calculate the value. The table is
>> actually derived from the same algorithm.
> 
> The problem with the table is that it does not allow for flexibility in choosing dfsr.  When I implemented the table code, I did not think that this was a problem, but apparently it is.

What would be the criteria to choose dfsr, especially for a defined bus
frequency.

Wolfgang.