From: Samuel Thibault <samuel.thibault@ens-lyon.org>
To: Alan Stern <stern@rowland.harvard.edu>
Cc: gregkh@linuxfoundation.org, linux-usb@vger.kernel.org,
linux-kernel@vger.kernel.org, dave@mielke.cc,
kevin.derome@epitech.eu, clause.andreabush@gmail.com,
mengualjeanphi@free.fr
Subject: Re: [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk
Date: Sun, 12 Mar 2017 22:47:13 +0100 [thread overview]
Message-ID: <20170312214713.dtefwa26z7xiyazn@var.youpi.perso.aquilenet.fr> (raw)
In-Reply-To: <Pine.LNX.4.44L0.1703121701080.22407-100000@netrider.rowland.org>
Alan Stern, on dim. 12 mars 2017 17:18:51 -0400, wrote:
> Interesting. This is a high-speed device that mistakenly uses the
> low/full-speed encoding for an interrupt bInterval value?
Yes...
> That's pretty unusual. Most HID devices (which includes the Braille
> devices I have heard of) run at low speed, and a few of them run at
> full speed. I can't remember any running at high speed.
That's the first device for which we have such issue. We'll try to
check whether some other devices need the same quirk.
> > + */
> > + /*
> > + * This quirk fixes bIntervals reported in ms.
> > + */
> > + if (to_usb_device(ddev)->quirks &
> > + USB_QUIRK_MS_INTR_BINTERVAL)
> > + i = j = n;
>
> You want to use the bInterval value the device intended to provide, not
> a default value.
n is alreay computed as such above, but OK :) (and better clamp anyway)
> > + /* Baum Vario Ultra */
> > + { USB_DEVICE(0x0904, 0x6101), .driver_info =
> > + USB_QUIRK_MS_INTR_BINTERVAL },
> > + { USB_DEVICE(0x0904, 0x6102), .driver_info =
> > + USB_QUIRK_MS_INTR_BINTERVAL },
> > + { USB_DEVICE(0x0904, 0x6103), .driver_info =
> > + USB_QUIRK_MS_INTR_BINTERVAL },
>
> You didn't read the comment at the start of the file. :-) This list
> is supposed to remain sorted by vendor and product ID.
D'oh, sorry :)
Samuel
prev parent reply other threads:[~2017-03-12 21:47 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-12 20:10 [PATCH] usb-core: Add MS_INTR_BINTERVAL USB quirk Samuel Thibault
2017-03-12 21:18 ` Alan Stern
2017-03-12 21:42 ` Dave Mielke
2017-03-13 1:31 ` Alan Stern
2017-03-13 1:36 ` Dave Mielke
2017-03-13 1:40 ` Alan Stern
2017-03-13 1:46 ` Dave Mielke
2017-03-13 10:38 ` Dave Mielke
2017-03-14 1:43 ` Alan Stern
2017-03-14 2:20 ` Dave Mielke
2017-03-14 8:45 ` Samuel Thibault
2017-03-13 7:05 ` Samuel Thibault
2017-03-14 1:44 ` Alan Stern
2017-03-12 21:47 ` Samuel Thibault [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=20170312214713.dtefwa26z7xiyazn@var.youpi.perso.aquilenet.fr \
--to=samuel.thibault@ens-lyon.org \
--cc=clause.andreabush@gmail.com \
--cc=dave@mielke.cc \
--cc=gregkh@linuxfoundation.org \
--cc=kevin.derome@epitech.eu \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-usb@vger.kernel.org \
--cc=mengualjeanphi@free.fr \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.