i2c errors when using the touchpad #39

New issue

Open

opened 2018-09-15 23:11:22 +02:00 by SolidEva · 2 comments

SolidEva commented

2018-09-15 23:11:22 +02:00

(Migrated from github.com)

When using the touchpad, this gets printed in dmesg once an a while:

elan_i2c 4-0015: invalid report id data (ff)

One of the untested patches seems to fix this issue, further testing required.
This doesn't seem to effect functionality of the touchpad.

When using the touchpad, this gets printed in dmesg once an a while: ``` elan_i2c 4-0015: invalid report id data (ff) ``` One of the untested patches seems to fix this issue, further testing required. This doesn't seem to effect functionality of the touchpad.

👍 1

SolidEva commented

2018-10-10 17:22:56 +02:00

(Migrated from github.com)

Try disabling i2c 4 in the device tree files?

SolidEva commented

2019-06-08 00:36:01 +02:00

(Migrated from github.com)

with any of the I2C debug config settings, the invalid reports stop occuring. This suggests to me a timing issue, maybe a race condition?

These are the usual debug messages with just CONFIG_I2C_DEBUG_CORE=y enabeld

[   35.029021] i2c i2c-0: master_xfer[0] W, addr=0x1b, len=2

with any of the I2C debug config settings, the invalid reports stop occuring. This suggests to me a timing issue, maybe a race condition? These are the usual debug messages with just `CONFIG_I2C_DEBUG_CORE=y` enabeld ``` [ 35.029021] i2c i2c-0: master_xfer[0] W, addr=0x1b, len=2 ```