Grant Likely <> said on :

quoted

quoted

quoted

                               };

=20
This should look like:

quoted

                               eeprom@50 {
                                       compatible =3D "eeprom";

=20
=20
The new eeprom driver is at24, eeprom is the old one. at24 has write
support.=20
=20
EEPROMs from most vendors (AT24)
=20
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:=20
=20
24c00, 24c01, 24c02, spd (readonly 24c02), 24c04, 24c08, 24c16,
24c32, 24c64, 24c128, 24c256, 24c512, 24c1024

=20
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".
=20

Ok, here is what I used.  I see the nodes created in /sys/bus/i2c/...=20
but I see four of them at address 0x50,0x51,0x52,0x53.  That surprised
me since I only have 3 of them in the device tree.  However, in any case
I did not see a way to read or write them.  In one case I was able to
cat the file "eeprom", but it was only 256 bytes and did not exist for
the other 3 devices.  Here is the section of my device tree ... I do=20
see the controller being initialized in dmesg, it is just the read and
write that is eluding me.

One question I did have was within another sample device tree, there was
a comment that "this makes address 0x50 and 0x51"?  Does that mean that
large eeproms are spread over several nodes?  I searched around but
could
not find an example of how to use this at24 to access my E2 from
userspace.

Thanks
Ayman


                        IIC0: i2c@ef600700 {
                                compatible =3D "ibm,iic-460ex", =
"ibm,iic";
                                reg =3D <0xef600700 0x00000014>;
                                interrupt-parent =3D <&UIC0>;
                                interrupts =3D <0x2 0x4>;
                                #address-cells =3D <1>;
                                #size-cells =3D <0>;

                                at24@50 {
                                        compatible =3D "at24,at24c128";
                                        reg =3D <0x50>;
                                };
                                at24@52 {
                                        compatible =3D "at24,at24c128";
                                        reg =3D <0x52>;
                                };
                                at24@53 {
                                        compatible =3D "at24,at24c128";
                                        reg =3D <0x53>;
                                };
				}