From: Eugene Surovegin <ebs@ebshome.net>
To: "Robert P. J. Day" <rpjday@mindspring.com>
Cc: Embedded PPC Linux list <linuxppc-embedded@ozlabs.org>
Subject: Re: "I2C" versus "IIC"
Date: Wed, 13 Oct 2004 12:34:23 -0700 [thread overview]
Message-ID: <20041013193423.GA28349@gate.ebshome.net> (raw)
In-Reply-To: <Pine.LNX.4.60.0410131423540.12426@localhost.localdomain>
On Wed, Oct 13, 2004 at 02:26:23PM -0400, Robert P. J. Day wrote:
>
> i was just about to rename some of my variables and macros to be
> consistent with what i *thought* was the standard nomenclature of
> "IIC" as opposed to "I2C". just checked include/asm-ppc, and grepped
> for case-insensitive instances of both strings ... oh, god. there's
> really no preferred usage, is there?
Philips' documentation uses I2C, not IIC, so I guess this is
_official_ name of the _bus_.
Some vendors (like IBM in their 4xx parts) use IIC to name I2C
_interface_ to distinguish it from I2C _bus_ (they specifically
mention this in the chip manual).
For example, in the corresponding 4xx driver I used "iic" because it
was written for IBM IIC _interface_.
--
Eugene.
next prev parent reply other threads:[~2004-10-13 19:34 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2004-10-13 18:26 "I2C" versus "IIC" Robert P. J. Day
2004-10-13 18:50 ` Mark Chambers
2004-10-13 18:56 ` Robert P. J. Day
2004-10-13 19:10 ` annamaya
2004-10-13 19:34 ` Eugene Surovegin [this message]
2004-10-13 19:40 ` Robert P. J. Day
-- strict thread matches above, loose matches on Subject: below --
2004-10-13 20:18 VanBaren, Gerald (AGRE)
2004-10-13 20:26 ` Matt Porter
2004-10-13 20:48 ` Mark Chambers
2004-10-13 20:54 ` Matt Porter
2004-10-13 21:04 ` Matt Porter
2004-10-13 21:44 ` Mark Chambers
2004-10-13 21:14 ` Eugene Surovegin
2004-10-13 21:18 ` Matt Porter
2004-10-13 21:19 ` Robert P. J. Day
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=20041013193423.GA28349@gate.ebshome.net \
--to=ebs@ebshome.net \
--cc=linuxppc-embedded@ozlabs.org \
--cc=rpjday@mindspring.com \
/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;
as well as URLs for NNTP newsgroup(s).