From: Werner Sembach <wse@tuxedocomputers.com>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Hans de Goede <hdegoede@redhat.com>
Subject: Re: [PATCH 2/2] i8042: Use new forenorestore quirk to replace old buggy quirk combination
Date: Tue, 2 Jan 2024 15:08:11 +0100 [thread overview]
Message-ID: <19a39ca1-ca72-4ee1-96e9-c55541e67aa4@tuxedocomputers.com> (raw)
In-Reply-To: <20240102134833.68646-2-wse@tuxedocomputers.com>
Hi,
Am 02.01.24 um 14:48 schrieb Werner Sembach:
> The old quirk combination sometimes cause a laggy keyboard after boot. With
> the new quirk the initial issue of an unresponsive keyboard after s3 resume
> is also fixed, but it doesn't have the negative side effect of the
> sometimes laggy keyboard.
>
> Signed-off-by: Werner Sembach <wse@tuxedocomputers.com>
> Cc: stable@vger.kernel.org
Added Hans to the loop.
As mentioned in the one on one e-Mails with Hans I wrote a new quirk in [Patch
1/2] and tested it on the device in [Patch 2/2]
At least one more device will follow which has negative side effects with the
old quirkls, but I currently don't have it at hand for testing.
I wonder if devices where the old quirk combination did not cause issue should
also be switched to the new quirk, if, after testing, it also fixes the
unresponsive keyboard issues?
Kind regards,
Werner
prev parent reply other threads:[~2024-01-02 14:08 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-02 13:48 [PATCH 1/2] i8042: Add forcenorestore quirk to leave controller untouched even on s3 Werner Sembach
2024-01-02 13:48 ` [PATCH 2/2] i8042: Use new forenorestore quirk to replace old buggy quirk combination Werner Sembach
2024-01-02 14:08 ` Werner Sembach [this message]
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=19a39ca1-ca72-4ee1-96e9-c55541e67aa4@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=dmitry.torokhov@gmail.com \
--cc=hdegoede@redhat.com \
--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