From: Kevin Hilman <khilman-l0cyMroinI0@public.gmane.org>
To: NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org>
Cc: Tony Lindgren <tony-4v6yS6AI5VpBDgjK7y7TUQ@public.gmane.org>,
Ben Dooks <ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org>,
linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org,
Felipe Balbi <balbi-l0cyMroinI0@public.gmane.org>
Subject: Re: [PATCH] OMAP/I2C - Fix timeout problem during suspend.
Date: Wed, 04 Jan 2012 14:19:48 -0800 [thread overview]
Message-ID: <87boqjaz5n.fsf@ti.com> (raw)
In-Reply-To: <20111230124030.12c3d02c-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org> (NeilBrown's message of "Fri, 30 Dec 2011 12:40:30 +1100")
+Felipe
NeilBrown <neilb-l3A5Bk7waGM@public.gmane.org> writes:
> On a board with OMAP3 processor and TWL4030 Power management,
> we need to talk to the TWL4030 during late suspend but cannot
> because the I2C interrupt is disabled (as late suspend disables
> interrupt).
I'm not convinced this is the right solution to this problem.
IMO, this problem is caused by the MUSB driver being broken for
suspend/resume. I've reported this problem (and an RFC/PATCH)
already[1], but I don't think the driver has been fixed.
Can you try my patch[1] to see if it fixes your problem as well?
Kevin
[1] http://marc.info/?l=linux-omap&m=132252827112721&w=2
next prev parent reply other threads:[~2012-01-04 22:19 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2011-12-30 1:40 [PATCH] OMAP/I2C - Fix timeout problem during suspend NeilBrown
[not found] ` <20111230124030.12c3d02c-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2012-01-04 22:19 ` Kevin Hilman [this message]
[not found] ` <87boqjaz5n.fsf-l0cyMroinI0@public.gmane.org>
2012-01-05 7:10 ` NeilBrown
[not found] ` <20120105181026.24b8c0f4-wvvUuzkyo1EYVZTmpyfIwg@public.gmane.org>
2012-01-05 20:48 ` Kevin Hilman
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=87boqjaz5n.fsf@ti.com \
--to=khilman-l0cymroini0@public.gmane.org \
--cc=balbi-l0cyMroinI0@public.gmane.org \
--cc=ben-linux-elnMNo+KYs3YtjvyW6yDsg@public.gmane.org \
--cc=linux-i2c-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=linux-omap-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=neilb-l3A5Bk7waGM@public.gmane.org \
--cc=tony-4v6yS6AI5VpBDgjK7y7TUQ@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.