Bug 96756

Summary: ImPS/2 BYD TouchPad not supported by Synaptics
Product: xorg Reporter: Arcadiy Ivanov <arcadiy>
Component: Input/synapticsAssignee: Peter Hutterer <peter.hutterer>
Status: RESOLVED NOTOURBUG QA Contact:
Severity: enhancement    
Priority: medium CC: peter.hutterer
Version: unspecified   
Hardware: x86-64 (AMD64)   
OS: Linux (All)   
Whiteboard:
i915 platform: i915 features:

Description Arcadiy Ivanov 2016-06-30 20:14:13 UTC
Synaptics does not recognize ImPS/2 BYD TouchPad as a legitimate touchpad. The kernel patch for BYD Touchpad have been there since March 2016 (https://patchwork.kernel.org/patch/8173031/, https://github.com/torvalds/linux/commits/master/drivers/input/mouse/byd.c).

Without this support touchpad acceleration, speed and scroll direction cannot be changed. KDE does not recognize this touchpad as a touchpad either.

Dell Precision 7x10, 5x10 and XPS 9x50 lines are affected to my knowledge.
Comment 1 Peter Hutterer 2016-06-30 21:57:03 UTC
What's the evemu-describe output of this device?
Comment 2 Arcadiy Ivanov 2016-07-01 02:47:31 UTC
# EVEMU 1.3
# Kernel: 4.6.3-300.fc24.x86_64
# DMI: dmi:bvnDellInc.:bvr1.05.04:bd05/27/2016:svnDellInc.:pnPrecision7510:pvr:rvnDellInc.:rn0M91XC:rvrA00:cvnDellInc.:ct9:cvr:
# Input device name: "ImPS/2 BYD TouchPad"
# Input device ID: bus 0x11 vendor 0x02 product 0x05 version 0000
# Supported events:
#   Event type 0 (EV_SYN)
#     Event code 0 (SYN_REPORT)
#     Event code 1 (SYN_CONFIG)
#     Event code 2 (SYN_MT_REPORT)
#     Event code 3 (SYN_DROPPED)
#     Event code 4 ((null))
#     Event code 5 ((null))
#     Event code 6 ((null))
#     Event code 7 ((null))
#     Event code 8 ((null))
#     Event code 9 ((null))
#     Event code 10 ((null))
#     Event code 11 ((null))
#     Event code 12 ((null))
#     Event code 13 ((null))
#     Event code 14 ((null))
#   Event type 1 (EV_KEY)
#     Event code 272 (BTN_LEFT)
#     Event code 273 (BTN_RIGHT)
#     Event code 274 (BTN_MIDDLE)
#   Event type 2 (EV_REL)
#     Event code 0 (REL_X)
#     Event code 1 (REL_Y)
#     Event code 8 (REL_WHEEL)
# Properties:
#   Property  type 0 (INPUT_PROP_POINTER)
N: ImPS/2 BYD TouchPad
I: 0011 0002 0005 0000
P: 01 00 00 00 00 00 00 00
B: 00 0b 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 07 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 01 00 00 00 00 00 00 00 00
B: 02 03 01 00 00 00 00 00 00
B: 03 00 00 00 00 00 00 00 00
B: 04 00 00 00 00 00 00 00 00
B: 05 00 00 00 00 00 00 00 00
B: 11 00 00 00 00 00 00 00 00
B: 12 00 00 00 00 00 00 00 00
B: 14 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
B: 15 00 00 00 00 00 00 00 00
Comment 3 Peter Hutterer 2016-07-01 03:56:23 UTC
this is a kernel issue, the touchpad isn't recognised correctly and still looks like a 3-button mouse. that's why the touchpad drivers which require absolute mode don't hook onto it.

2d5f5611dd0de5 which enables absolute mode is in v4.6 but it apparently doesn't hook against your device. Best if you file a kernel bug and contact Richard and Chris, the authors of that patch to figure out why it's not working on your device.
Comment 4 Arcadiy Ivanov 2016-07-01 04:42:50 UTC
Thanks! 
Cross-linking here for the reference: https://bugzilla.kernel.org/show_bug.cgi?id=121281

Use of freedesktop.org services, including Bugzilla, is subject to our Code of Conduct. How we collect and use information is described in our Privacy Policy.