mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: JamChen <jam.chen.egalax@gmail.com>
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	[thread overview]
Message-ID: <20170811074201.2747-1-jam.chen.egalax@gmail.com> (raw)

From: Jam Chen <jam.chen.egalax@gmail.com>

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 <jam.chen.egalax@gmail.com>
---
 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

             reply	other threads:[~2017-08-11  7:42 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-08-11  7:42 JamChen [this message]
     [not found] ` <778fb127-4e62-943b-a14f-f219ffdac152@pr.hu>
     [not found]   ` <CAPHAoVBjJPekxs8=m314f9ziD60ANgzeuvOVoXeYridoEt3FeQ@mail.gmail.com>
2017-08-17 13:59     ` Boszormenyi Zoltan
2017-08-22  9:33 ` Benjamin Tissoires
2017-09-22  8:33   ` Boszormenyi Zoltan
     [not found] ` <71e49c0b-959b-4d55-b1d3-6aafe85f8652@gmail.com>
2017-08-22 16:13   ` Kirill Esipov

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=20170811074201.2747-1-jam.chen.egalax@gmail.com \
    --to=jam.chen.egalax@gmail.com \
    --cc=benjamin.tissoires@redhat.com \
    --cc=jikos@kernel.org \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=zboszor@pr.hu \
    /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®