linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Stefan Roese <sr@denx.de>
To: Jean Delvare <jdelvare@suse.com>
Cc: linux-i2c@vger.kernel.org,
	Mika Westerberg <mika.westerberg@linux.intel.com>,
	Jarkko Nikula <jarkko.nikula@linux.intel.com>,
	"Chew, Kean ho" <kean.ho.chew@intel.com>
Subject: Re: i2c-i801 / SMBus timeouts on BayTrail board (U-Boot)
Date: Fri, 24 Jun 2016 16:33:42 +0200	[thread overview]
Message-ID: <576D44C6.4030702@denx.de> (raw)
In-Reply-To: <1466775522.8139.3.camel@chaos.suse>

Hi Jean,

On 24.06.2016 15:38, Jean Delvare wrote:
> On ven., 2016-06-24 at 13:57 +0200, Stefan Roese wrote:
>> Hi,
>>
>> I'm currently trying to use the SMBus on a congatec BayTrail board.
>> This works just fine when booting via the original BIOS. But when I
>> boot into Linux using U-Boot as bootloader, I get the following
>> errors:
>>
>> [   81.877121] i801_smbus 0000:00:1f.3: Transaction timeout
>> [   81.879228] i801_smbus 0000:00:1f.3: Failed terminating the transaction
>> [   81.879320] i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
>> [   81.879373] i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
>> [   81.879421] i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
>> [   81.879496] i801_smbus 0000:00:1f.3: SMBus is busy, can't use it!
>> ...
>>
>> I checked with an oscilloscope and the SMBus clock is not toggling
>> at all in this case. My feeling is, that some basic setup is missing
>> in this non-BIOS case. Like some clock enabling. Does anyone of you
>> have some idea here?
>
> No immediate idea, sorry. Two ideas:
>
> * Is this problem specific to Baytrail systems, or does i2c-i801 fail on
> all U-Boot systems?

I only have BayTrail systems right now.

> * Did you try comparing the PCI configuration space of the SMBus device
> between original BIOS boot (working) and U-Boot boot (not working)?

The issue seems to be solved just a few minutes ago. As it seems
a pin-mux configuration was missing for the SMBus pins. Now the bus
can be scanned in Linux without any issues.

Thanks,
Stefan

      reply	other threads:[~2016-06-24 14:33 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2016-06-24 11:57 i2c-i801 / SMBus timeouts on BayTrail board (U-Boot) Stefan Roese
2016-06-24 13:38 ` Jean Delvare
2016-06-24 14:33   ` Stefan Roese [this message]

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=576D44C6.4030702@denx.de \
    --to=sr@denx.de \
    --cc=jarkko.nikula@linux.intel.com \
    --cc=jdelvare@suse.com \
    --cc=kean.ho.chew@intel.com \
    --cc=linux-i2c@vger.kernel.org \
    --cc=mika.westerberg@linux.intel.com \
    /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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).