All of lore.kernel.org
 help / color / mirror / Atom feed
From: Werner Sembach <wse@tuxedocomputers.com>
To: dmitry.torokhov@gmail.com, hdegoede@redhat.com, tiwai@suse.de,
	samuel@cavoj.net, linux-input@vger.kernel.org,
	linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] Input: i8042 - add additional TUXEDO devices to i8042 quirk tables
Date: Fri,  8 Jul 2022 18:10:03 +0200	[thread overview]
Message-ID: <20220708161005.1251929-1-wse@tuxedocomputers.com> (raw)

Some additional devices needing i8042 quirks for the keyboard to reliably
work after boot and suspend. The first patch are some older devices I found
needing the quirks in our install routine.

The second patch are two devices that I purposly seperated in an own patch,
because it is not clear cut if these should be applied or not:
They need the quirks for the keyboard to not be completly dead by chance
after suspend. However setting the quirk causes the keyboard to lag for the
first few seconds after every boot and sometimes also a little bit after
resume, giving double inputs or missing keystrokes. However this very
quickly goes away again.
Imho the lag issue is less severe then an occasionally completly dead
keyboard. However I'm interested in other opinions. A counter argument is
that the quirks can always be set via boot parameter, but not unset when
they are part of the quirk list.



             reply	other threads:[~2022-07-08 16:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08 16:10 Werner Sembach [this message]
2022-07-08 16:10 ` [PATCH 1/2] Input: i8042 - add additional TUXEDO devices to i8042 quirk tables Werner Sembach
2022-07-08 19:38   ` Hans de Goede
2022-07-08 20:20   ` Dmitry Torokhov
2022-07-08 16:10 ` [PATCH 2/2] Input: i8042 - add TUXEDO devices to i8042 quirk tables for partial fix Werner Sembach
2022-07-08 19:39   ` Hans de Goede
2022-07-11 12:45     ` Werner Sembach
2022-07-11 12:55       ` Hans de Goede
2023-03-21 16:10         ` Werner Sembach
2023-03-21 18:53           ` Dmitry Torokhov
2023-03-21 19:18             ` Werner Sembach

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=20220708161005.1251929-1-wse@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 \
    --cc=samuel@cavoj.net \
    --cc=tiwai@suse.de \
    /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.