From: Felipe Balbi <balbi@ti.com>
To: Paul Zimmerman <Paul.Zimmerman@synopsys.com>
Cc: "balbi@ti.com" <balbi@ti.com>,
Jorge Ramirez-Ortiz <jorge.ramirez-ortiz@linaro.org>,
Greg KH <gregkh@linuxfoundation.org>,
"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
"linux-usb@vger.kernel.org" <linux-usb@vger.kernel.org>
Subject: Re: [PATCH] usb: gadget: USB3 support to the legacy printer driver
Date: Tue, 18 Nov 2014 21:10:49 -0600 [thread overview]
Message-ID: <20141119031049.GB24874@saruman> (raw)
In-Reply-To: <A2CA0424C0A6F04399FB9E1CD98E0304844EDA05@US01WEMBX2.internal.synopsys.com>
[-- Attachment #1: Type: text/plain, Size: 1105 bytes --]
On Tue, Nov 18, 2014 at 09:45:13PM +0000, Paul Zimmerman wrote:
> > From: linux-usb-owner@vger.kernel.org [mailto:linux-usb-owner@vger.kernel.org] On Behalf Of Felipe Balbi
> > Sent: Tuesday, November 18, 2014 12:47 PM
> >
> > On Tue, Nov 18, 2014 at 03:41:43PM -0500, Jorge Ramirez-Ortiz wrote:
> > >
> > > notice that the original PLX driver was still far from the theoretical 5Gbps
> > > target (I was expecting to measure at least 3Gbps and could only get 1Gbps).
> > > So 1Gbps should be the target to meet on the kernel.org net2280 - do you agree?
> >
> > this depends on a whole bunch of things. Mainline is a lot different
> > from PLX's kernel tree, I'm sure.
> >
> > It also depends on how many PCIe lanes you're using. Just because USB3
> > guarantees 5Gbps bandwidth, if you use a 1x PCIe connector, you'll never
> > get that ;-)
>
> Being pedantic, USB3 runs at 4Gbps, not 5Gbps. The signal transitions
> on the bus are at 5GT/s (5 giga-transitions per second), but due to the
> 8b/10b encoding, that equates to 4Gbps data rate.
I stand corrected :-)
--
balbi
[-- Attachment #2: Digital signature --]
[-- Type: application/pgp-signature, Size: 819 bytes --]
prev parent reply other threads:[~2014-11-19 3:10 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2014-11-17 23:19 [PATCH] usb: gadget: USB3 support to the legacy printer driver Jorge Ramirez-Ortiz
2014-11-18 0:30 ` Felipe Balbi
2014-11-18 0:54 ` Greg KH
2014-11-18 1:14 ` Jorge Ramirez-Ortiz
2014-11-18 14:19 ` Jorge Ramirez-Ortiz
2014-11-18 15:17 ` Felipe Balbi
2014-11-18 17:52 ` Jorge Ramirez-Ortiz
2014-11-18 18:00 ` Felipe Balbi
2014-11-18 20:41 ` Jorge Ramirez-Ortiz
2014-11-18 20:47 ` Felipe Balbi
2014-11-18 21:33 ` Jorge Ramirez-Ortiz
2014-11-19 3:14 ` Felipe Balbi
2014-11-18 21:45 ` Paul Zimmerman
2014-11-19 3:10 ` Felipe Balbi [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=20141119031049.GB24874@saruman \
--to=balbi@ti.com \
--cc=Paul.Zimmerman@synopsys.com \
--cc=gregkh@linuxfoundation.org \
--cc=jorge.ramirez-ortiz@linaro.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
/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