From: Jean Delvare <khali-PUYAD+kWke1g9hUCZPvPmw@public.gmane.org>
To: 伊泽 <wxc200-Re5JQEeQqe8AvxtiuMwx3w@public.gmane.org>
Cc: Linux I2C <linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>
Subject: Re: pxa i2c unit busy caused unrecoverable phone hang problem
Date: Mon, 27 Apr 2009 12:08:10 +0200 [thread overview]
Message-ID: <20090427120810.20af38b8@hyperion.delvare> (raw)
In-Reply-To: <fd6b62c10904270057w610239dflfd228f949c0649b2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
On Mon, 27 Apr 2009 15:57:45 +0800, 伊泽 wrote:
> We use Marvell's pxaXXX chip,and the i2c unit often become BUSY status .As
> normal operation,the Unit-Busy will become free quickly,but sometimes
> UNIT-BUSY forever.For there are very frequent i2c operations,the cell-phone
> become hang soon,nothing could be done but remove the battery and reboot.
>
> So could you give a suggestion? Is there any useful way to protect from
> entering this abnormal UNIT-BUSY i2c status or recover from that?
I don't know anything about PXA platforms, there's nothing I can do for
you, sorry.
--
Jean Delvare
next parent reply other threads:[~2009-04-27 10:08 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <fd6b62c10904270057w610239dflfd228f949c0649b2@mail.gmail.com>
[not found] ` <fd6b62c10904270057w610239dflfd228f949c0649b2-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-27 10:08 ` Jean Delvare [this message]
[not found] ` <20090427120810.20af38b8-ig7AzVSIIG7kN2dkZ6Wm7A@public.gmane.org>
2009-04-27 10:33 ` pxa i2c unit busy caused unrecoverable phone hang problem Mike Rapoport
[not found] ` <fd6b62c10904270641p1dc6d86awc271dcc10a1f6b0@mail.gmail.com>
[not found] ` <fd6b62c10904270641p1dc6d86awc271dcc10a1f6b0-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-04-27 15:32 ` 伊泽
[not found] ` <fd6b62c10904270832w54c77fb3kdff9981d949ff54b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-05-03 22:33 ` Ben Dooks
[not found] ` <20090503223351.GC5750-elnMNo+KYs3pIgCt6eIbzw@public.gmane.org>
2009-05-04 3:16 ` 伊泽
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=20090427120810.20af38b8@hyperion.delvare \
--to=khali-puyad+kwke1g9huczpvpmw@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=wxc200-Re5JQEeQqe8AvxtiuMwx3w@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