From: Timur Tabi <timur@freescale.com>
To: u-boot@lists.denx.de
Subject: [U-Boot] fsl_i2c: increase I2C timeout values and make them configurable
Date: Thu, 10 Sep 2009 10:22:38 -0500 [thread overview]
Message-ID: <4AA919BE.20602@freescale.com> (raw)
In-Reply-To: <OFA127F531.FC78FF44-ONC125762D.004BAA88-C125762D.004CC9E8@transmode.se>
Joakim Tjernlund wrote:
> Come on, just because my board is somewhat broken, it doesn't mean the
> driver is correct. If I define my speed to 100KHz I get
> a DFSR of 22, way over what is allowed for my board.
Why is a value of 22 over what is allowed on the board? I was under the impression that DFSR and FDR are just two values that work together to create a divider. Is there something special about DFSR?
--
Timur Tabi
Linux kernel developer at Freescale
next prev parent reply other threads:[~2009-09-10 15:22 UTC|newest]
Thread overview: 28+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-09-09 9:19 [U-Boot] fsl_i2c: increase I2C timeout values and make them configurable Joakim Tjernlund
2009-09-09 14:24 ` Timur Tabi
2009-09-09 14:33 ` Joakim Tjernlund
2009-09-10 8:15 ` Joakim Tjernlund
2009-09-10 13:07 ` Timur Tabi
2009-09-10 13:20 ` Joakim Tjernlund
2009-09-10 13:29 ` Timur Tabi
2009-09-10 13:58 ` Joakim Tjernlund
2009-09-10 15:22 ` Timur Tabi [this message]
2009-09-10 15:46 ` Joakim Tjernlund
2009-09-10 15:57 ` Timur Tabi
2009-09-10 14:57 ` Joakim Tjernlund
2009-09-10 15:26 ` Timur Tabi
2009-09-10 15:53 ` Joakim Tjernlund
2009-09-10 16:13 ` Timur Tabi
2009-09-10 16:30 ` Joakim Tjernlund
2009-09-10 17:13 ` Joakim Tjernlund
2009-09-11 8:44 ` Joakim Tjernlund
[not found] ` <4AAA6ACD.9040905@free <4AAE55FA.4070702@freescale.com>
2009-09-11 15:20 ` Timur Tabi
2009-09-14 13:53 ` Detlev Zundel
2009-09-14 14:18 ` Wolfgang Grandegger
2009-09-14 14:40 ` Timur Tabi
2009-09-14 15:54 ` Joakim Tjernlund
2009-09-15 11:53 ` Wolfgang Grandegger
2009-09-15 12:24 ` Joakim Tjernlund
2009-09-15 18:53 ` Joakim Tjernlund
2009-09-14 16:01 ` Wolfgang Grandegger
2009-09-14 16:18 ` Joakim Tjernlund
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=4AA919BE.20602@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