From: Stefani Seibold <stefani@seibold.net>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: linux-usb <linux-usb@vger.kernel.org>,
linux-kernel@vger.kernel.org, Greg KH <greg@kroah.com>,
sarah.a.sharp@linux.intel.com, andreas.brief@rohde-schwarz.com
Subject: Re: Missing USB XHCI and EHCI reset for kexec
Date: Tue, 15 Apr 2014 21:08:12 +0200 [thread overview]
Message-ID: <1397588892.21892.6.camel@vger.seibold.net> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1404151502160.1310-100000@iolanthe.rowland.org>
Am Dienstag, den 15.04.2014, 15:05 -0400 schrieb Alan Stern:
> On Tue, 15 Apr 2014, Stefani Seibold wrote:
>
> > > One other thing you can try is to increase the reset timeout in
> > > drivers/usb/host/ehci-hub.c. This is under the USB_PORT_FEAT_RESET
> > > case in ehci_hub_control(), around line 1225:
> > >
> > > /*
> > > * caller must wait, then call GetPortStatus
> > > * usb 2.0 spec says 50 ms resets on root
> > > */
> > > ehci->reset_done [wIndex] = jiffies
> > > + msecs_to_jiffies (50);
> > >
> > > Increasing the 50 to 100 or more might help.
> > >
> > > Alan Stern
> > >
> >
> > I tried this, when i increase the value to 1000, the reset and
> > enumeration process will be faster after a kexec: 28 Seconds vs. 162
> > Seconds.
>
> Even 28 seconds is much longer than it should be. And a 1000-ms long
> reset signal is a lot longer than any device should need.
>
> Anyway, since you saw the same problem after unbind and rebind, you
> don't have to perform a kexec for testing.
>
Right, but i would prefer a solution for this. Since it works perfectly
in kernel 3.4 i don't think it is a hardware issue.
- Stefani
next prev parent reply other threads:[~2014-04-15 19:09 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-04-13 19:22 Stefani Seibold
2014-04-14 2:14 ` Alan Stern
2014-04-14 13:54 ` stefani
2014-04-14 14:49 ` Alan Stern
2014-04-14 15:25 ` stefani
2014-04-14 16:27 ` Alan Stern
2014-04-14 16:35 ` Stefani Seibold
2014-04-14 17:58 ` Alan Stern
2014-04-15 18:32 ` Stefani Seibold
2014-04-15 19:05 ` Alan Stern
2014-04-15 19:08 ` Stefani Seibold [this message]
2014-04-15 18:30 ` Stefani Seibold
2014-04-15 19:02 ` Alan Stern
2014-04-15 19:06 ` Stefani Seibold
2014-04-15 19:14 ` Alan Stern
2014-04-15 19:17 ` Stefani Seibold
2014-04-15 19:14 ` Stefani Seibold
2014-04-15 19:34 ` Alan Stern
2014-04-14 9:42 ` Benjamin Herrenschmidt
2014-04-14 15:44 ` stefani
2014-04-14 21:48 ` Thadeu Lima de Souza Cascardo
2014-04-15 10:04 ` stefani
2014-04-15 12:20 ` Thadeu Lima de Souza Cascardo
2014-04-15 15:00 ` stefani
2014-04-15 18:33 ` Thadeu Lima de Souza Cascardo
2014-04-15 18:42 ` Stefani Seibold
2014-04-15 18:49 ` Thadeu Lima de Souza Cascardo
2014-04-15 18:54 ` Stefani Seibold
2014-06-07 8:15 ` Benjamin Herrenschmidt
2014-06-07 15:40 ` Alan Stern
2014-06-07 21:11 ` Benjamin Herrenschmidt
2014-06-07 22:35 ` Benjamin Herrenschmidt
2014-06-08 1:09 ` Alan Stern
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=1397588892.21892.6.camel@vger.seibold.net \
--to=stefani@seibold.net \
--cc=andreas.brief@rohde-schwarz.com \
--cc=greg@kroah.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=sarah.a.sharp@linux.intel.com \
--cc=stern@rowland.harvard.edu \
/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
all inboxes | Powered by JetHome®