Re: Synaptics i2c and rmi: dmesg requested to send report

[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]

 



Hi, Tim. Thanks for your report.

With "psmouse.synaptics_intertouch=1", do suspend and hibernation (aka s2ram and s2disk) work without problem? (This is a must check.)

If it is possible for you to apply a patch to the source and compile the kernel, I'll prepare a patch and send it.

> I have not received any response on below message.

Sorry to hear that. I'm not a kernel developer, but have been working on this issue to help them. Unless someone volunteers, a change won't happen, unfortunately. (In fact, I was aware of your first message, but I've been busy. ;-)

Regards,
Teika

From: Tim Mohlmann <tim@xxxxxxxxxx>
Subject: Synaptics i2c and rmi: dmesg requested to send report
Date: Mon, 27 May 2019 14:08:13 +0300

> Good day,
>
> I'm sending this report as suggested by dmesg message:
>
> psmouse serio2: synaptics: Your touchpad (PNP: SYN1218 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.
>
> Checked in /proc/bus/input/devices:
>
> I: Bus=0011 Vendor=0002 Product=0007 Version=01b1
> N: Name="SynPS/2 Synaptics TouchPad"
> P: Phys=isa0060/serio2/input0
> S: Sysfs=/devices/platform/i8042/serio2/input/input10
> U: Uniq=
> H: Handlers=event5
> B: PROP=1
> B: EV=b
> B: KEY=e520 30000 0 0 0 0
> B: ABS=660800011000003
>
> So I've set psmouse.synaptics_intertouch=1 on kernel command line and
> after reboot:
>
> I: Bus=001d Vendor=06cb Product=0000 Version=0000
> N: Name="Synaptics TM3189-001"
> P: Phys=rmi4-00/input0
> S: Sysfs=/devices/rmi4-00/input/input11
> U: Uniq=
> H: Handlers=event5
> B: PROP=1
> B: EV=b
> B: KEY=e520 30000 0 0 0 0
> B: ABS=6f3800001000003
>
> Its worth to mention that the touchpad worked using PS/2, but was a bit
> choppy in its response. It works way better after setting
> psmouse.synaptics_intertouch=1.
>
> I don't now the make of the touchpad, as it does not show up in lspci.
> It's part of a custom built laptop, based on a Clevo N350DW model.
> Hopefully the above vendor ID is all you need.
>
> |$ uname -r 5.1.4-gentoo $ grep -E 'INPUT|I2C_HID|HID_RMI' .config
> CONFIG_RFKILL_INPUT=y CONFIG_INPUT=y CONFIG_INPUT_LEDS=m
> CONFIG_INPUT_FF_MEMLESS=y CONFIG_INPUT_POLLDEV=y
> CONFIG_INPUT_SPARSEKMAP=m # CONFIG_INPUT_MATRIXKMAP is not set #
> CONFIG_INPUT_MOUSEDEV is not set # CONFIG_INPUT_JOYDEV is not set
> CONFIG_INPUT_EVDEV=y # CONFIG_INPUT_EVBUG is not set
> CONFIG_INPUT_KEYBOARD=y CONFIG_INPUT_MOUSE=y CONFIG_INPUT_JOYSTICK=y
> CONFIG_INPUT_TABLET=y CONFIG_INPUT_TOUCHSCREEN=y CONFIG_INPUT_MISC=y #
> CONFIG_INPUT_AD714X is not set # CONFIG_INPUT_BMA150 is not set #
> CONFIG_INPUT_E3X0_BUTTON is not set # CONFIG_INPUT_MSM_VIBRATOR is not
> set # CONFIG_INPUT_PCSPKR is not set # CONFIG_INPUT_MMA8450 is not set #
> CONFIG_INPUT_APANEL is not set # CONFIG_INPUT_ATLAS_BTNS is not set #
> CONFIG_INPUT_ATI_REMOTE2 is not set # CONFIG_INPUT_KEYSPAN_REMOTE is not
> set # CONFIG_INPUT_KXTJ9 is not set # CONFIG_INPUT_POWERMATE is not set
> # CONFIG_INPUT_YEALINK is not set # CONFIG_INPUT_CM109 is not set #
> CONFIG_INPUT_UINPUT is not set # CONFIG_INPUT_PCF8574 is not set #
> CONFIG_INPUT_ADXL34X is not set # CONFIG_INPUT_IMS_PCU is not set #
> CONFIG_INPUT_CMA3000 is not set # CONFIG_INPUT_IDEAPAD_SLIDEBAR is not
> set # CONFIG_INPUT_DRV2665_HAPTICS is not set #
> CONFIG_INPUT_DRV2667_HAPTICS is not set
> CONFIG_USB_VIDEO_CLASS_INPUT_EVDEV=y CONFIG_USB_PWC_INPUT_EVDEV=y
> CONFIG_SND_JACK_INPUT_DEV=y # CONFIG_SND_HDA_INPUT_BEEP is not set
> CONFIG_HID_RMI=y CONFIG_I2C_HID=y|
>
> Let me know if there is anything else you need from me.
>
> Br, Tim Mohlmann




[Index of Archives]     [Linux Media Devel]     [Linux USB Devel]     [Video for Linux]     [Linux Audio Users]     [Yosemite News]     [Linux Kernel]     [Linux SCSI]     [Linux Wireless Networking]     [Linux Omap]

  Powered by Linux