From mboxrd@z Thu Jan 1 00:00:00 1970 Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935577AbdCMBkm (ORCPT ); Sun, 12 Mar 2017 21:40:42 -0400 Received: from netrider.rowland.org ([192.131.102.5]:49995 "HELO netrider.rowland.org" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with SMTP id S1751138AbdCMBkf (ORCPT ); Sun, 12 Mar 2017 21:40:35 -0400 Date: Sun, 12 Mar 2017 21:40:33 -0400 (EDT) From: Alan Stern X-X-Sender: stern@netrider.rowland.org To: Dave Mielke cc: Samuel Thibault , , , , , , Subject: Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk In-Reply-To: <20170313013649.GH20039@beta.private.mielke.cc> Message-ID: MIME-Version: 1.0 Content-Type: TEXT/PLAIN; charset=US-ASCII Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org 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