From: Heiko Schocher <hs@denx.de>
To: u-boot@lists.denx.de
Subject: [U-Boot] [PATCH] i2c: intel_i2c: SMBus driver PCI addition (e.g. BayTrail)
Date: Fri, 5 Aug 2016 09:10:56 +0200 [thread overview]
Message-ID: <57A43C00.4020406@denx.de> (raw)
In-Reply-To: <CAEUhbmWUmGdDWyOYUiyiDk8xXqLOHMmQ5vtdgi3ujZ495BP9OQ@mail.gmail.com>
Hello Bin,
Am 05.08.2016 um 07:46 schrieb Bin Meng:
> Simon, Stefan,
>
> On Tue, Jul 26, 2016 at 8:13 PM, Stefan Roese <sr@denx.de> wrote:
>> Hi Simon,
>>
>> On 25.07.2016 04:07, Simon Glass wrote:
>>>
>>> On 28 June 2016 at 07:44, Stefan Roese <sr@denx.de> wrote:
>>>>
>>>> This patch adds support for the SMBus block read/write functionality.
>>>> Other protocols like the SMBus quick command need to get added
>>>> if this is needed.
>>>>
>>>> This patch also removed the SMBus related defines from the Ivybridge
>>>> pch.h header. As they are integrated in this driver and should be
>>>> used from here. This change is added in this patch to avoid compile
>>>> breakage to keep the source git bisectable.
>>>>
>>>> Tested on a congatec BayTrail board to configure the SMSC2513 USB
>>>> hub.
>>>>
>>>> Signed-off-by: Stefan Roese <sr@denx.de>
>>>> Cc: Bin Meng <bmeng.cn@gmail.com>
>>>> Cc: Simon Glass <sjg@chromium.org>
>>>> Cc: Heiko Schocher <hs@denx.de>
>>>> ---
>>>> Simon, I'm not sure if this change breaks your Ivybridge targets
>>>> using the probe part of this driver. Could you please let me
>>>> know if this works? Or let me know what needs changes here?
>>>
>>>
>>> Yes this breaks booting on link. Something odd is going on because the
>>> call to set up I2C in ivybridge's print_cpuinfo() returns a very
>>> strange error -726376.
>>
>>
>> Hmmm, very strange.
>>
>>> But I then enabled CONFIG_CMD_I2C and it boots. However 'i2c probe'
>>> produces a lot of errors like this:
>>>
>>> ERROR: len=0 on read
>>> smbus_block_read (107): dev=0x3b offs=0x0 len=0x1
>>> smbus_block_read (136): count=0 (len=1)
>>
>>
>> A general question:
>>
>> Is the SMBus controller on Ivybridge also exported as PCI device? If
>> yes, can't we just use the PCI code as done for BayTrail for this
>> platform as well? And get rid of the platform specific stuff this
>> way?
>>
>> Could you send me the output of "pci 0 long" on this platform?
>>
>
> Do you plan to get this I2C merged in this release? If so, please work
> this out .. I don't feel comfortable to apply this at present.
Full Ack.
bye,
Heiko
--
DENX Software Engineering GmbH, Managing Director: Wolfgang Denk
HRB 165235 Munich, Office: Kirchenstr.5, D-82194 Groebenzell, Germany
next prev parent reply other threads:[~2016-08-05 7:10 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-06-28 13:44 [U-Boot] [PATCH] i2c: intel_i2c: SMBus driver PCI addition (e.g. BayTrail) Stefan Roese
2016-07-12 5:22 ` Bin Meng
2016-07-19 4:39 ` Bin Meng
2016-07-25 2:07 ` Simon Glass
2016-07-25 11:34 ` Stefan Roese
2016-07-26 12:13 ` Stefan Roese
2016-08-05 5:46 ` Bin Meng
2016-08-05 7:10 ` Heiko Schocher [this message]
2016-08-05 7:18 ` Stefan Roese
2016-08-06 3:36 ` Simon Glass
2016-08-07 9:13 ` Stefan Roese
2016-08-05 16:09 ` George McCollister
2016-08-09 5:32 ` Stefan Roese
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=57A43C00.4020406@denx.de \
--to=hs@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.