From: Mike Murdoch <main.haarp@gmail.com>
To: linux-input@vger.kernel.org
Cc: benjamin.tissoires@redhat.com
Subject: High CPU usage on RMI4 interrupt with Synaptics touchpad
Date: Thu, 9 Jan 2020 23:37:37 +0100 [thread overview]
Message-ID: <fb009d40-13f9-fc20-1186-77b60eac244a@gmail.com> (raw)
Greetings,
I'm running kernel 5.4.7 on a recently acquired a Lenovo Thinkpad X1
Extreme Gen 2. It has a Synaptics touchpad and a Elan trackpoint being
passed through.
When the psmouse module loads normally, I get a message indicating it
can support a different bus:
psmouse serio1: synaptics: Your touchpad (PNP: LEN0402 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@vger.kernel.org.
Upon reloading the module with synaptics_intertouch=1, the touchpad and
trackpoint return, here's the kernel log:
rmi4_smbus 5-002c: registering SMbus-connected sensor
rmi4_f34 rmi4-02.fn34: rmi_f34v7_probe: Unrecognized bootloader version
rmi4_f34: probe of rmi4-02.fn34 failed with error -22
rmi4_f01 rmi4-02.fn01: found RMI device, manufacturer: Synaptics,
product: TM3512-010, fw id: 2956703
input: Synaptics TM3512-010 as /devices/rmi4-02/input/input41
serio: RMI4 PS/2 pass-through port at rmi4-02.fn03
psmouse serio6: trackpoint: Elan TrackPoint firmware: 0x11, buttons: 3/3
input: TPPS/2 Elan TrackPoint as
/devices/rmi4-02/rmi4-02.fn03/serio6/input/input42
However I notice that cursor movement with the touchpad is now quite
choppy and causes a LOT of CPU usage on irq/165-rmi4_sm. Clearly
something is not working as intended. Curiously, I think I managed to
get RMI4 to work properly *once*, but cannot reproduce it anymore. Might
have been a fluke or my imagination too...
I'll be glad to help figure this out.
Thanks and best regards,
- Mike
reply other threads:[~2020-01-09 22:37 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=fb009d40-13f9-fc20-1186-77b60eac244a@gmail.com \
--to=main.haarp@gmail.com \
--cc=benjamin.tissoires@redhat.com \
--cc=linux-input@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).