linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Grant Likely <grant.likely@secretlab.ca>
To: Jon Smirl <jonsmirl@gmail.com>
Cc: Ayman El-Khashab <AymanE@tanisys.com>,
	devicetree-discuss@ozlabs.org, Linuxppc-embedded@ozlabs.org
Subject: Re: Device tree configuration for I2C eeprom
Date: Thu, 18 Sep 2008 22:04:41 -0700	[thread overview]
Message-ID: <20080919050441.GD25528@secretlab.ca> (raw)
In-Reply-To: <9e4733910809181521r3cd74119tfedd36567e3b5394@mail.gmail.com>

On Thu, Sep 18, 2008 at 06:21:36PM -0400, Jon Smirl wrote:
> On Thu, Sep 18, 2008 at 6:13 PM, Sebastian Siewior
> <linuxppc-embedded@ml.breakpoint.cc> wrote:
> >>                                eeprom@50 {
> >>                                        compatible = "?????";
> >>                                                   something
> >>                                        something;
> >>                                };
> >
> > This should look like:
> > |                                eeprom@50 {
> > |                                        compatible = "eeprom";
> 
> 
> The new eeprom driver is at24, eeprom is the old one. at24 has write support.
> 
> EEPROMs from most vendors (AT24)
> 
> Enable this driver to get read/write support to most I2C EEPROMs,
> after you configure the driver to know about each EEPROM on
> your target board. Use these generic chip names, instead of
> vendor-specific ones like at24c64 or 24lc02:
> 
> 24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08,
> 24c16, 24c32, 24c64, 24c128, 24c256, 24c512, 24c1024

No, don't use the generic chip names.  Device tree convention is to be
specific and prefix the part number with the vendor name.  ie. You should
be using "at,at24c64", not "24c64".

g.

  reply	other threads:[~2008-09-19  5:04 UTC|newest]

Thread overview: 15+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-18 19:44 Device tree configuration for I2C eeprom Ayman El-Khashab
2008-09-18 22:13 ` Sebastian Siewior
2008-09-18 22:21   ` Jon Smirl
2008-09-19  5:04     ` Grant Likely [this message]
2008-09-19  7:12       ` Sebastian Siewior
2008-09-19  7:44         ` Grant Likely
2008-09-19  8:12           ` Sebastian Siewior
2008-11-04 16:28         ` Grant Likely
2008-11-04 16:29           ` Grant Likely
2008-11-04 17:17             ` Sebastian Andrzej Siewior
2008-11-04 16:07       ` Ayman El-Khashab
2008-11-04 16:45         ` Felix Radensky
2008-11-04 19:52           ` Ayman El-Khashab
2008-11-04 20:04             ` Felix Radensky
2008-11-04 21:00               ` Ayman El-Khashab

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=20080919050441.GD25528@secretlab.ca \
    --to=grant.likely@secretlab.ca \
    --cc=AymanE@tanisys.com \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=jonsmirl@gmail.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).