Re: synaptics: Your touchpad (PNP: LEN2018 PNP0f13) says it can support a different bus

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

 



What kernel version are you using precisely?

On 11.05.21 19:42, Derek Dolney wrote:
> Hi, Yussuf,
>
> Thanks for your help. I finally noticed today that it does not work.
> Sometimes suspends and resumes but sometimes chokes. Any advice about
> that or can you point me in the right direction to find some fix? I get
> these messages in my syslog:
>
> kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
> kernel: rmi4_f01 rmi4-00.fn01: Failed to write sleep mode: -16.
> kernel: rmi4_f01 rmi4-00.fn01: Suspend failed with code -16.
> kernel: rmi4_physical rmi4-00: Failed to suspend functions: -16
> kernel: rmi4_smbus 7-002c: Failed to suspend device: -16
> kernel: PM: dpm_run_callback(): 0xffffffffc06a0050 returns -16
> kernel: PM: Device 7-002c failed to suspend: error -16
> kernel: PM: Some devices failed to suspend, or early wake event
> detected
> kernel: i801_smbus 0000:00:1f.4: SMBus is busy, can't use it!
> kernel: rmi4_physical rmi4-00: rmi_driver_set_irq_bits: Failed to
> change enabled interrupts!
> kernel: psmouse: probe of serio2 failed with error -1
>
> On Wed, 2021-05-05 at 23:32 +0200, Yussuf Khalil wrote:
>> Hi Derek,
>>
>> have you tested whether suspending and resuming works fine? If yes, can
>> you send in a commit that adds the PNP ID to the list in
>> drivers/input/mouse/synaptics.c?
>>
>> Regards
>> Yussuf Khalil
>>
>> On 05.05.21 23:06, Derek Dolney wrote:
>>> First of all thank you for all your hard work keeping the Linux
>>> kernel
>>> awesome!
>>>
>>> Running on a Lenovo Thinkpad T460p, I found these lines in my dmesg:
>>>
>>> [   17.360279] psmouse serio1: synaptics: queried max coordinates: x
>>> [..5676], y [..4758]
>>> [   17.390832] psmouse serio1: synaptics: queried min coordinates: x
>>> [1266..], y [1096..]
>>> [   17.390853] psmouse serio1: synaptics: Your touchpad (PNP: LEN2018
>>> 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.
>>>
>>> Indeed i2c-hid and hid-rmi modules are not loaded. Setting
>>> psmouse.synaptics_intertouch=1 as directed, now I get the following
>>> and
>>> the device works well imho:
>>>
>>> [   80.967562] psmouse serio1: synaptics: queried max coordinates: x
>>> [..5676], y [..4758]
>>> [   81.004823] psmouse serio1: synaptics: queried min coordinates: x
>>> [1266..], y [1096..]
>>> [   81.004828] psmouse serio1: synaptics: Trying to set up SMBus
>>> access
>>> [   81.025153] rmi4_smbus 7-002c: registering SMbus-connected sensor
>>> [   81.079177] rmi4_f01 rmi4-00.fn01: found RMI device, manufacturer:
>>> Synaptics, product: TM3053-006, fw id: 2010421
>>> [   81.141785] input: Synaptics TM3053-006 as /devices/rmi4-
>>> 00/input/input22
>>> [   81.148458] serio: RMI4 PS/2 pass-through port at rmi4-00.fn03
>>> [   81.559841] input: PS/2 Generic Mouse as /devices/rmi4-00/rmi4-
>>> 00.fn03/serio2/input/input23
>>>
>>> Thanks again,
>>> Derek
>>>
>



[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