From: robert.jarzmik@free.fr (Robert Jarzmik)
To: linux-arm-kernel@lists.infradead.org
Subject: pxa27x_udc: Oops on probe with usb cable connected.
Date: Sun, 04 Jul 2010 01:48:57 +0200 [thread overview]
Message-ID: <87r5jkxh1y.fsf@free.fr> (raw)
In-Reply-To: <20100703221022.27df1a2e.ospite@studenti.unina.it> (Antonio Ospite's message of "Sat\, 3 Jul 2010 22\:10\:22 +0200")
Antonio Ospite <ospite@studenti.unina.it> writes:
> Done that as well this time. See
> http://people.openezx.org/ao2/tmp/pxa27x-udc_BUG/
> I replaced the old files with the new ones as per your instructions.
>
> Thanks,
> Antonio
Nice.
Now, would you test the patch attached in this mail to see if :
- it fixes your Oops
- the UDC is usable after you attach a gadget driver to pxa27x_udc
Cheers.
--
Robert
---
diff --git a/drivers/usb/gadget/pxa27x_udc.c b/drivers/usb/gadget/pxa27x_udc.c
index 85b0d89..d76d9ee 100644
--- a/drivers/usb/gadget/pxa27x_udc.c
+++ b/drivers/usb/gadget/pxa27x_udc.c
@@ -1938,6 +1938,9 @@ static void handle_ep0_ctrl_req(struct pxa_udc *udc,
nuke(ep, -EPROTO);
spin_lock_irqsave(&ep->lock, flags);
+ if (!udc->driver)
+ goto stall;
+
/*
* In the PXA320 manual, in the section about Back-to-Back setup
* packets, it describes this situation. The solution is to set OPC to
-------------- next part --------------
An embedded and charset-unspecified text was scrubbed...
Name: patch.txt
URL: <http://lists.infradead.org/pipermail/linux-arm-kernel/attachments/20100704/0c0b80fc/attachment.txt>
next prev parent reply other threads:[~2010-07-03 23:48 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-06-30 9:53 pxa27x_udc: Oops on probe with usb cable connected Antonio Ospite
2010-07-02 18:17 ` Robert Jarzmik
2010-07-03 20:10 ` Antonio Ospite
2010-07-03 23:48 ` Robert Jarzmik [this message]
2010-07-05 8:40 ` Antonio Ospite
2010-07-06 22:34 ` Robert Jarzmik
2010-07-06 22:56 ` Antonio Ospite
2010-07-11 8:13 ` Robert Jarzmik
2010-07-22 15:14 ` Antonio Ospite
2010-07-23 11:18 ` Antonio Ospite
2010-07-23 19:07 ` Robert Jarzmik
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=87r5jkxh1y.fsf@free.fr \
--to=robert.jarzmik@free.fr \
--cc=linux-arm-kernel@lists.infradead.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;
as well as URLs for NNTP newsgroup(s).