All of lore.kernel.org
 help / color / mirror / Atom feed
From: "Michał Kępień" <kernel@kempniu.pl>
To: "Pali Rohár" <pali.rohar@gmail.com>
Cc: Darren Hart <dvhart@infradead.org>,
	Alex Hung <alex.hung@canonical.com>,
	platform-driver-x86@vger.kernel.org
Subject: Re: [PATCH][V2] intel-hid: support 5 array button
Date: Wed, 8 Feb 2017 08:21:46 +0100	[thread overview]
Message-ID: <20170208072146.GA1199@ozzy.nask.waw.pl> (raw)
In-Reply-To: <20170204160653.GA27398@pali>

> Hi!
> 
> On Saturday 04 February 2017 02:26:05 Darren Hart wrote:
> > Apologies, this time with Pali's correct email address (aliases fail).
> > 
> ...
> > > 
> > > Pali, would you care to offer a review or some testing to verify no unexpected
> > > conflicts with the other dell drivers?
> 
> I do not have Dell machine which uses intel-hid.ko so I cannot test this
> patch. And obviously as it is not loaded it cannot break machines which
> do not use intel-hid.ko.
> 
> > > > +/* 5 button array notification value. */
> > > > +static const struct key_entry intel_array_keymap[] = {
> > > > +	{ KE_KEY,    0xC2, { KEY_LEFTMETA} },                /* Press */
> > > > +	{ KE_IGNORE, 0xC3, { KEY_LEFTMETA} },                /* Release */
> > > > +	{ KE_KEY,    0xC4, { KEY_VOLUMEUP} },                /* Press */
> > > > +	{ KE_IGNORE, 0xC5, { KEY_VOLUMEUP} },                /* Release */
> > > > +	{ KE_KEY,    0xC6, { KEY_VOLUMEDOWN} },              /* Press */
> > > > +	{ KE_IGNORE, 0xC7, { KEY_VOLUMEDOWN} },	             /* Release */
> > > > +	{ KE_SW,     0xC8, { .sw = {SW_ROTATE_LOCK, 1} } },   /* Press */
> > > > +	{ KE_SW,     0xC9, { .sw = {SW_ROTATE_LOCK, 0} } },   /* Release */
> > > > +	{ KE_KEY,    0xCE, { KEY_POWER} },                   /* Press */
> > > > +	{ KE_IGNORE, 0xCF, { KEY_POWER} },                   /* Release */
> > > > +	{ KE_END },
> > > > +};
> 
> This looks suspicious. Why are all release events ignored?

I also do not have a Dell machine that makes use of this driver, but my
understanding is that calling sparse_keymap_report_event() with
autorelease set to true makes release events irrelevant and simplifies
implementation.  Though each release event still needs a KE_IGNORE entry
in the keymap so that superfluous KEY_UNKNOWN events are suppressed.

-- 
Best regards,
Michał Kępień

  reply	other threads:[~2017-02-08  7:29 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2017-01-26  7:33 [PATCH][V2] intel-hid: support 5 array button Alex Hung
2017-01-27 14:16 ` Michał Kępień
2017-02-04  1:14 ` Darren Hart
2017-02-04  1:26   ` Darren Hart
2017-02-04 16:06     ` Pali Rohár
2017-02-08  7:21       ` Michał Kępień [this message]
2017-02-08  8:17         ` Pali Rohár
2017-02-08  9:05           ` Alex Hung
2017-02-08  9:07             ` Pali Rohár
2017-02-04 14:58   ` Andy Shevchenko
2017-02-09  2:22     ` Darren Hart
2017-02-09  3:09       ` Alex Hung
2017-02-09 19:56         ` Andy Shevchenko
2017-02-17  2:43           ` Darren Hart
2017-02-08  8:54   ` Alex Hung
2017-02-13 11:43     ` Michał Kępień
2017-02-13 23:23       ` Andy Shevchenko
2017-02-14  0:06         ` Alex Hung

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=20170208072146.GA1199@ozzy.nask.waw.pl \
    --to=kernel@kempniu.pl \
    --cc=alex.hung@canonical.com \
    --cc=dvhart@infradead.org \
    --cc=pali.rohar@gmail.com \
    --cc=platform-driver-x86@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 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.