From: Jiri Kosina <jikos@kernel.org>
To: Hans de Goede <hdegoede@redhat.com>
Cc: Benjamin Tissoires <benjamin.tissoires@redhat.com>,
linux-input@vger.kernel.org
Subject: Re: [PATCH 2/3] HID: multitouch: Disable event reporting on suspend on the Asus T101HA touchpad
Date: Thu, 13 May 2021 12:34:00 +0200 (CEST) [thread overview]
Message-ID: <nycvar.YFH.7.76.2105131233500.28378@cbobk.fhfr.pm> (raw)
In-Reply-To: <20210306133716.453447-2-hdegoede@redhat.com>
On Sat, 6 Mar 2021, Hans de Goede wrote:
> The Asus T101HA has a problem with spurious wakeups when the lid is
> closed, this is caused by the screen sitting so close to the touchpad
> that the touchpad ends up reporting touch events, causing these wakeups.
>
> Add a quirk which disables event reporting on suspend when set, and
> enable this quirk for the Asus T101HA touchpad fixing the spurious
> wakeups, while still allowing the device to be woken by pressing a
> key on the keyboard (which is part of the same USB device).
This one also applied to for-5.13/upstream-fixes. Thanks,
--
Jiri Kosina
SUSE Labs
next prev parent reply other threads:[~2021-05-13 10:34 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-03-06 13:37 [PATCH 1/3] HID: asus: Cleanup Asus T101HA keyboard-dock handling Hans de Goede
2021-03-06 13:37 ` [PATCH 2/3] HID: multitouch: Disable event reporting on suspend on the Asus T101HA touchpad Hans de Goede
2021-05-13 10:34 ` Jiri Kosina [this message]
2021-03-06 13:37 ` [PATCH 3/3] HID: multitouch: Disable event reporting on suspend when our parent is not a wakeup-source Hans de Goede
2021-05-05 13:40 ` Benjamin Tissoires
2021-05-05 13:59 ` Hans de Goede
2021-05-05 14:09 ` Benjamin Tissoires
2021-03-31 9:41 ` [PATCH 1/3] HID: asus: Cleanup Asus T101HA keyboard-dock handling Jiri Kosina
2021-05-05 12:24 ` Jiri Kosina
2021-05-05 13:36 ` Benjamin Tissoires
2021-05-13 10:33 ` Jiri Kosina
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=nycvar.YFH.7.76.2105131233500.28378@cbobk.fhfr.pm \
--to=jikos@kernel.org \
--cc=benjamin.tissoires@redhat.com \
--cc=hdegoede@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.