linux-i2c.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Rajeev kumar <rajeev-dlh.kumar-qxv4g6HH51o@public.gmane.org>
To: Jason Hui <jason.hui-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org>
Cc: "ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org"
	<ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
	"khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org"
	<khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>,
	"linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
	<linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: About one i2c failure issue after system reset
Date: Mon, 21 Nov 2011 15:49:49 +0530	[thread overview]
Message-ID: <4ECA25C5.3010205@st.com> (raw)
In-Reply-To: <CAFQ4atSRapXvhBnm=nH__zz2U=XRjxN4GK-JsXT=AEcKybANZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>

Hello Jason

On 11/21/2011 1:05 PM, Jason Hui wrote:
> Hi, Ben, Jean,
>
> I have one issue about the i2c failure: there will be on-going i2c
> transfer while system get reset.
> At the time when the reset happens, the slave may pull the SDA to
> LOW.After reset, the i2c master may reset, but
> the slave may still pull the SDA to LOW since there is no reset pin
> for the slave device to do i2c reset, thus
> result in the further i2c access failure forever unless we completely
> power off the system by pulling out
> the battery.
>
This is not the only solution for this. Master can accomplishes error 
recovery by clocking Clock until Data is high and then issuing a Start 
followed by a Stop.

Best Regards
Rajeev
...

> I know we have the shutdown member function, but as I know there is
> very less i2c master has implemented this
> function correctly. I think we need take seriously about this issue,
> do you have any comments? Thanks,
>
>
> Jason Liu
> --
> To unsubscribe from this list: send the line "unsubscribe linux-i2c" in
> the body of a message to majordomo-u79uwXL29TY76Z2rM5mHXA@public.gmane.org
> More majordomo info at  http://vger.kernel.org/majordomo-info.html
>

  parent reply	other threads:[~2011-11-21 10:19 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2011-11-21  7:35 About one i2c failure issue after system reset Jason Hui
     [not found] ` <CAFQ4atSRapXvhBnm=nH__zz2U=XRjxN4GK-JsXT=AEcKybANZA-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2011-11-21 10:19   ` Rajeev kumar [this message]
2011-11-21 11:49   ` Michael Lawnick

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=4ECA25C5.3010205@st.com \
    --to=rajeev-dlh.kumar-qxv4g6hh51o@public.gmane.org \
    --cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
    --cc=jason.hui-QSEj5FYQhm4dnm+yROfE0A@public.gmane.org \
    --cc=khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org \
    --cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@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 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).