From: Werner Sembach <wse@tuxedocomputers.com>
To: dmitry.torokhov@gmail.com, swboyd@chromium.org,
gregkh@linuxfoundation.org, hdegoede@redhat.com,
mkorpershoek@baylibre.com, chenhuacai@kernel.org,
wsa+renesas@sang-engineering.com, tiwai@suse.de,
linux-input@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 0/2] Fix "Input: i8042 - add TUXEDO devices to i8042 quirk tables for partial fix"
Date: Wed, 1 Mar 2023 17:57:44 +0100 [thread overview]
Message-ID: <192c2eab-3b57-8a09-dfd7-5720b2b419b8@tuxedocomputers.com> (raw)
In-Reply-To: <20230227185907.569154-1-wse@tuxedocomputers.com>
Am 27.02.23 um 19:59 schrieb Werner Sembach:
> This is a continuation of
> https://lore.kernel.org/linux-input/20220708161005.1251929-3-wse@tuxedocomputers.com/
>
> That fix did fix the keyboard not responding at all sometimes after resume,
> but at the price of it being laggy for some time after boot. Additionally
> setting atkbd.reset removes that lag.
>
> This patch comes in 2 parts: The first one adds a quirk to atkbd to set
> atkbd.reset and the second one then applies that and the i8042 quirks to
> the affected devices.
>
>
Somehow, for my testing last week these patches seemed work, but now i still see
occasional laggy keyboard after boot. So sadly the atkbd_reset quirk didn't fix
the issue after all.
next prev parent reply other threads:[~2023-03-01 16:57 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-27 18:59 Werner Sembach
2023-02-27 18:59 ` [PATCH v2 1/2] Input: atkbd - Make it possible to apply atkbd.reset via kernel quirk Werner Sembach
2023-02-28 7:34 ` Greg KH
2023-02-28 10:58 ` Werner Sembach
2023-02-27 18:59 ` [PATCH v2 2/2] Input: i8042 - add 2 more TUXEDO devices to i8042 and atkbd quirk tables Werner Sembach
2023-02-28 8:41 ` [PATCH v2 0/2] Fix "Input: i8042 - add TUXEDO devices to i8042 quirk tables for partial fix" Hans de Goede
2023-02-28 11:07 ` Werner Sembach
2023-03-01 16:57 ` Werner Sembach [this message]
2023-03-01 17:52 ` Hans de Goede
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=192c2eab-3b57-8a09-dfd7-5720b2b419b8@tuxedocomputers.com \
--to=wse@tuxedocomputers.com \
--cc=chenhuacai@kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=gregkh@linuxfoundation.org \
--cc=hdegoede@redhat.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mkorpershoek@baylibre.com \
--cc=swboyd@chromium.org \
--cc=tiwai@suse.de \
--cc=wsa+renesas@sang-engineering.com \
/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
all inboxes | Powered by JetHome®