public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Robert de Rooy <robert.de.rooy@gmail.com>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: Jiri Kosina <jikos@jikos.cz>, Greg KH <greg@kroah.com>,
	Joel.Becker@oracle.com,
	USB development list <linux-usb-devel@lists.sourceforge.net>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: [linux-usb-devel] ThinkPad T41 - Strange USB 2.0 behaviour
Date: Tue, 12 Jun 2007 00:42:28 +0200	[thread overview]
Message-ID: <466DCFD4.9080702@gmail.com> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0706101129070.29131-100000@netrider.rowland.org>

Alan Stern wrote:
> Okay.  It's clear that you've got a hardware problem of some sort.  
> Hard to say what it is, but evidently the EHCI controller thinks that 
> the device is repeatedly being unplugged and replugged.
>
> Anyway, this isn't a problem of recognizing that a single device is
> having problems.  In fact the computer has no way of knowing that a
> single device is involved; all it knows is that _something_ gets
> plugged into the port and then removed.  There's no way to tell if it's 
> the same _something_ from one iteration to the next.
>
> You can manually force the port to run at full speed instead of high 
> speed as follows:
>
> 	echo '4' >/sys/class/usb_host/usb_host4/companion
>
> The "companion" attribute file contains a list of ports which are 
> permanently set to be handled by the EHCI's companion controller.  To 
> return to high-speed operation, use '-4' instead of '4' above.  This 
> might or might not solve your problem -- the hardware bug might cause 
> the port to return automatically to high-speed regardless.
>
> Let me know what happens.
>
> Alan Stern

Yes that works.
I tried to plug and unplug the device repeatedly and each time it came 
up in full-speed mode.


  reply	other threads:[~2007-06-11 20:43 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2007-06-07 20:23 ThinkPad T41 - Strange USB 2.0 behaviour Robert de Rooy
2007-06-07 20:50 ` Joel Becker
2007-06-07 21:42   ` Robert de Rooy
2007-06-07 21:58     ` Joel Becker
2007-06-08  9:12     ` Jiri Kosina
2007-06-08 10:09       ` Robert de Rooy
2007-06-08 10:17         ` Jiri Kosina
2007-06-08 14:27           ` [linux-usb-devel] " Alan Stern
2007-06-08 22:19             ` Robert de Rooy
2007-06-09 21:20               ` Alan Stern
2007-06-09 23:43                 ` Robert de Rooy
2007-06-10 15:43                   ` Alan Stern
2007-06-11 22:42                     ` Robert de Rooy [this message]
2007-06-11 21:23                       ` Alan Stern
2007-06-12  5:57                         ` Robert de Rooy
2007-06-12 14:54                           ` 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=466DCFD4.9080702@gmail.com \
    --to=robert.de.rooy@gmail.com \
    --cc=Joel.Becker@oracle.com \
    --cc=greg@kroah.com \
    --cc=jikos@jikos.cz \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb-devel@lists.sourceforge.net \
    --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