From: Stephen Warren <swarren-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
To: Marc Dietrich <marvin24-Mmb7MZpHnFY@public.gmane.org>
Cc: "linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org"
<linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org>,
Venu Byravarasu
<vbyravarasu-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
Subject: Re: unhandled interrupt from otg port
Date: Tue, 19 Feb 2013 10:03:47 -0700 [thread overview]
Message-ID: <5123B073.7060005@wwwdotorg.org> (raw)
In-Reply-To: <1978166.seipGZS4QH@ax5200p>
On 02/17/2013 04:48 AM, Marc Dietrich wrote:
> Hi,
>
> I sometimes see unhandled irq from the otg port on my AC100 (kernel 3.8.0-rc7).
> This happens randomly when the a cable is pluged into the mini usb port. Seems
> the port generates an interrupt on probe which isn't handled.
Perhaps Venu can explain this; he is our USB expert.
> Any ideas?
I'm slightly confused by your description though; I assume this problem
happens when you boot with a USB cable already plugged in, not when you
first boot the system, then plug in a cable? Is the cable connected to a
host PC, or to a device?
next prev parent reply other threads:[~2013-02-19 17:03 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2013-02-17 11:48 unhandled interrupt from otg port Marc Dietrich
2013-02-19 17:03 ` Stephen Warren [this message]
[not found] ` <5123B073.7060005-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-19 22:12 ` Marc Dietrich
2013-02-19 22:17 ` Marc Dietrich
2013-02-19 22:24 ` Stephen Warren
[not found] ` <5123FBAC.6010302-3lzwWm7+Weoh9ZMKESR00Q@public.gmane.org>
2013-02-20 8:50 ` Marc Dietrich
[not found] ` <2407399.sDvuQ1S2GC-D3pzGp0ZKuDWZbiwp4sFPyrtisivX6KghOMvlBiLbJSELgA04lAiVw@public.gmane.org>
2013-02-20 8:59 ` Venu Byravarasu
2013-02-28 6:47 ` Venu Byravarasu
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=5123B073.7060005@wwwdotorg.org \
--to=swarren-3lzwwm7+weoh9zmkesr00q@public.gmane.org \
--cc=linux-tegra-u79uwXL29TY76Z2rM5mHXA@public.gmane.org \
--cc=marvin24-Mmb7MZpHnFY@public.gmane.org \
--cc=vbyravarasu-DDmLM1+adcrQT0dZR+AlfA@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.