Comment 295 for bug 606238

@dturvene

Thanks for taking the time to walk me through this. The DSDT entry for my touchpad is "DLL0584", and now that I know what to look for I can see it all over the place:

/var/log/dmesg:[ 0.312892] pnp 00:0b: Plug and Play ACPI device, IDs DLL0584 PNP0f13 (active)
/var/log/udev:KERNEL[1.827693] add /devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/DLL0584:00 (acpi)
/var/log/udev:DEVPATH=/devices/LNXSYSTM:00/device:00/PNP0A08:00/device:01/DLL0584:00
/var/log/udev:MODALIAS=acpi:DLL0584:PNP0F13:
/var/log/Xorg.0.log:[ 6.601] (--) PCI:*(0:0:2:0) 8086:0166:1028:0584 rev 9, Mem @ 0xf7800000/4194304, 0xe0000000/268435456, I/O @ 0x0000f000/64

I have added a new line to alps_model_data in alps.c, making up the values I didn't know or copying them from the other V5 entry:

136a137,138
> /* Dell Latitude 6430u */
> { { 0x88, 0x08, 0x22 }, 0x22, ALPS_PROTO_V5, 0x8f, 0x8f, ALPS_DUALPOINT },

The touchpad is now recognized by the kernel as an Alps Dualpoint:

$ tail /var/log/syslog
kernel: [ 8248.837263] acpi_get_handle failure: status 5
kernel: [ 8248.855173] psmouse serio1: alps: E6 report: 00 00 64
kernel: [ 8248.873121] psmouse serio1: alps: E7 report: 73 03 0a
kernel: [ 8248.889559] psmouse serio1: alps: Model=25, proto_version=4
kernel: [ 8250.026387] input: DualPoint Stick as /devices/platform/i8042/serio1/input/input24
kernel: [ 8250.038950] input: AlpsPS/2 ALPS DualPoint TouchPad as /devices/platform/i8042/serio1/input/input25

$ xinput -list
⎡ Virtual core pointer id=2 [master pointer (3)]
⎜ ↳ Virtual core XTEST pointer id=4 [slave pointer (2)]
⎜ ↳ Logitech USB Optical Mouse id=11 [slave pointer (2)]
⎜ ↳ DualPoint Stick id=14 [slave pointer (2)]
⎜ ↳ AlpsPS/2 ALPS DualPoint TouchPad id=16 [slave pointer (2)]

I can now change the touchpad settings via synclient / tpconfig / gnome control center. Vertical and horizontal edge scrolling work, and also disabling the touchpad while typing. 2 finger and 3 finger tapping also work, I haven't tested other multitouch gestures. If there's something else I can test/try that will help improve this driver just let me know, I'll keep an eye on this bug in case it's needed in the future.

Thanks again Dave and others for your efforts and your help with this issue.

^dj