public inbox for linux-arm-kernel@lists.infradead.org 
 help / color / mirror / Atom feed
From: b-cousson@ti•com (Cousson, Benoit)
To: linux-arm-kernel@lists•infradead.org
Subject: [PATCH v2 09/10] arm/dts: omap3-beagle: Add twl4030 and i2c EEPROM
Date: Tue, 10 Jan 2012 11:09:05 +0100	[thread overview]
Message-ID: <4F0C0E41.1020405@ti.com> (raw)
In-Reply-To: <CAOZdJXU9w1O69ZgNEmgUZfezXEyn1JTyZxgmmLXAb3-mtJLnOA@mail.gmail.com>

On 1/10/2012 12:24 AM, Tabi Timur-B04825 wrote:
> On Fri, Dec 9, 2011 at 8:02 AM, Benoit Cousson<b-cousson@ti•com>  wrote:
>>
>> +       eeprom at 50 {
>> +               compatible = "ti,eeprom";
>> +               reg =<0x50>;
>> +       };
>
> Why is this "ti,"?  For EDID, isn't the I2C device actually on the
> monitor itself, and DVI cable just connects to the I2C bus?

Yes, in fact I didn't know what to put here, since I do not know what 
kind of eeprom the monitor will use.

And then I realized that the i2c driver is using the compatible name 
without the prefix, so any prefix can be used there...
OK, that's maybe not a very valid reason... but I did not find any 
better prefix at that time:-)

> The reason I ask is that I'm trying to do the same thing for a PowerPC
> board.  I need to defined an EDID I2C node.

Well, this seems to be generic i2c eeprom, so maybe a "ddc," prefix or 
"edid," will be a little bit better.

If later, we want to access that node from the display driver, we can 
just add a phandle to the node's label: "edid-eeprom: eeprom at 50:"

Regards,
Benoit

  reply	other threads:[~2012-01-10 10:09 UTC|newest]

Thread overview: 41+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-12-09 14:02 [PATCH v2 00/10] OMAP4: Add DT support for i2c and twl6030 Benoit Cousson
2011-12-09 14:02 ` [PATCH v2 01/10] ARM: OMAP2+: pm: Do not init statically the SR and voltage layer with DT Benoit Cousson
2012-01-04 18:04   ` Grant Likely
2011-12-09 14:02 ` [PATCH v2 02/10] i2c: OMAP: Add DT support for i2c controller Benoit Cousson
2011-12-14  1:06   ` Kevin Hilman
2012-01-04 13:36     ` Cousson, Benoit
2012-01-04 18:08       ` Grant Likely
2012-01-04 21:28       ` Kevin Hilman
2012-01-04 21:56         ` Grant Likely
2011-12-14 16:58   ` Rob Herring
2011-12-15 15:05     ` Cousson, Benoit
2011-12-15 15:48       ` Rob Herring
2011-12-15 16:09         ` Cousson, Benoit
2011-12-22  8:22   ` Shubhrajyoti
2011-12-09 14:02 ` [PATCH v2 03/10] mfd: twl-core: Add initial DT support for twl4030/twl6030 Benoit Cousson
2011-12-19 12:03   ` Samuel Ortiz
2011-12-19 13:53     ` Cousson, Benoit
2012-01-04 18:12   ` Grant Likely
2012-01-05 10:21     ` Cousson, Benoit
2011-12-09 14:02 ` [PATCH v2 04/10] rtc: rtc-twl: Add DT support for RTC inside twl4030/twl6030 Benoit Cousson
2011-12-19 16:52   ` Cousson, Benoit
2011-12-26  1:18     ` Alessandro Zummo
2011-12-20 15:13   ` Cousson, Benoit
2012-01-04 18:13   ` Grant Likely
2011-12-09 14:02 ` [PATCH v2 05/10] arm/dts: OMAP4: Add i2c controller nodes Benoit Cousson
2012-01-04 18:13   ` Grant Likely
2011-12-09 14:02 ` [PATCH v2 06/10] arm/dts: OMAP3: " Benoit Cousson
2012-01-04 18:14   ` Grant Likely
2011-12-09 14:02 ` [PATCH v2 07/10] arm/dts: omap4-panda: Add twl6030 and i2c EEPROM Benoit Cousson
2011-12-14  5:06   ` Kevin Hilman
2011-12-14 16:50     ` Cousson, Benoit
2011-12-15  0:31       ` Kevin Hilman
2012-01-04 18:14   ` Grant Likely
2011-12-09 14:02 ` [PATCH v2 08/10] arm/dts: omap4-sdp: Add twl6030, i2c3 and i2c4 devices Benoit Cousson
2012-01-04 18:14   ` Grant Likely
2011-12-09 14:02 ` [PATCH v2 09/10] arm/dts: omap3-beagle: Add twl4030 and i2c EEPROM Benoit Cousson
2012-01-04 18:15   ` Grant Likely
2012-01-09 23:24   ` Tabi Timur-B04825
2012-01-10 10:09     ` Cousson, Benoit [this message]
2011-12-09 14:02 ` [PATCH v2 10/10] ARM: OMAP2+: board-generic: Remove i2c static init Benoit Cousson
2012-01-04 18:15   ` Grant Likely

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=4F0C0E41.1020405@ti.com \
    --to=b-cousson@ti$(echo .)com \
    --cc=linux-arm-kernel@lists$(echo .)infradead.org \
    /path/to/YOUR_REPLY

  https://kernel.org/pub/software/scm/git/docs/git-send-email.html
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