[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <Pine.LNX.4.44L0.1703122139020.30930-100000@netrider.rowland.org>
Date: Sun, 12 Mar 2017 21:40:33 -0400 (EDT)
From: Alan Stern <stern@...land.harvard.edu>
To: Dave Mielke <dave@...lke.cc>
cc: Samuel Thibault <samuel.thibault@...-lyon.org>,
<gregkh@...uxfoundation.org>, <linux-usb@...r.kernel.org>,
<linux-kernel@...r.kernel.org>, <kevin.derome@...tech.eu>,
<clause.andreabush@...il.com>, <mengualjeanphi@...e.fr>
Subject: Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
On Sun, 12 Mar 2017, Dave Mielke wrote:
> [quoted lines by Alan Stern on 2017/03/12 at 21:31 -0400]
>
> >A device's speed is only partially related to its USB version. A
> >USB-1.1 device can run at low speed or full speed. A USB-2 device can
> >run at low, full, or high speed. And a USB-3 device can run at low,
> >full, high, or Super speed.
>
> Yes, I did know this, so maybe I misunderstood what you were wondering about.
> Were you wondering why 64ms was too long?
No, I was wondering why an HID device would run at high speed. Both
you and Samuel implied that this was because it was a USB-2 device.
But that is not an adequate answer, because it is perfectly valid for a
USB-2 device to run at full speed.
Alan Stern
Powered by blists - more mailing lists