From: Robert Baldyga <r.baldyga@samsung.com>
To: dinh.linux@gmail.com
Cc: "paulz@synopsys.com >> Paul Zimmerman" <paulz@synopsys.com>,
"balbi@ti.com" <balbi@ti.com>,
gregkh@linuxfoundation.org,
Marek Szyprowski <m.szyprowski@samsung.com>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>
Subject: usb: dwc2: problems with IN requests completion in linux-next
Date: Mon, 22 Dec 2014 15:13:08 +0100 [thread overview]
Message-ID: <549826F4.6080709@samsung.com> (raw)
Hi,
I have recently noticed problem with DWC2 driver in latest linux-next. I
use it in gadget only mode at Samsung platform (Odroid U3) but I believe
the bug can be reproduced at another platforms.
While running FFS example (tools/usb/ffs-aio-example/simple/) the
communication breaks after few seconds. It's because one of IN requests
enqueued in DWC2 driver do not complete. At USB analyzer I see that USB
device started to transmit data from this request, but it ended incomplete.
I bisected kernel tree, and I got following patches are reason of break.
941fcce usb: dwc2: Update the gadget driver to use common dwc2_hsotg
structure
117777b usb: dwc2: Move gadget probe function into platform code
bcc0607 usb: dwc2: convert to use dev_pm_ops API
510ffaa usb: dwc2: Initialize the USB core for peripheral mode
db8178c usb: dwc2: Update common interrupt handler to call gadget
interrupt handler
8d736d8 usb: dwc2: gadget: Do not fail probe if there isn't a clock node
Patch 941fcce breaks DWC2 driver at my platform and it starts to work
from 8d736d8 but it has described bug.
I will try to localize reason of this issue.
Best regards,
Robert Baldyga
next reply other threads:[~2014-12-22 14:13 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-12-22 14:13 Robert Baldyga [this message]
2015-01-12 21:35 ` Paul Zimmerman
2015-01-13 10:18 ` Robert Baldyga
2015-01-13 10:50 ` Robert Baldyga
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=549826F4.6080709@samsung.com \
--to=r.baldyga@samsung.com \
--cc=balbi@ti.com \
--cc=dinh.linux@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=paulz@synopsys.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox
Powered by JetHome