From: Wolfram Sang <wsa@the-dreams.de>
To: Simon Horman <horms@verge.net.au>, devicetree@vger.kernel.org
Cc: Geert Uytterhoeven <geert@linux-m68k.org>,
Sergei Shtylyov <sergei.shtylyov@cogentembedded.com>,
Linux-sh list <linux-sh@vger.kernel.org>,
"linux-arm-kernel@lists.infradead.org"
<linux-arm-kernel@lists.infradead.org>,
Magnus Damm <magnus.damm@gmail.com>,
Wolfram Sang <wsa@sang-engineering.com>
Subject: I2C eeprom compatibles? (was Re: [PATCH/RFC 03/19] ARM: shmobile: gose: add i2c2 bus to device tree)
Date: Fri, 18 Dec 2015 08:35:32 +0100 [thread overview]
Message-ID: <20151218073531.GA1517@katana> (raw)
In-Reply-To: <20151218030239.GB10973@verge.net.au>
[-- Attachment #1: Type: text/plain, Size: 1746 bytes --]
On Fri, Dec 18, 2015 at 12:02:39PM +0900, Simon Horman wrote:
> On Mon, Dec 14, 2015 at 10:39:47AM +0100, Geert Uytterhoeven wrote:
> > On Mon, Dec 14, 2015 at 8:11 AM, Wolfram Sang <wsa@the-dreams.de> wrote:
> > >> > >+ eeprom@50 {
> > >> > >+ compatible = "renesas,24c02";
> > >> >
> > >> > This is not a valid value -- the Renesas chip model is different from 24c02.
> > >>
> > >> I copied this value from r8a7791.dtsi.
> > >>
> > >> Looking at the schematic for gose (v100), koelsch (rev024) and porter (v300)
> > >> I see the following "R1EX24002ATAS0G#U0". Shall we update r8a7791 and
> > >> this patch to "renesas,24002" or leave things as is?
> > >
> > > I wouldn't like to update the at24 driver with all namings from all
> > > vendors for chips which in large cases are simple 24c02 devices.
> > >
> > > So, if Sergei insists on the change, I'd propose
> > >
> > > compatible = "renesas,24002", "24c02";
> >
> > "renesas,r1ex24002"?
> >
> > I don't think the "A" is relevant (<= 64 is A, >= 128 is B).
> >
> > http://www.renesas.com/products/memory/eeprom/product_selector.jsp
>
> Thanks.
>
> It seems to me that we have some consensus around:
>
> compatible = "renesas,r1ex24002", "24c02";
Thinking again, "generic,24c02" or "generic-24c02" could also be an
option.
> Should this be added to Documentation/devicetree/bindings/eeprom/eeprom.txt ?
> Or documented elsewhere?
Probably we need a DT maintainers advice here? I don't mind vendor
specific compatibles being documented, but I'm reluctant to add all
these compatibles for the myriads of I2C eeproms to the at24 driver. 99%
are covered by the generic case.
Adding DT to CC.
Thanks,
Wolfram
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
next parent reply other threads:[~2015-12-18 7:35 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <1449802376-11301-1-git-send-email-horms+renesas@verge.net.au>
[not found] ` <1449802376-11301-4-git-send-email-horms+renesas@verge.net.au>
[not found] ` <566AB2A5.4090105@cogentembedded.com>
[not found] ` <20151214021110.GD13945@verge.net.au>
[not found] ` <20151214071103.GC1516@katana>
[not found] ` <CAMuHMdXWcyEmoVRZuCTM4yqfxXYjgZF1yP8uqCEU8Bj=pmkNYw@mail.gmail.com>
[not found] ` <20151218030239.GB10973@verge.net.au>
2015-12-18 7:35 ` Wolfram Sang [this message]
2015-12-18 9:06 ` I2C eeprom compatibles? (was Re: [PATCH/RFC 03/19] ARM: shmobile: gose: add i2c2 bus to device tree) Arnd Bergmann
2015-12-18 10:32 ` Wolfram Sang
2015-12-21 4:33 ` Simon Horman
2015-12-21 8:02 ` Geert Uytterhoeven
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=20151218073531.GA1517@katana \
--to=wsa@the-dreams.de \
--cc=devicetree@vger.kernel.org \
--cc=geert@linux-m68k.org \
--cc=horms@verge.net.au \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-sh@vger.kernel.org \
--cc=magnus.damm@gmail.com \
--cc=sergei.shtylyov@cogentembedded.com \
--cc=wsa@sang-engineering.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).