From: Geert Uytterhoeven <geert@linux-m68k.org>
To: Javier Martinez Canillas <javier@dowhile0.org>
Cc: "Rob Herring" <robh@kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"Mark Rutland" <mark.rutland@arm.com>,
"Andrew Lunn" <andrew@lunn.ch>,
"Wolfram Sang" <wsa@the-dreams.de>,
"Tony Lindgren" <tony@atomide.com>,
"Catalin Marinas" <catalin.marinas@arm.com>,
"Will Deacon" <will.deacon@arm.com>,
"Russell King" <linux@armlinux.org.uk>,
"Masahiro Yamada" <yamada.masahiro@socionext.com>,
"Paul Mackerras" <paulus@samba.org>,
"Linux I2C" <linux-i2c@vger.kernel.org>,
"Hongtao Jia" <hongtao.jia@nxp.com>,
"David Lechner" <david@lechnology.com>,
"Herbert Xu" <herbert@gondor.apana.org.au>,
"Horia Geantă" <horia.geanta@nxp.com>,
"Michael Ellerman" <mpe@ellerman.id.au>,
"Magnus Damm" <magnus.damm@gmail.com>,
"Michal Simek" <michal.simek@xilinx.com>,
"Andy Shevchenko" <andy.shevchenko@gmail.com>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
"Benjamin Herrenschmidt" <benh@kernel.crashing.org>,
"Jason Cooper" <jason@lakedaemon.net>,
"Sebastian Hesselbarth" <sebastian.hesselbarth@gmail.com>,
"devicetree@vger.kernel.org" <devicetree@vger.kernel.org>,
"Mark Jackson" <mpfj@newflow.co.uk>,
"Sekhar Nori" <nsekhar@ti.com>,
"Joachim Eastwood" <manabian@gmail.com>,
"Stuart Yoder" <stuart.yoder@nxp.com>,
"Scott Wood" <oss@buserror.net>,
"Simon Horman" <horms@verge.net.au>,
"Santosh Shilimkar" <ssantosh@kernel.org>,
"Gregory Clement" <gregory.clement@free-electrons.com>,
"linux-omap@vger.kernel.org" <linux-omap@vger.kernel.org>,
"Sascha Hauer" <kernel@pengutronix.de>,
"Sören Brinkmann" <soren.brinkmann@xilinx.com>,
"Florian Larysch" <fl@n621.de>,
"linuxppc-dev@lists.ozlabs.org" <linuxppc-dev@lists.ozlabs.org>,
"Li Yang" <leoyang.li@nxp.com>,
Linux-Renesas <linux-renesas-soc@vger.kernel.org>,
"Dinh Nguyen" <dinguyen@kernel.org>,
"Benoît Cousson" <bcousson@baylibre.com>,
"Fabio Estevam" <fabio.estevam@nxp.com>,
"Shawn Guo" <shawnguo@kernel.org>
Subject: Re: [PATCH v4 00/20] eeprom: at24: Add OF device ID table
Date: Mon, 22 May 2017 21:30:22 +0200 [thread overview]
Message-ID: <CAMuHMdVaY6J04TL=cEBVkCx=qhQuvbprxXt4VCjh_oEedRYnzg@mail.gmail.com> (raw)
In-Reply-To: <CABxcv==8R5_tG8-rsp-9UdS_5N7X8QXkd0OFnN63Ct7L2jFvhA@mail.gmail.com>
Hi Javier,
On Mon, May 22, 2017 at 7:15 PM, Javier Martinez Canillas
<javier@dowhile0.org> wrote:
>>> 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@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
next prev parent reply other threads:[~2017-05-22 19:30 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-05-22 14:01 [PATCH v4 00/20] eeprom: at24: Add OF device ID table Javier Martinez Canillas
2017-05-22 14:02 ` [PATCH v4 16/20] powerpc/5200: Add generic compatible string for I2C EEPROM Javier Martinez Canillas
2017-05-22 14:02 ` [PATCH v4 17/20] powerpc/fsl: " Javier Martinez Canillas
2017-05-22 14:02 ` [PATCH v4 18/20] powerpc/512x: " Javier Martinez Canillas
2017-05-22 14:02 ` [PATCH v4 19/20] powerpc/83xx: " Javier Martinez Canillas
2017-05-23 13:42 ` Rob Herring
2017-05-23 13:49 ` Javier Martinez Canillas
2017-05-22 14:02 ` [PATCH v4 20/20] powerpc/44x: " Javier Martinez Canillas
2017-05-22 14:23 ` [PATCH v4 00/20] eeprom: at24: Add OF device ID table Geert Uytterhoeven
2017-05-22 14:26 ` Rob Herring
2017-05-22 14:46 ` Javier Martinez Canillas
2017-05-22 16:52 ` Rob Herring
2017-05-22 17:15 ` Javier Martinez Canillas
2017-05-22 19:30 ` Geert Uytterhoeven [this message]
2017-05-22 19:39 ` Javier Martinez Canillas
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='CAMuHMdVaY6J04TL=cEBVkCx=qhQuvbprxXt4VCjh_oEedRYnzg@mail.gmail.com' \
--to=geert@linux-m68k.org \
--cc=andrew@lunn.ch \
--cc=andy.shevchenko@gmail.com \
--cc=bcousson@baylibre.com \
--cc=benh@kernel.crashing.org \
--cc=catalin.marinas@arm.com \
--cc=david@lechnology.com \
--cc=devicetree@vger.kernel.org \
--cc=dinguyen@kernel.org \
--cc=fabio.estevam@nxp.com \
--cc=fl@n621.de \
--cc=gregory.clement@free-electrons.com \
--cc=herbert@gondor.apana.org.au \
--cc=hongtao.jia@nxp.com \
--cc=horia.geanta@nxp.com \
--cc=horms@verge.net.au \
--cc=jason@lakedaemon.net \
--cc=javier@dowhile0.org \
--cc=kernel@pengutronix.de \
--cc=leoyang.li@nxp.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-i2c@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-omap@vger.kernel.org \
--cc=linux-renesas-soc@vger.kernel.org \
--cc=linux@armlinux.org.uk \
--cc=linuxppc-dev@lists.ozlabs.org \
--cc=magnus.damm@gmail.com \
--cc=manabian@gmail.com \
--cc=mark.rutland@arm.com \
--cc=michal.simek@xilinx.com \
--cc=mpe@ellerman.id.au \
--cc=mpfj@newflow.co.uk \
--cc=nsekhar@ti.com \
--cc=oss@buserror.net \
--cc=paulus@samba.org \
--cc=robh@kernel.org \
--cc=sebastian.hesselbarth@gmail.com \
--cc=shawnguo@kernel.org \
--cc=soren.brinkmann@xilinx.com \
--cc=ssantosh@kernel.org \
--cc=stuart.yoder@nxp.com \
--cc=tony@atomide.com \
--cc=will.deacon@arm.com \
--cc=wsa@the-dreams.de \
--cc=yamada.masahiro@socionext.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).