All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kefeng Wang <wangkefeng.wang-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
To: linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
Cc: Wolfram Sang <wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org>,
	Alexey Brodkin <abrodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org>,
	Ding Tianhong
	<dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>,
	"Guohanjun (Hanjun Guo)"
	<guohanjun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
Subject: question about i2c-designware
Date: Thu, 9 Jul 2015 16:59:03 +0800	[thread overview]
Message-ID: <559E37D7.6040103@huawei.com> (raw)

Hi all,

  We met a issue when use Synopsys DesignWare I2C. The SDA will keep low level and never go back to the high level
if both i2c controllers simultaneously access the same i2c device(rtc), then both two i2c controllers can't send any data.
we try to reset the rtc, but not working. After reset the i2c controller, the SDA goes back to the high state and we
can get time from rtc again.

The scenario is as follows, any advice will be appreciated.

                   OS 1            |     OS 2
                                  |
	+--------------+----------|--------------+
	|	       |	  |              |
	|    +---------|----+-----|---------+    |
	|    |	       |    |     |         |    |
   ----------------    ------	  |    -----------------
   |i2c controller1|   | rtc|	  |    |i2c controller2|
   ----------------    ------     |    -----------------
                                  |
note:
1) i2c controller1 and controller2 use same IP.
2) OS1 use v3.19 and OS2 use 2.6

Thanks
Kefeng

             reply	other threads:[~2015-07-09  8:59 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-07-09  8:59 Kefeng Wang [this message]
     [not found] ` <559E37D7.6040103-hv44wF8Li93QT0dZR+AlfA@public.gmane.org>
2015-07-10  4:11   ` question about i2c-designware Kefeng Wang
2015-07-10  4:11     ` Kefeng Wang

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=559E37D7.6040103@huawei.com \
    --to=wangkefeng.wang-hv44wf8li93qt0dzr+alfa@public.gmane.org \
    --cc=abrodkin-HKixBCOQz3hWk0Htik3J/w@public.gmane.org \
    --cc=dingtianhong-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=guohanjun-hv44wF8Li93QT0dZR+AlfA@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
    --cc=wsa-z923LK4zBo2bacvFa/9K2g@public.gmane.org \
    /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.