From: Felipe Balbi <me@felipebalbi.com>
To: Tony Lindgren <tony@atomide.com>
Cc: Kim Kyuwon <chammoru@gmail.com>,
linux-omap@vger.kernel.org, ????????? <kyungmin.park@samsung.com>,
????????? <q1.kim@samsung.com>
Subject: Re: [PATCH] ARM: OMAP: Disable USB interrupt in the musb_resume() function
Date: Wed, 4 Feb 2009 00:28:42 +0200 [thread overview]
Message-ID: <20090203222842.GB6214@frodo> (raw)
In-Reply-To: <20090203204235.GH7215@atomide.com>
On Tue, Feb 03, 2009 at 12:42:36PM -0800, Tony Lindgren wrote:
> * Kim Kyuwon <chammoru@gmail.com> [090131 00:22]:
> > USB should be suspended with interrupt disabled[1]. If USB is suspended with
> > interrupt enabled and connected to host PC, a kernel panic would occur When
> > it wakes up. Because, after the arch_suspend_enable_irqs() function is called
> > in the suspend_enter() function, USB Interrupt handler is called, even though
> > USB controller is still not resumed! All devices are resumed after the
> > device_resume() is called.
>
> Please send the usb patches to the linux-usb@vger.kernel.org list
> with linux-omap list Cc'd.
and Cc me as well and David Brownell
--
balbi
next prev parent reply other threads:[~2009-02-03 22:28 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2009-01-31 8:21 [PATCH] ARM: OMAP: Disable USB interrupt in the musb_resume() function Kim Kyuwon
2009-02-03 20:42 ` Tony Lindgren
2009-02-03 22:28 ` Felipe Balbi [this message]
2009-02-03 23:33 ` Kim Kyuwon
[not found] ` <4d34a0a70901310021l6f42b34es24ca320e44c51ae6-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-04 0:01 ` Kim Kyuwon
[not found] ` <4d34a0a70902031601r5c8c3424l4cd399193142e612-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-21 2:30 ` David Brownell
2009-02-23 3:28 ` Kim Kyuwon
[not found] ` <4d34a0a70902221928y2724f776j4f4558306b01e6ff-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2009-02-23 5:50 ` David Brownell
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=20090203222842.GB6214@frodo \
--to=me@felipebalbi.com \
--cc=chammoru@gmail.com \
--cc=kyungmin.park@samsung.com \
--cc=linux-omap@vger.kernel.org \
--cc=q1.kim@samsung.com \
--cc=tony@atomide.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 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.