From: "Grant Likely" <grant.likely@secretlab.ca>
To: "Sebastian Siewior" <linuxppc-embedded@ml.breakpoint.cc>
Cc: Ayman El-Khashab <AymanE@tanisys.com>,
devicetree-discuss@ozlabs.org, Linuxppc-embedded@ozlabs.org
Subject: Re: Device tree configuration for I2C eeprom
Date: Tue, 4 Nov 2008 09:29:09 -0700 [thread overview]
Message-ID: <fa686aa40811040829r4b68fb4axde8612cc3d06cca@mail.gmail.com> (raw)
In-Reply-To: <fa686aa40811040828y23d0d65bsebc3f542c57291a@mail.gmail.com>
On Tue, Nov 4, 2008 at 9:28 AM, Grant Likely <grant.likely@secretlab.ca> wrote:
> On Fri, Sep 19, 2008 at 12:12 AM, Sebastian Siewior
> <linuxppc-embedded@ml.breakpoint.cc> wrote:
>> * Grant Likely | 2008-09-18 22:04:41 [-0700]:
>>
>>>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".
>>
>> What about the i2c drivers which don't have any prefix like the m41t80?
>> Prior commit 0d1cde2 aka "powerpc/i2c: Convert i2c-mpc into an
>> of_platform driver" the ids were converted.
>
> That is the *driver* not the device tree description. The OF i2c code
> is still converts the name. By default it does this by simply
> stripping off the manufacturer prefix, but the match table does still
> exist when the default behavior needs to be overridden.
Oops, I already replied to this one. Sorry for the duplicate response.
g.
--
Grant Likely, B.Sc., P.Eng.
Secret Lab Technologies Ltd.
next prev parent reply other threads:[~2008-11-04 16:29 UTC|newest]
Thread overview: 15+ messages / expand[flat|nested] mbox.gz Atom feed top
2008-09-18 19:44 Device tree configuration for I2C eeprom Ayman El-Khashab
2008-09-18 22:13 ` Sebastian Siewior
2008-09-18 22:21 ` Jon Smirl
2008-09-19 5:04 ` Grant Likely
2008-09-19 7:12 ` Sebastian Siewior
2008-09-19 7:44 ` Grant Likely
2008-09-19 8:12 ` Sebastian Siewior
2008-11-04 16:28 ` Grant Likely
2008-11-04 16:29 ` Grant Likely [this message]
2008-11-04 17:17 ` Sebastian Andrzej Siewior
2008-11-04 16:07 ` Ayman El-Khashab
2008-11-04 16:45 ` Felix Radensky
2008-11-04 19:52 ` Ayman El-Khashab
2008-11-04 20:04 ` Felix Radensky
2008-11-04 21:00 ` Ayman El-Khashab
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=fa686aa40811040829r4b68fb4axde8612cc3d06cca@mail.gmail.com \
--to=grant.likely@secretlab.ca \
--cc=AymanE@tanisys.com \
--cc=Linuxppc-embedded@ozlabs.org \
--cc=devicetree-discuss@ozlabs.org \
--cc=linuxppc-embedded@ml.breakpoint.cc \
/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).