All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Adrien Vergé" <adrienverge@gmail.com>
To: Oliver Neukum <oneukum@suse.com>
Cc: "Jiri Kosina" <jikos@kernel.org>,
	"Greg Kroah-Hartman" <gregkh@linuxfoundation.org>,
	"Logan Gunthorpe" <logang@deltatee.com>,
	"Hans de Goede" <hdegoede@redhat.com>,
	"Vincent Palatin" <vpalatin@chromium.org>,
	"Adrien Vergé" <adrienverge@gmail.com>,
	"Macpaul Lin" <macpaul@gmail.com>,
	"Adel Gadllah" <adel.gadllah@gmail.com>,
	linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	linux-usb@vger.kernel.org
Subject: [PATCH v3 1/2] USB: quirks: Fix another ELAN touchscreen
Date: Tue, 24 Nov 2015 14:49:07 +0100	[thread overview]
Message-ID: <1448372948-8861-2-git-send-email-adrienverge@gmail.com> (raw)
In-Reply-To: <1448372948-8861-1-git-send-email-adrienverge@gmail.com>

Like other buggy models that had their fixes [1], the touchscreen with
id 04f3:21b8 from ELAN Microelectronics needs the device-qualifier
quirk. Otherwise, it fails to respond, blocks the boot for a random
amount of time and pollutes dmesg with:

[ 2887.373196] usb 1-5: new full-speed USB device number 41 using xhci_hcd
[ 2889.502000] usb 1-5: unable to read config index 0 descriptor/start: -71
[ 2889.502005] usb 1-5: can't read configurations, error -71
[ 2889.654571] usb 1-5: new full-speed USB device number 42 using xhci_hcd
[ 2891.783438] usb 1-5: unable to read config index 0 descriptor/start: -71
[ 2891.783443] usb 1-5: can't read configurations, error -71

[1]: See commits c68929f, 876af5d, d749947, a32c99e and dc703ec.

Tested-by: Adrien Vergé <adrienverge@gmail.com>
Signed-off-by: Adrien Vergé <adrienverge@gmail.com>
---
 drivers/usb/core/quirks.c | 3 +++
 1 file changed, 3 insertions(+)

diff --git a/drivers/usb/core/quirks.c b/drivers/usb/core/quirks.c
index f5a3819..fcd6ac0 100644
--- a/drivers/usb/core/quirks.c
+++ b/drivers/usb/core/quirks.c
@@ -125,6 +125,9 @@ static const struct usb_device_id usb_quirk_list[] = {
 	{ USB_DEVICE(0x04f3, 0x016f), .driver_info =
 			USB_QUIRK_DEVICE_QUALIFIER },
 
+	{ USB_DEVICE(0x04f3, 0x21b8), .driver_info =
+			USB_QUIRK_DEVICE_QUALIFIER },
+
 	/* Roland SC-8820 */
 	{ USB_DEVICE(0x0582, 0x0007), .driver_info = USB_QUIRK_RESET_RESUME },
 
-- 
2.4.3


  reply	other threads:[~2015-11-24 13:50 UTC|newest]

Thread overview: 32+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2015-11-22  4:06 [PATCH] USB: quirks: Fix another ELAN touchscreen Adrien Vergé
2015-11-22  4:06 ` Adrien Vergé
2015-11-23 14:52 ` Jiri Kosina
2015-11-23 14:52   ` Jiri Kosina
2015-11-23 17:37   ` Adrien Vergé
2015-11-24  7:29     ` Oliver Neukum
2015-11-23 17:43 ` [PATCH v2] " Adrien Vergé
2015-11-24 13:49 ` [PATCH v3 0/2] Fixes for ELAN touchscreens Adrien Vergé
2015-11-24 13:49   ` Adrien Vergé [this message]
2015-11-24 13:49   ` [PATCH v3 2/2] USB: quirks: Apply ALWAYS_POLL to all ELAN devices Adrien Vergé
2015-11-24 14:11     ` Benjamin Tissoires
2015-11-24 14:11       ` Benjamin Tissoires
2015-11-24 14:34       ` Adrien Vergé
2015-11-24 15:02 ` [PATCH v4 0/2] Fixes for ELAN touchscreens Adrien Vergé
2015-11-24 15:02   ` Adrien Vergé
2015-11-24 15:02   ` [PATCH v4 1/2] USB: quirks: Fix another ELAN touchscreen Adrien Vergé
2015-11-24 15:02   ` [PATCH v4 2/2] USB: quirks: Apply ALWAYS_POLL to all ELAN devices Adrien Vergé
2015-11-24 15:02     ` Adrien Vergé
2015-11-24 16:11     ` Benjamin Tissoires
2015-11-24 16:11       ` Benjamin Tissoires
2015-11-24 16:41     ` kbuild test robot
2015-11-24 16:41       ` kbuild test robot
2015-12-01 18:21     ` Greg Kroah-Hartman
2015-12-01 18:56 ` [PATCH v5 0/2] Fixes for ELAN touchscreens Adrien Vergé
2015-12-01 18:56   ` [PATCH v5 1/2] USB: quirks: Fix another ELAN touchscreen Adrien Vergé
2015-12-01 18:56     ` Adrien Vergé
2015-12-01 18:56   ` [PATCH v5 2/2] USB: quirks: Apply ALWAYS_POLL to all ELAN devices Adrien Vergé
2015-12-01 22:09     ` Jiri Kosina
2015-12-01 22:09       ` Jiri Kosina
2015-12-01 22:11       ` Greg Kroah-Hartman
2015-12-01 22:11         ` Greg Kroah-Hartman
2015-12-02  8:53         ` Adrien Vergé

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=1448372948-8861-2-git-send-email-adrienverge@gmail.com \
    --to=adrienverge@gmail.com \
    --cc=adel.gadllah@gmail.com \
    --cc=gregkh@linuxfoundation.org \
    --cc=hdegoede@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-usb@vger.kernel.org \
    --cc=logang@deltatee.com \
    --cc=macpaul@gmail.com \
    --cc=oneukum@suse.com \
    --cc=vpalatin@chromium.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 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.