public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: Simon Arlott <simon@fire.lp0.eu>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: USB list <linux-usb@vger.kernel.org>,
	Kernel development list <linux-kernel@vger.kernel.org>
Subject: Re: cxacru usb_bulk_msg() firmware upload 36x slower with OHCI vs. UHCI
Date: Mon, 30 Aug 2010 22:49:52 +0100	[thread overview]
Message-ID: <4C7C2780.8040003@simon.arlott.org.uk> (raw)
In-Reply-To: <Pine.LNX.4.44L0.0911221714160.31173-100000@netrider.rowland.org>

On 22/11/09 22:17, Alan Stern wrote:
> On Sun, 22 Nov 2009, Simon Arlott wrote:
>> I've tried sending 64 and 2048 bytes at a time, with the same speed
>> (4ms and 128ms), so that time is just a coincidence.
> 
> These timings indicate that one packet is getting transmitted every 4 
> frames.  In theory the slowness could be caused by either the host 
> controller or the device, but you'd need a bus analyzer to tell which.  
> Certainly there's no good reason for the controller to run that slowly, 
> but there's also no good reason for the device to run that slowly only 
> with OHCI.
> 
>> Submitting it all as multiple asynchronous URBs in one go doesn't help
>> either. I've been trying to get EHCI working too (via two different
>> high speed hubs) but that's not working even if I add long delays.
> 
> Have you tried using a non-high-speed hub, or forcing the port into 
> full speed and adding a hub?  That is, does the presence of a hub with 
> OHCI make any difference?

Something has changed in the kernel between the last time I looked at
this issue and now. On both my OHCI hardware the firmware initialisation
runs at the same speed as UHCI did. It's even working via a hub on EHCI.

This may have something to do with cxacru trying to use an interrupt
transfer for a bulk endpoint, which now returns an error if
CONFIG_USB_DEBUG is enabled...

Commit f661c6f8c67bd55e93348f160d590ff9edf08904 is in urgent need of a
printk(); a patch follows this email.

-- 
Simon Arlott

      reply	other threads:[~2010-08-30 21:56 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-11-18 12:58 cxacru usb_bulk_msg() firmware upload 36x slower with OHCI vs. UHCI Simon Arlott
2009-11-18 15:51 ` Alan Stern
2009-11-18 20:02   ` Simon Arlott
2009-11-18 21:28     ` Alan Stern
2009-11-18 21:59       ` Simon Arlott
2009-11-18 22:25         ` Alan Stern
2009-11-22 10:58           ` Simon Arlott
2009-11-22 16:14             ` Alan Stern
2009-11-22 17:16               ` Simon Arlott
2009-11-22 22:17                 ` Alan Stern
2010-08-30 21:49                   ` Simon Arlott [this message]

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=4C7C2780.8040003@simon.arlott.org.uk \
    --to=simon@fire.lp0.eu \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --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