From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Alexander Babayants <babayants.alexander@gmail.com>
Cc: linux-input@vger.kernel.org
Subject: Re: PROBLEM: atkbd: Incorrect (?) handling of BAT from laptop PS/2 keyboard
Date: Sun, 2 Jul 2017 13:25:35 -0700 [thread overview]
Message-ID: <20170702202535.GA3935@dtor-ws> (raw)
In-Reply-To: <CAB92dJZtxT2+CqKyNjW5NuE8wWvXVmKknt5muHZdbucXXRMT5A@mail.gmail.com>
Hi Alexander,
On Sun, Jul 02, 2017 at 04:32:18AM +0300, Alexander Babayants wrote:
> Hi,
>
> HP Pavilion 15 keyboard controller sometimes (as far as I've found, at
> least after keyboard (re-)connection and LED status change) emits 0xAA
> scancode (BAT passed) and key-up events for LCtrl, LAlt, RCtrl, RAlt,
> RShift. This, in turn, causes the keyboard to reconnect
> (drivers/input/keyboard/atkbd.c, line 424) and to emit 0xAA scancode again,
> which results in keyboard being stuck in endless loop of reconnecting.
> While in this loop, keyboard is usable, but some keystrokes are being
> occasionally dropped.
> Is it necessary to handle BAT scancode in such particular way? Couldn't it
> just be ignored?
We should not ignore BAT, as it normally indicates that the keyboard
lost its state and we need to re-initialize it (update LED state to be
in sync with the keyboard state, set up repeat rate, select proper set -
2 or 3, etc).
I would be interesting to see the command stream there. Can you try
booting with i8042.debug and reproducing the issue?
Thanks.
--
Dmitry
next parent reply other threads:[~2017-07-02 20:25 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CAB92dJZtxT2+CqKyNjW5NuE8wWvXVmKknt5muHZdbucXXRMT5A@mail.gmail.com>
2017-07-02 20:25 ` Dmitry Torokhov [this message]
2017-07-04 11:31 ` PROBLEM: atkbd: Incorrect (?) handling of BAT from laptop PS/2 keyboard Alexander Babayants
2017-07-02 1:37 Alexander Babayants
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=20170702202535.GA3935@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=babayants.alexander@gmail.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).