From: Stefan Roese <sr@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] BayTrail I2C support
Date: Mon, 14 Mar 2016 13:30:54 +0100 [thread overview]
Message-ID: <56E6AEFE.8030503@denx.de> (raw)
In-Reply-To: <CAEUhbmXb1JLXTMw_oHX=-OevHAHPa0UPE5m8JKh5TO_L_NUq2Q@mail.gmail.com>
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
next prev parent reply other threads:[~2016-03-14 12:30 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-03-11 17:33 [U-Boot] BayTrail I2C support Stefan Roese
2016-03-13 2:52 ` Simon Glass
2016-03-14 8:56 ` Bin Meng
2016-03-14 12:30 ` Stefan Roese [this message]
2016-03-15 1:52 ` Bin Meng
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=56E6AEFE.8030503@denx.de \
--to=sr@denx.de \
--cc=u-boot@lists.denx.de \
/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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.