public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] Odd value for I2C_TIMEOUT in fsl_i2c.c
Date: Fri, 04 Sep 2009 10:12:18 -0500	[thread overview]
Message-ID: <4AA12E52.2080403@freescale.com> (raw)
In-Reply-To: <20090904150135.E88CB832E8DE@gemini.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

  reply	other threads:[~2009-09-04 15:12 UTC|newest]

Thread overview: 20+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-09-03 15:22 [U-Boot] Odd value for I2C_TIMEOUT in fsl_i2c.c Timur Tabi
2009-09-04  7:16 ` Heiko Schocher
2009-09-04  9:25   ` Wolfgang Denk
2009-09-04 14:09     ` Timur Tabi
2009-09-04 15:01       ` Wolfgang Denk
2009-09-04 15:12         ` Timur Tabi [this message]
2009-09-04 15:28           ` Peter Tyser
2009-09-04 15:30             ` Timur Tabi
2009-09-04 16:04               ` Peter Tyser
2009-09-04 18:30               ` Wolfgang Denk
2009-09-04 18:39                 ` Timur Tabi
2009-09-04 19:28                   ` Wolfgang Denk
2009-09-04 18:28             ` Wolfgang Denk
2009-09-04 15:29           ` Wolfgang Denk
2009-09-04 18:34             ` Scott Wood
2009-09-04 19:23               ` Wolfgang Denk
2009-09-04 19:28                 ` Scott Wood
2009-09-04  8:31 ` Wolfgang Denk
2009-09-04 18:36   ` Scott Wood
2009-09-04 19:27     ` Wolfgang Denk

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=4AA12E52.2080403@freescale.com \
    --to=timur@freescale.com \
    --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