Thread (21 messages) 21 messages, 3 authors, 2017-05-22

[PATCH v4 00/20] eeprom: at24: Add OF device ID table

From: geert@linux-m68k.org (Geert Uytterhoeven)
Date: 2017-05-22 19:30:22
Also in: linux-devicetree, linux-i2c, linux-omap, linuxppc-dev

Hi Javier,

On Mon, May 22, 2017 at 7:15 PM, Javier Martinez Canillas
[off-list ref] wrote:
quoted
quoted
I also wonder why this is really needed if AFAIU "renesas,24c02" is
compatible with "atmel,24c02". IOW, the driver doesn't need to
differentiate between the two since the devices are the same and will
always match using "atmel,24c02".
It is needed, so that when a difference is found, it can be handled
without updating the DT.
Yes, I understand this. What I tried to ask is if there could really
be a difference for the same chip type between different vendors, or
is just that people were using other manufacturers in the compatible
string as a consequence of the DT binding doc and the I2C core
ignoring the vendor prefix.
The devices from different vendors are not the same. They contain FLASH
ROM of a specific size, and glue logic to expose an i2c slave
interface providing
an AT24-compatible command set.  They should behave similar within
the limits of the AT24 "spec".  But the actual implementation may be different.
I don't mind though, I will leave the manufacturers that are different
than the atmel variants in the mainline DTS as you and Geert asked.
OK, thanks!

Gr{oetje,eeting}s,

                        Geert

--
Geert Uytterhoeven -- There's lots of Linux beyond ia32 -- geert at linux-m68k.org

In personal conversations with technical people, I call myself a hacker. But
when I'm talking to journalists I just say "programmer" or something like that.
                                -- Linus Torvalds
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help