public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Jerry Van Baren <gerald.vanbaren@smiths-aerospace.com>
To: u-boot@lists.denx.de
Subject: [U-Boot-Users] Please pull u-boot-83xx.git (I2C rework)
Date: Tue, 28 Nov 2006 13:25:07 -0500	[thread overview]
Message-ID: <456C7F03.9060409@smiths-aerospace.com> (raw)
In-Reply-To: <1164737878.31193.38.camel@saruman.qstreams.net>

Ben Warren wrote:
> On Tue, 2006-11-28 at 12:04 -0600, Timur Tabi wrote:
>> Joakim Tjernlund wrote:
>>
>>> I think that the I2C_READ and I2C_WRITE #defines in fsl_i2c.h conflicts
>>> with
>>> soft I2C.
>> Can you be more specific?  These two macros are defined in a variety of ways in 
>> U-Boot.  Soft I2C is not used on any Freescale parts (AFAIK).
>>
> While it's not used on any Freescale evaluation boards, it could
> certainly be implemented on boards with Freescale CPUs.  I'm not sure
> why you'd bit-bang I2C if you have nice hardware controllers, but there
> may be situations where this makes sense.  On the other hand, I don't
> know if SOFT_I2C and HARD_I2C can co-exist.
> 
> Either way, I don't think we should preclude the use of SOFT I2C on
> Freescale CPUs.
> 
> regards,
> Ben

It is used on some boards with Mot/Freescale CPUs, the WindRiver (EST) 
SBC8260 for example (although configurable hard vs. soft IIRC).  The 
hardware i2c can be more effort than it is worth compared to bit-banging 
it.  Perhaps the new QUICCs are easier to use, perhaps y'all are just 
smarter than we were back then.  :-)

gvb

  reply	other threads:[~2006-11-28 18:25 UTC|newest]

Thread overview: 25+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2006-11-28 13:54 [U-Boot-Users] Please pull u-boot-83xx.git (I2C rework) Joakim Tjernlund
2006-11-28 18:04 ` Timur Tabi
2006-11-28 18:17   ` Ben Warren
2006-11-28 18:25     ` Jerry Van Baren [this message]
2006-11-28 18:31     ` Pantelis Antoniou
2006-11-28 19:56       ` Timur Tabi
2006-11-28 18:43     ` Joakim Tjernlund
2006-11-28 21:03     ` Wolfgang Denk
2006-11-28 21:09       ` Tolunay Orkun
2006-11-29 16:50         ` Wolfgang Denk
2006-11-28 21:03   ` Wolfgang Denk
2006-11-28 21:08     ` Timur Tabi
2006-11-28 21:39       ` Joakim Tjernlund
2006-11-28 22:16         ` Timur Tabi
2006-11-28 22:25           ` Joakim Tjernlund
2006-11-28 22:46             ` Timur Tabi
2006-11-28 22:49           ` Joakim Tjernlund
2006-11-29 13:20             ` Jerry Van Baren
2006-11-28 21:47       ` Ben Warren
2006-11-29 16:49       ` Wolfgang Denk
  -- strict thread matches above, loose matches on Subject: below --
2006-11-30 10:00 Joakim Tjernlund
2006-11-04  2:11 [U-Boot-Users] Please pull u-boot-83xx.git Kim Phillips
2006-11-26 13:49 ` [U-Boot-Users] Please pull u-boot-83xx.git (I2C rework) Stefan Roese
2006-11-27  2:45   ` Ben Warren
2006-11-27  6:22     ` Stefan Roese
2006-11-27 17:28   ` Timur Tabi

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=456C7F03.9060409@smiths-aerospace.com \
    --to=gerald.vanbaren@smiths-aerospace.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