On 1/10/2012 12:24 AM, Tabi Timur-B04825 wrote:
On Fri, Dec 9, 2011 at 8:02 AM, Benoit Cousson wrote:
+ eeprom@50 {
+ compatible = "ti,eeprom";
+ reg =<0x50>;
+ };
Why is this "ti,"? For EDID, isn't the I2C device actually on the
monitor itself, and D
On Fri, Dec 9, 2011 at 8:02 AM, Benoit Cousson wrote:
>
> + eeprom@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?
Th
On Fri, Dec 09, 2011 at 03:02:40PM +0100, Benoit Cousson wrote:
> Add required clock frequencies for the i2c client devices existing
> on beagle board.
>
> Add the twl4030 basic description with only the twl_rtc module.
>
> Add the EEPROM node.
>
> Based on original patch from Manju:
> http://ww
Add required clock frequencies for the i2c client devices existing
on beagle board.
Add the twl4030 basic description with only the twl_rtc module.
Add the EEPROM node.
Based on original patch from Manju:
http://www.spinics.net/lists/linux-omap/msg55831.html
Signed-off-by: Benoit Cousson
Cc: G
