From: Mario Limonciello <mario_limonciello@dell.com>
To: "Dmitry Torokhov" <dmitry.torokhov@gmail.com>,
"Pali Rohár" <pali.rohar@gmail.com>
Cc: LKML <linux-kernel@vger.kernel.org>,
"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Rob <robr.bensson@gmail.com>
Subject: Re: [PATCH] Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode.
Date: Wed, 25 Feb 2015 12:26:18 -0600 [thread overview]
Message-ID: <54EE13CA.1090101@dell.com> (raw)
In-Reply-To: <20150224005109.GD604@dtor-glaptop>
On 02/23/2015 06:51 PM, Dmitry Torokhov wrote:
> On Sun, Feb 22, 2015 at 05:55:05PM +0100, Pali Rohár wrote:
> I am not sure what exactly the issue is... We do need to have the break
> code to know when the key is released. We can't go and say that we will
> release old key when we detect another key press as that would mess up
> key combination handling (like control, meta, etc).
>
> What does Windows driver do?
>
> Thanks.
>
To me it sounds like the Windows driver understands a situation that there are a bunch of key down events without a keyup event until you lift your finger rather than expecting a pair every time.
https://msdn.microsoft.com/en-us/library/windows/desktop/ms646267(v=vs.85).aspx
next prev parent reply other threads:[~2015-02-25 18:26 UTC|newest]
Thread overview: 37+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-02-19 1:43 [PATCH] Add a quirk for the Dell XPS 13 (2015) when in PS/2 mode Mario Limonciello
2015-02-19 17:16 ` Dmitry Torokhov
2015-02-19 18:16 ` Mario Limonciello
2015-02-20 18:47 ` Dmitry Torokhov
2015-02-20 19:24 ` Pali Rohár
2015-02-20 19:56 ` Mario Limonciello
2015-02-20 20:41 ` Pali Rohár
2015-02-20 21:21 ` Mario Limonciello
2015-02-20 21:31 ` Benjamin Tissoires
2015-02-20 21:40 ` Mario Limonciello
2015-02-20 21:46 ` Pali Rohár
2015-02-20 21:54 ` Mario Limonciello
2015-02-22 16:55 ` Pali Rohár
2015-02-23 23:31 ` Mario Limonciello
2015-02-24 0:01 ` Pali Rohár
2015-02-25 18:16 ` [SUSPECT SPAM] " Mario Limonciello
2015-02-24 0:51 ` Dmitry Torokhov
2015-02-25 18:26 ` Mario Limonciello [this message]
2015-02-25 18:48 ` Mario Limonciello
2015-02-25 20:45 ` Pali Rohár
2015-03-14 19:17 ` Benjamin Tissoires
2015-03-16 14:29 ` Mario Limonciello
2015-03-16 14:40 ` Benjamin Tissoires
2015-03-16 17:10 ` Jason Ekstrand
2015-03-16 18:50 ` Mario Limonciello
2015-03-16 20:42 ` Jason Ekstrand
2015-03-16 20:50 ` Mario Limonciello
2015-03-16 20:57 ` Jason Ekstrand
2015-03-16 21:07 ` Benjamin Tissoires
2015-03-17 0:45 ` Mario Limonciello
2015-04-10 22:39 ` Pali Rohár
2015-04-10 23:07 ` Mario Limonciello
2015-04-10 23:14 ` Pali Rohár
2015-04-10 23:32 ` Mario Limonciello
2015-04-11 2:19 ` Ben Gamari
2015-04-13 18:55 ` Mario Limonciello
2015-03-21 17:21 ` Ben Gamari
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=54EE13CA.1090101@dell.com \
--to=mario_limonciello@dell.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pali.rohar@gmail.com \
--cc=robr.bensson@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 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).