From mboxrd@z Thu Jan  1 00:00:00 1970
From: Stefan Roese <sr@denx.de>
Date: Mon, 14 Mar 2016 13:30:54 +0100
Subject: [U-Boot] BayTrail I2C support
In-Reply-To: <CAEUhbmXb1JLXTMw_oHX=-OevHAHPa0UPE5m8JKh5TO_L_NUq2Q@mail.gmail.com>
References: <56E30186.1000607@denx.de>
 <CAPnjgZ2QWYyVmF7jng=6xoW5jQM7XuWEnXkKLSrWs-3UOvPHCQ@mail.gmail.com>
 <CAEUhbmXb1JLXTMw_oHX=-OevHAHPa0UPE5m8JKh5TO_L_NUq2Q@mail.gmail.com>
Message-ID: <56E6AEFE.8030503@denx.de>
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

Hi Bin,

On 14.03.2016 09:56, Bin Meng wrote:
> On Sun, Mar 13, 2016 at 10:52 AM, Simon Glass <sjg@chromium.org> wrote:
>> Hi Stefan,
>>
>> On 11 March 2016 at 10:33, Stefan Roese <sr@denx.de> wrote:
>>> Hi Simon, Hi Bin,
>>>
>>> could you please let me know, what the status of I2C support for
>>> BayTrail in U-Boot is? Is this driver generic enough to handle
>>> BayTrail / Minnowboard MAX as well (I haven't looked in depth yet)?
>>> Or what needs to be done to get BayTrail supported here?
>>
>> There is a dummy driver but it does not work. It needs to be filled
>> out with an implementation using the datasheet or perhaps looking at
>> coreboot smbus code.
>>
>
> I guess Stefan is not looking for legacy SMBUS support, instead the
> SIO I2C device on device 24 on BayTrail.

I need to communicate with some of I2C devices connected to some
of the I2C busses (e.g. bus #1) on this platform.

> It is currently not
> supported. The IP used on BayTrail is from Synopsis Designware, and
> this I2C IP is also seen on Intel Quark.

Is it documented somewhere, that these BayTrail I2C controllers
are Synopsis Designware based / compatible? Could you please point
me to this datasheet?

> It is possible we can reuse
> U-Boot Synopsis I2C driver on Intel platform, with adaptations to PCI.

I can definitely look into this. Thanks for letting me know.

Thanks,
Stefan