All of lore.kernel.org
 help / color / mirror / Atom feed
From: Stephan Linz <linz@mazet.de>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Proposal to add "ispeed" (I2C speed) command
Date: Thu, 4 Mar 2004 16:08:08 +0100	[thread overview]
Message-ID: <04030416080802.12732@pcj86> (raw)
In-Reply-To: <20040304132105.AE2E8C0655@atlas.denx.de>

Am Donnerstag,  4. M?rz 2004 14:21 schrieb Wolfgang Denk:
> In message <04030413332001.12732@pcj86> you wrote:
> > This 'could' be usefull to speed up the i2c communication if there are
> > more than one i2c devices with significant differences between the clock
> > timing; ex. 27C32 (100kHz at 3.3V) and LM75 (400kHz). Tolunay has spoken
> > about like this. But right I see now reason to do so, too. U-Boot has to
                             ^^^^^^^^^
OOPS, this was a small but fine typing error, should be:

" ... But right I see _NO_ reason to do so, too. ... "


(that's life)

> > be a boot loader not a performant operator...
>
> Do you think it is legal to clock the I2C bus at 400 kHz  when  there
> are  devices  on  the bus that are spec'ed only for 100 kHz? I may be
> wrong, but such an idea sounds awfully risky to me.

You're right, see above :-)


Best Regards,
Stephan Linz

  reply	other threads:[~2004-03-04 15:08 UTC|newest]

Thread overview: 10+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2004-03-03 17:36 [U-Boot-Users] Proposal to add "ispeed" (I2C speed) command listmember at orkun.us
2004-03-04  8:48 ` Stephan Linz
2004-03-04 15:58   ` listmember at orkun.us
2004-03-04 16:13     ` Wolfgang Denk
2004-03-04  9:11 ` Wolfgang Denk
2004-03-04 12:33   ` Stephan Linz
2004-03-04 13:21     ` Wolfgang Denk
2004-03-04 15:08       ` Stephan Linz [this message]
2004-03-04 16:10   ` listmember at orkun.us
2004-03-04 16:36     ` 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=04030416080802.12732@pcj86 \
    --to=linz@mazet.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.