mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Greg KH <gregkh@linuxfoundation.org>
To: David Pieters <davidpieters1978@gmail.com>
Cc: linux-usb@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] USB: quirks: add USB_QUIRK_NO_LPM for ELECOM DEFT Pro TrackBall
Date: Wed, 30 Sep 2026 08:55:27 +0200	[thread overview]
Message-ID: <2026093013-stature-rekindle-ba2a@gregkh> (raw)
In-Reply-To: <CAJ3h-bPZ4LyGyoUywhxnGx-Je3irbM67g5z2y6Sn_6oxOdtAvA@mail.gmail.com>

On Wed, Sep 30, 2026 at 08:39:06AM +0200, David Pieters wrote:
> The 2.4GHz wireless USB receiver of the ELECOM DEFT Pro TrackBall
> (056e:0132) and its wired counterpart (056e:0131) fail to handle USB
> Link Power Management (LPM / USB 2.0 L1 sleep states) during initial
> enumeration on modern USB host controllers. When LPM negotiation occurs
> at boot, the device stalls and fails to register any input events until
> it is physically unplugged and replugged.
> 
> Applying USB_QUIRK_NO_LPM prevents LPM negotiation and allows the device
> to initialize properly at system boot.
> 
> Signed-off-by: David Pieters <davidpieters1978@gmail.com>
> ---
>  drivers/usb/core/quirks.c | 4 ++++
>  1 file changed, 4 insertions(+)
> 
> diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
> index 8923a10e7b41..0f34e819b22a 100644
> --- a/drivers/usb/core/quirks.c
> +++ b/drivers/usb/core/quirks.c
> @@ -350,6 +350,10 @@ static const struct usb_device_id usb_quirk_list[] = {
>   /* Corsair Strafe RGB */
>   { USB_DEVICE(0x1b1c, 0x1b20), .driver_info = USB_QUIRK_DELAY_INIT },
> 
> + /* ELECOM DEFT Pro TrackBall (fails on USB Link Power Management) */
> + { USB_DEVICE(0x056e, 0x0131), .driver_info = USB_QUIRK_NO_LPM },
> + { USB_DEVICE(0x056e, 0x0132), .driver_info = USB_QUIRK_NO_LPM },
> +
>   { }  /* terminating entry must be last */
>  };
> 
> -- 
> 2.43.0

Hi,

This is the friendly patch-bot of Greg Kroah-Hartman.  You have sent him
a patch that has triggered this response.  He used to manually respond
to these common problems, but in order to save his sanity (he kept
writing the same thing over and over, yet to different people), I was
created.  Hopefully you will not take offence and will fix the problem
in your patch and resubmit it so that it can be accepted into the Linux
kernel tree.

You are receiving this message because of the following common error(s)
as indicated below:

- Your patch is malformed (tabs converted to spaces, linewrapped, etc.)
  and can not be applied.  Please read the file,
  Documentation/process/email-clients.rst in order to fix this.


If you wish to discuss this problem further, or you have questions about
how to resolve this issue, please feel free to respond to this email and
Greg will reply once he has dug out from the pending patches received
from other developers.

thanks,

greg k-h's patch email bot

       reply	other threads:[~2026-09-30  6:55 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
     [not found] <CAJ3h-bPZ4LyGyoUywhxnGx-Je3irbM67g5z2y6Sn_6oxOdtAvA@mail.gmail.com>
2026-09-30  6:55 ` Greg KH [this message]
2026-09-30  9:40 David Pieters
2026-09-30 10:49 ` Greg Kroah-Hartman

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=2026093013-stature-rekindle-ba2a@gregkh \
    --to=gregkh@linuxfoundation.org \
    --cc=davidpieters1978@gmail.com \
    --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

all inboxes | Powered by JetHome®