Thread (12 messages) 12 messages, 5 authors, 2008-11-04

Re: Device tree configuration for I2C eeprom

From: Grant Likely <hidden>
Date: 2008-09-19 05:04:41
Also in: linux-devicetree

Possibly related (same subject, not in this thread)

On Thu, Sep 18, 2008 at 06:21:36PM -0400, Jon Smirl wrote:
On Thu, Sep 18, 2008 at 6:13 PM, Sebastian Siewior
[off-list ref] wrote:
quoted
quoted
                               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.
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help