From: Kai Heng Feng <kai.heng.feng@canonical.com>
To: Jiri Kosina <jikos@kernel.org>
Cc: benjamin.tissoires@redhat.com, linux-input@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] HID: i2c-hid: Disable runtime PM on Goodix touchpad
Date: Wed, 16 Jan 2019 16:21:21 +0800 [thread overview]
Message-ID: <663EE74C-02E8-49DB-A197-2022AFE2D863@canonical.com> (raw)
In-Reply-To: <nycvar.YFH.7.76.1901141217550.6626@cbobk.fhfr.pm>
> On Jan 14, 2019, at 19:18, Jiri Kosina <jikos@kernel.org> wrote:
>
> On Mon, 14 Jan 2019, Kai-Heng Feng wrote:
>
>> A Goodix touchpad doesn't work. Touching the touchpad can trigger IRQ
>> but there's no input event from HID subsystem.
>>
>> Turns out it reports some invalid data:
>> [ 22.136630] i2c_hid i2c-DELL091F:00: input: 0b 00 01 00 00 00 00 00 00 00 00
>>
>> After some trial and error, it's another device that doesn't work well
>> with ON/SLEEP commands. Disable runtime PM to fix the issue.
>
> Thanks, I've now applied the patch to for-5.0/upstream-fixes. I am
> wondering though we are we seeing these at all - do other OSes not do the
> runtime PM on i2c at all?
According to the vendor, Windows does use ON/SLEEP, but infrequently.
We can use pm_runtime_use_autosuspend() to reduce the frequency of
ON/SLEEP commands, but it’s just papering over the touchpad firmware
bug.
Kai-Heng
>
> --
> Jiri Kosina
> SUSE Labs
>
next prev parent reply other threads:[~2019-01-16 8:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-01-14 8:47 [PATCH] HID: i2c-hid: Disable runtime PM on Goodix touchpad Kai-Heng Feng
2019-01-14 11:18 ` Jiri Kosina
2019-01-16 8:21 ` Kai Heng Feng [this message]
2019-01-17 5:02 ` Kai-Heng Feng
2019-01-17 8:06 ` Benjamin Tissoires
2019-01-17 11:41 ` Kai-Heng Feng
2019-01-17 12:35 ` Benjamin Tissoires
2019-01-21 3:23 ` Kai-Heng Feng
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=663EE74C-02E8-49DB-A197-2022AFE2D863@canonical.com \
--to=kai.heng.feng@canonical.com \
--cc=benjamin.tissoires@redhat.com \
--cc=jikos@kernel.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).