From mboxrd@z Thu Jan  1 00:00:00 1970
From: Troy Kisky <troy.kisky@boundarydevices.com>
Date: Sat, 02 Jun 2012 17:12:19 -0700
Subject: [U-Boot] [PATCH 9/9] mx6qsabrelite: Add splaschscreen support
In-Reply-To: <CAOMZO5A00kB2wFZgbPLchDWghZW0uCFc+e3NOFw2u_abeRrhSg@mail.gmail.com>
References: <1338485043-21666-1-git-send-email-fabio.estevam@freescale.com>
	<1338485043-21666-9-git-send-email-fabio.estevam@freescale.com>
	<4FC9B6A8.2050903@googlemail.com>
	<CAOMZO5A1==WFLwzfsXSFJDJzYPae50uQ0SJqLGFmA_X83jZLBg@mail.gmail.com>
	<4FCA60E2.9000404@googlemail.com>
	<CAOMZO5A00kB2wFZgbPLchDWghZW0uCFc+e3NOFw2u_abeRrhSg@mail.gmail.com>
Message-ID: <4FCAABE3.8050401@boundarydevices.com>
List-Id: <u-boot.lists.denx.de>
MIME-Version: 1.0
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
To: u-boot@lists.denx.de

On 6/2/2012 3:36 PM, Fabio Estevam wrote:
> Hi Dirk,
>
> On Sat, Jun 2, 2012 at 3:52 PM, Dirk Behme<dirk.behme@googlemail.com>  wrote:
>
>> Maybe you could check [1]
>>
>> -#define CONFIG_SYS_I2C_SLAVE            0xfe
>> +#define CONFIG_SYS_I2C_SLAVE    0x1f
>>
>> then? I'm no I2C expert and I wasn't sure what to use for
>> CONFIG_SYS_I2C_SLAVE.
> Yes, 0x1f is the correct address for the Hannstar LVDS I2C slave address.

If 0x1f is the Hannstar LVDS address, then you definitely should NOT use 
0x1f for the

CONFIG_SYS_I2C_SLAVE value.


CONFIG_SYS_I2C_SLAVE is meant to define which address the processor will respond to
in a multi-master bus environment. However, as mxc_i2c does not support slave mode
the entire discussion is moot.



Troy