From: Jae Hyun Yoo <jae.hyun.yoo@linux.intel.com>
To: Tao Ren <taoren@fb.com>, OpenBMC Maillist <openbmc@lists.ozlabs.org>
Subject: Re: AST2500 I2C Controller got stuck in SRXD state
Date: Tue, 3 Sep 2019 14:51:07 -0700 [thread overview]
Message-ID: <fc49fd92-856a-456e-6be3-2ddcee16aa82@linux.intel.com> (raw)
In-Reply-To: <7af0671b-524c-02a7-fc6c-60360b06f0db@fb.com>
On 9/3/2019 2:45 PM, Tao Ren wrote:
> Hi,
>
> I found the issue on Minipack (AST2500) BMC i2c-0: it's multi-master environment with BMC and Bridged-IC.
>
> The BMC I2C controller got stuck in SLAVE_RX_DONE state because STOP condition is not detected during one BIC-to-BMC transfer.
> Because of this, all the subsequent I2C master transactions would fail with timeout.
> Here is BMC I2C state reported in I2CD14 Command/Status register:
>
> - I2CD14[22:19] = 0100b /* transfer state machine: SLAVE_RX_DONE */
> - I2CD14[18] = 1 /* sampled SCL line: high/idle */
> - I2CD14[17] = 1 /* sampled SDA line: high/idle */
> - I2CD14[16] = 0 /* bus is idle */
>
> I'm suspecting it's caused by some flaws in BIC firmware, but can we do something in BMC side to recover the bus?
> For example:
>
> 1) As Jae mentioned earlier, enable slave inactive timeout interrupt and reset bus when the interrupt is delivered?
>
> 2) Check I2CD14[22:19] in aspeed_i2c_recover_bus() function and reset bus if needed?
>
Hi Tao,
I made the slave inactive timeout support. Will submit it soon.
Cheers,
Jae
>
> Thanks,
>
> Tao
>
next prev parent reply other threads:[~2019-09-03 21:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-09-03 21:45 AST2500 I2C Controller got stuck in SRXD state Tao Ren
2019-09-03 21:51 ` Jae Hyun Yoo [this message]
2019-09-03 21:52 ` Tao Ren
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=fc49fd92-856a-456e-6be3-2ddcee16aa82@linux.intel.com \
--to=jae.hyun.yoo@linux.intel.com \
--cc=openbmc@lists.ozlabs.org \
--cc=taoren@fb.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 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.