From: Daniel Walker <danielwa@cisco.com>
To: linux-i2c@vger.kernel.org,
"xe-kernel@external.cisco.com" <xe-kernel@external.cisco.com>,
"Anil Veliyankara Madam (aveliyan)" <aveliyan@cisco.com>,
"Perry Li (chuangli)" <chuangli@cisco.com>
Subject: i2c device hangs the whole bus, recovery ?
Date: Thu, 14 Apr 2016 16:34:29 -0700 [thread overview]
Message-ID: <57102905.7080904@cisco.com> (raw)
Hi all,
We have a pca954x MUX and connected to this is some devices. We have one
device connected to the MUX which goes bad, and when we try to
communicate with the bad device (we don't know it's bad yet) , it causes
one of the i2c lines to go low and makes it impossible to connect with
any of the other devices on the bus.
I don't know how common this type of situation is, but I thought I would
ask here how people would recover from this condition ? Is there a
standard way to do it, or is the standard way to reboot the machine ?
I think ideally I would like to be able to detect that something is
wrong, and black list the device, and recover if possible.
Any suggestions appreciated,
Daniel
reply other threads:[~2016-04-14 23:44 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=57102905.7080904@cisco.com \
--to=danielwa@cisco.com \
--cc=aveliyan@cisco.com \
--cc=chuangli@cisco.com \
--cc=linux-i2c@vger.kernel.org \
--cc=xe-kernel@external.cisco.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).