On 20 June 2017 at 04:55, Dmitry Torokhov <dmitry.torokhov@xxxxxxxxx> wrote: > On Sat, Jun 10, 2017 at 12:42:13PM +0200, Damjan Georgievski wrote: >> > >> > - mark "guest" RMI device as pass-through port to avoid "phantom" ALPS >> > toouchpad on newer Lenovo Carbons >> >> What's the end game for supporting these devices? >> >> With the latest HEAD of Linus, first I get: >> » Jun 10 12:19:17 cambrian kernel: psmouse serio1: synaptics: Your >> touchpad (PNP: LEN0072 PNP0f13) says it can support a different bus. >> If i2c-hid and hid-rmi are not used, you might want to try setting >> psmouse.synaptics_intertouch to 1 and report this to >> linux-input@xxxxxxxxxxxxxxx. >> >> Then if I patch drivers/input/mouse/synaptics.c and add "LEN0072" to >> smbus_pnp_ids, this strange thing happens: >> >> [ 8.526635] psmouse serio1: synaptics: queried max coordinates: x >> [..5676], y [..4760] >> [ 8.555746] psmouse serio1: synaptics: queried min coordinates: x >> [1266..], y [1094..] >> [ 8.555750] psmouse serio1: synaptics: Trying to set up SMBus access >> [ 8.615774] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: >> Synaptics, product: TM3289-002, fw id: 2492434 >> [ 8.679863] input: Synaptics TM3289-002 as /devices/rmi4-00/input/input18 >> [ 8.682660] mousedev: PS/2 mouse device common for all mice >> … snipped … >> [ 107.225549] input: ImPS/2 Generic Wheel Mouse as >> /devices/rmi4-00/rmi4-00.fn03/serio2/input/input20 >> >> Notice how the trackpoint only appeared 100 seconds after boot (X was >> already started and initially the trackpoint was not listed in xinput) > > 100 seconds is quire ridiculous. Could you please post your entire boot > log so we can understand what happened there. Sorry for the delay, I was travelling and couldn't put more time into it … There was nothing happening in-between (at least nothing in the logs). Just to make this clear, I'm running the lastest linus 4.12 tree, with this[1] one-liner patch to add the X1 Carbon to smbus_pnp_ids. The behaviour is that after boot, xinput only shows "Synaptics TM3289-002", and evemu-describe too. I'm not sure how the trackpoint appeared previously, but just testing now, and the trackpoint device did *not* appear for an hour at all. But after rmmod-ing the psmouse module and loading it again it did show up. Jun 25 15:59:32 cambrian kernel: psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4760] Jun 25 15:59:32 cambrian kernel: psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1094..] Jun 25 15:59:32 cambrian kernel: psmouse serio1: synaptics: Trying to set up SMBus access Jun 25 15:59:32 cambrian kernel: rmi4_smbus 6-002c: registering SMbus-connected sensor Jun 25 15:59:32 cambrian kernel: rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer: Synaptics, product: TM3289-002, fw id: 2492434 Jun 25 15:59:32 cambrian kernel: input: Synaptics TM3289-002 as /devices/rmi4-00/input/input18 ... Jun 25 17:16:39 cambrian sudo[5770]: damjan : TTY=pts/1 ; PWD=/home/damjan ; USER=root ; COMMAND=/usr/bin/rmmod psmouse Jun 25 17:16:45 cambrian sudo[5786]: damjan : TTY=pts/1 ; PWD=/home/damjan ; USER=root ; COMMAND=/usr/bin/modprobe psmouse Jun 25 17:16:46 cambrian kernel: psmouse serio1: synaptics: queried max coordinates: x [..5676], y [..4760] Jun 25 17:16:46 cambrian kernel: psmouse serio1: synaptics: queried min coordinates: x [1266..], y [1094..] Jun 25 17:16:46 cambrian kernel: psmouse serio1: synaptics: Trying to set up SMBus access Jun 25 17:16:46 cambrian kernel: rmi4_smbus 6-002c: registering SMbus-connected sensor Jun 25 17:16:46 cambrian kernel: rmi4_f01 rmi4-01.fn01: found RMI device, manufacturer: Synaptics, product: TM3289-002, fw id: 2492434 Jun 25 17:16:46 cambrian kernel: input: Synaptics TM3289-002 as /devices/rmi4-01/input/input22 Jun 25 17:16:47 cambrian kernel: input: ImPS/2 Generic Wheel Mouse as /devices/rmi4-01/rmi4-01.fn03/serio3/input/input23 [1] https://github.com/gdamjan/linux/commit/517fad4882d6274478b82e5dc68775d8005df6be -- damjan -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
