public inbox for stable@vger.kernel.org
 help / color / mirror / Atom feed
From: Greg Kroah-Hartman <gregkh@linuxfoundation.org>
To: Nicolas Dumazet <ndumazet@google.com>
Cc: Jean-Francois Le Fillatre <jflf_kernel@gmx.com>,
	Petar Kostic <petar@kostic.dev>, Oliver Neukum <oneukum@suse.com>,
	Ole Ernst <olebowle@gmx.com>, Hannu Hartikainen <hannu@hrtk.in>,
	Jimmy Wang <wangjm221@gmail.com>,
	linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org,
	stable@vger.kernel.org
Subject: Re: [PATCH v2] usb: add NO_LPM quirk for Realforce 87U Keyboard
Date: Wed, 9 Nov 2022 12:29:36 +0100	[thread overview]
Message-ID: <Y2uPIItkmcYgDy6k@kroah.com> (raw)
In-Reply-To: <20221027090342.38928-1-ndumazet@google.com>

On Thu, Oct 27, 2022 at 11:03:42AM +0200, Nicolas Dumazet wrote:
> Before adding this quirk, this (mechanical keyboard) device would not be
> recognized, logging:
> 
>   new full-speed USB device number 56 using xhci_hcd
>   unable to read config index 0 descriptor/start: -32
>   chopping to 0 config(s)
> 
> It would take dozens of plugging/unpuggling cycles for the keyboard to
> be recognized. Keyboard seems to simply work after applying this quirk.
> 
> This issue had been reported by users in two places already ([1], [2])
> but nobody tried upstreaming a patch yet. After testing I believe their
> suggested fix (DELAY_INIT + NO_LPM + DEVICE_QUALIFIER) was probably a
> little overkill. I assume this particular combination was tested because
> it had been previously suggested in [3], but only NO_LPM seems
> sufficient for this device.
> 
> [1]: https://qiita.com/float168/items/fed43d540c8e2201b543
> [2]: https://blog.kostic.dev/posts/making-the-realforce-87ub-work-with-usb30-on-Ubuntu/
> [3]: https://bugs.launchpad.net/ubuntu/+source/linux/+bug/1678477
> 
> ---
> Changes in v2:
>   - add the entry to the right location (sorting entries by
>     vendor/device id).
> 
> Cc: stable@vger.kernel.org
> Signed-off-by: Nicolas Dumazet <ndumazet@google.com>
> ---

By putting your s-o-b below the --- line, tools will drop it, how did
you test this?

Put the v2 stuff below the --- line, don't add a new one.  See the
thousands of examples on the list for how to do this correctly (as well
as the kernel documentation.)

Can you fix this up and resend a v3 please?

thanks,

greg k-h

  reply	other threads:[~2022-11-09 11:29 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-27  9:03 [PATCH v2] usb: add NO_LPM quirk for Realforce 87U Keyboard Nicolas Dumazet
2022-11-09 11:29 ` Greg Kroah-Hartman [this message]
2022-11-09 12:31   ` Nicolas Dumazet

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=Y2uPIItkmcYgDy6k@kroah.com \
    --to=gregkh@linuxfoundation.org \
    --cc=hannu@hrtk.in \
    --cc=jflf_kernel@gmx.com \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=ndumazet@google.com \
    --cc=olebowle@gmx.com \
    --cc=oneukum@suse.com \
    --cc=petar@kostic.dev \
    --cc=stable@vger.kernel.org \
    --cc=wangjm221@gmail.com \
    /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