public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Wolfgang Grandegger <wg@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH 3/3] fsl_i2c: Impl. AN2919, rev 5 to calculate FDR/DFSR
Date: Mon, 21 Sep 2009 13:59:04 +0200	[thread overview]
Message-ID: <4AB76A88.4060700@denx.de> (raw)
In-Reply-To: <OFBE4ECC30.9585C961-ONC1257638.003D5FB3-C1257638.003F939F@transmode.se>

Joakim Tjernlund wrote:
> Wolfgang Grandegger <wg@denx.de> wrote on 21/09/2009 12:53:36:
>> Hi Joakim,
>>
>> Joakim Tjernlund wrote:
>>> The latest AN2919 has changed the way FDR/DFSR should be calculated.
>>> Update the driver according to spec. However, Condition 2
>>> is not accounted for as it is not clear how to do so.
>> I compared rev. 5 of AN2919 with rev. 3 and, as you pointed out, it puts
>> additional constraints on how to select dfsr and fdr. Especially dfsr
>> should not exceed a certain, frequency dependent value: dfsr <= 50 /
>> period-in-ns. Therefore, I expected problems with divider values from
>> the table which high dfsr values. I did your "=> date;date;date;date"
>> test on a MPC8548 board using dfsr=43 and fdr=7 but it did not fail.
>> According to the rev. 5, dfsr is not allowed to be greater than 8.
>> Your patch works fine on this board as well. I have no time for a more
>> thorough testing with different CPUs and frequencies. Anyhow...
> 
> Yes, I too notice that higher dfsr values than the spec says works, in
> fact my board needs at least dfsr 8 to be 100% stable but the spec says
> no more that 6 for my board. I suspect that we should enforce a minimum
> value of 8 to be on the safe side, especially as the HW default is 0x10.

You say that the new constraints introduced by rev. 5 are not even
correct!? Well, these modifications are obscure anyhow.

> Anyhow it is better now than before.

At least for your board. Let's keep an eye on people reporting I2C
problems for these processors on the U-Boot and linuxppc-dev ML.

Wolfgang.

  reply	other threads:[~2009-09-21 11:59 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-17  9:07 [U-Boot] [PATCH 1/3] fsl_i2c: Wait for STOP condition to propagate Joakim Tjernlund
2009-09-17  9:07 ` [U-Boot] [PATCH 2/3] fsl_i2c: Add CONFIG_FSL_I2C_CUSTOM_{DFSR/FDR} Joakim Tjernlund
2009-09-17  9:07   ` [U-Boot] [PATCH 3/3] fsl_i2c: Impl. AN2919, rev 5 to calculate FDR/DFSR Joakim Tjernlund
2009-09-17 12:04     ` Heiko Schocher
2009-09-21 10:53     ` Wolfgang Grandegger
2009-09-21 11:34       ` Joakim Tjernlund
2009-09-21 11:59         ` Wolfgang Grandegger [this message]
2009-09-21 12:30           ` Joakim Tjernlund
2009-09-17 12:03   ` [U-Boot] [PATCH 2/3] fsl_i2c: Add CONFIG_FSL_I2C_CUSTOM_{DFSR/FDR} Heiko Schocher
2009-09-17 14:38   ` Timur Tabi
2009-09-17 18:11     ` Joakim Tjernlund
2009-09-17 12:03 ` [U-Boot] [PATCH 1/3] fsl_i2c: Wait for STOP condition to propagate Heiko Schocher
2009-09-17 12:37   ` Joakim Tjernlund
2009-09-22 20:57 ` Wolfgang Denk
2009-09-23  7:58   ` Joakim Tjernlund
2009-09-23  9:02     ` Heiko Schocher
2009-09-23  9:14       ` Joakim Tjernlund
2009-09-23 12:19         ` Heiko Schocher

Reply instructions:

You may reply publicly to this message via plain-text email
using any one of the following methods:

* Save the following mbox file, import it into your mail client,
  and reply-to-all from there: mbox

  Avoid top-posting and favor interleaved quoting:
  https://en.wikipedia.org/wiki/Posting_style#Interleaved_style

* Reply using the --to, --cc, and --in-reply-to
  switches of git-send-email(1):

  git send-email \
    --in-reply-to=4AB76A88.4060700@denx.de \
    --to=wg@denx.de \
    --cc=u-boot@lists.denx.de \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html

* If your mail client supports setting the In-Reply-To header
  via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox