From: "Pali Rohár" <pali.rohar@gmail.com>
To: Andrei Antonov <polymorphm@gmail.com>
Cc: "Matthew Garrett" <mjg59@srcf.ucam.org>,
platform-driver-x86@vger.kernel.org,
" мастер инструкции о том как отсылать патчи в ядро ( если что
то виним во всём этого парня)" <i.gnatenko.brain@gmail.com>
Subject: Re: [PATCH] module 'dell-laptop': quirk for laptop Dell Inspiron 3179: problem with keyboard controller for keys: Home, End, PgUp, PgDn
Date: Sat, 7 Jan 2017 22:21:42 +0100 [thread overview]
Message-ID: <201701072221.42852@pali> (raw)
In-Reply-To: <20170107205240.11836-1-polymorphm@gmail.com>
[-- Attachment #1: Type: Text/Plain, Size: 865 bytes --]
On Saturday 07 January 2017 21:52:40 Andrei Antonov wrote:
> + /*
> + * kbd_missing_release_interrupts=1 means bug in keyboard
> controller for additional keys: + * Home, End, PgUp, PgDn. These
> four keys only -- from all keyboard. + * These keys does not send
> key-release interrupts (send key-press interrupts only). + *
> kbd_missing_release_interrupts=<...> (!=0) -- for other variations
> of similar issues + */
NACK. There is "no new force-release quirks" policy in linux kernel.
https://git.kernel.org/cgit/linux/kernel/git/torvalds/linux.git/commit/?id=8b8a518ef16be2de27207991e32fc32b0475c767
"force release" quirks are handled by userspace e.g. by udev rule. There
is hwdb database where can be put DMI of problematic/broken machines
together with keys which should be force-released.
--
Pali Rohár
pali.rohar@gmail.com
[-- Attachment #2: This is a digitally signed message part. --]
[-- Type: application/pgp-signature, Size: 198 bytes --]
prev parent reply other threads:[~2017-01-07 21:21 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <20170107205240.11836-1-polymorphm@gmail.com>
2017-01-07 21:16 ` [PATCH] module 'dell-laptop': quirk for laptop Dell Inspiron 3179: problem with keyboard controller for keys: Home, End, PgUp, PgDn Matthew Garrett
2017-01-07 21:21 ` Pali Rohár [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=201701072221.42852@pali \
--to=pali.rohar@gmail.com \
--cc=i.gnatenko.brain@gmail.com \
--cc=mjg59@srcf.ucam.org \
--cc=platform-driver-x86@vger.kernel.org \
--cc=polymorphm@gmail.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 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.