Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S1752617AbdHKHmU (ORCPT ); Fri, 11 Aug 2017 03:42:20 -0400 Received: from mail-pg0-f65.google.com ([74.125.83.65]:36911 "EHLO mail-pg0-f65.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1751871AbdHKHmR (ORCPT ); Fri, 11 Aug 2017 03:42:17 -0400 From: JamChen To: jikos@kernel.org, benjamin.tissoires@redhat.com Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org, zboszor@pr.hu, jam.chen.egalax@gmail.com Subject: [PATCH] HID: core: assign usbhid to handle EETI PID=0x0001 HID device Date: Fri, 11 Aug 2017 15:42:01 +0800 Message-Id: <20170811074201.2747-1-jam.chen.egalax@gmail.com> X-Mailer: git-send-email 2.11.0 Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1143 Lines: 33 From: Jam Chen The vendor used the same PID(0x0001) for multiple touch IC controllers. The newer ICs can support HID class and report the multitouch collection in the descriptor. So they were handled by the hid-multitouch driver. But some customized firmwares don't support multitouch protocol even if driver have got the Win8 blob data. Actually, those ICs only support the single touch function, and report the mouse protocol by default. We can assign usbhid to handle them all. Signed-off-by: Jam Chen --- drivers/hid/hid-core.c | 4 ++++ 1 file changed, 4 insertions(+) diff --git a/drivers/hid/hid-core.c b/drivers/hid/hid-core.c index 9017dcc14502..df4696022488 100644 --- a/drivers/hid/hid-core.c +++ b/drivers/hid/hid-core.c @@ -828,6 +828,10 @@ static int hid_scan_report(struct hid_device *hid) */ hid->group = HID_GROUP_RMI; break; + case USB_VENDOR_ID_DWAV: + if (hid->product == USB_DEVICE_ID_EGALAX_TOUCHCONTROLLER) + hid->group = HID_GROUP_GENERIC; + break; } /* fall back to generic driver in case specific driver doesn't exist */ -- 2.11.0