linuxppc-dev.lists.ozlabs.org archive mirror
 help / color / mirror / Atom feed
From: Sebastian Siewior <linuxppc-embedded@ml.breakpoint.cc>
To: Grant Likely <grant.likely@secretlab.ca>
Cc: Ayman El-Khashab <AymanE@tanisys.com>,
	devicetree-discuss@ozlabs.org, Linuxppc-embedded@ozlabs.org
Subject: Re: Device tree configuration for I2C eeprom
Date: Fri, 19 Sep 2008 10:12:31 +0200	[thread overview]
Message-ID: <20080919081231.GA9252@Chamillionaire.breakpoint.cc> (raw)
In-Reply-To: <20080919074458.GA7602@secretlab.ca>

* Grant Likely | 2008-09-19 00:44:58 [-0700]:

>Do not fall into the temptation of writing the device tree to reflect
>the current implementation of the operating system.  Stick to
>established conventions and documented bindings.
>
>That being said, it is a non-issue in this case.  The current Linux OF
>support code automagically strips off the manufacturer prefix when
>registering I2C devices.  Take a look at of_modalias_node() in
>drivers/of/base.c for details.
Thanks for this information.

>
>g.

Sebastian

  reply	other threads:[~2008-09-19  8:12 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 [this message]
2008-11-04 16:28         ` Grant Likely
2008-11-04 16:29           ` Grant Likely
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=20080919081231.GA9252@Chamillionaire.breakpoint.cc \
    --to=linuxppc-embedded@ml.breakpoint.cc \
    --cc=AymanE@tanisys.com \
    --cc=Linuxppc-embedded@ozlabs.org \
    --cc=devicetree-discuss@ozlabs.org \
    --cc=grant.likely@secretlab.ca \
    /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).