public inbox for linux-kernel@vger.kernel.org
 help / color / mirror / Atom feed
From: "Tanya Brokhman" <tlinder@codeaurora.org>
To: "'Alan Stern'" <stern@rowland.harvard.edu>
Cc: <gregkh@suse.de>, <linux-usb@vger.kernel.org>,
	<linux-arm-msm@vger.kernel.org>,
	"'David Brownell'" <dbrownell@users.sourceforge.net>,
	<linux-kernel@vger.kernel.org>
Subject: RE: [PATCH v6] usb: Adding SuperSpeed support to dummy_hcd
Date: Tue, 25 Jan 2011 15:14:31 +0200	[thread overview]
Message-ID: <000601cbbc91$cf9d8d80$6ed8a880$@org> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1011181045430.1801-100000@iolanthe.rowland.org>

> On Thu, 18 Nov 2010, Tatyana Brokhman wrote:
> 
> > USB 3.0 hub includes 2 hubs - HS and SS ones.
> > Thus, when dummy_hcd enabled it will register 2 root hubs (SS and
> HS).
> 
> Hmm.  A quick comparison with the original source shows that you
> neglected to add code for SuperSpeed transfers to periodic_bytes() and
> show_urb().

Added in the next patch that will be uploaded soon.

> 
> > @@ -1352,6 +1544,9 @@ static void dummy_timer (unsigned long _dum)
> >  	case USB_SPEED_HIGH:
> >  		total = 512/*bytes*/ * 13/*packets*/ * 8/*uframes*/;
> >  		break;
> > +	case USB_SPEED_SUPER:
> > +		total = 400 << 20; /* 400MB = 400*(2^20) bytes */
> > +		break;
> 
> Somehow I doubt that SuperSpeed USB, quick though it is, can transfer
> 400 MB in one millisecond.  Where did you get that number from?
> 

>From USB3.0 Spec section 4.4.11. My mistake was that this value (400 << 20)
is per sec and not per milisec. When we divide it by 1000 (milisec) we'll
receive a value close to what you suggested bellow. Fixed.

> I can't find the appropriate table in the USB-3.0 spec (it might not be
> there at all), but with a bus transfer rate of 500 million bytes/s it
> seems clear that you can't transfer more than 500000 bytes per frame.
> The actual limit must be lower than that, maybe something like 1024
> bytes/packet * 60 packets/uframe * 8 uframes/frame = 491520
> bytes/frame.
> 
> Alan Stern

Sorry for the poor quoting (this mail is a bit old) and the late response.
Our intention was to release the unittests we used to test this
implementation with the next patch version but releasing them got delayed
due to legal issues.

Best regards,
Tanya Brokhman
Consultant for Qualcomm Innovation Center, Inc.
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum






      reply	other threads:[~2011-01-25 13:14 UTC|newest]

Thread overview: 4+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2010-11-18 12:57 [PATCH v6] usb: Adding SuperSpeed support to dummy_hcd Tatyana Brokhman
2010-11-18 15:55 ` Greg KH
2010-11-18 16:06 ` Alan Stern
2011-01-25 13:14   ` Tanya Brokhman [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='000601cbbc91$cf9d8d80$6ed8a880$@org' \
    --to=tlinder@codeaurora.org \
    --cc=dbrownell@users.sourceforge.net \
    --cc=gregkh@suse.de \
    --cc=linux-arm-msm@vger.kernel.org \
    --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