From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Brian Norris <briannorris@chromium.org>
Cc: Enric Balletbo i Serra <enric.balletbo@collabora.co.uk>,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
Doug Anderson <dianders@chromium.org>
Subject: Re: [PATCH] input: cros_ec_keyb: fix button/switch capability reports
Date: Mon, 12 Nov 2018 11:24:20 -0800 [thread overview]
Message-ID: <20181112192420.GC192687@dtor-ws> (raw)
In-Reply-To: <20181107223813.178462-1-briannorris@chromium.org>
On Wed, Nov 07, 2018 at 02:38:13PM -0800, Brian Norris wrote:
> The cros_ec_keyb_bs array lists buttons and switches together, expecting
> that its users will match the appropriate type and bit fields. But
> cros_ec_keyb_register_bs() only checks the 'bit' field, which causes
> misreported input capabilities in some cases. For example, tablets
> (e.g., Scarlet -- a.k.a. Acer Chromebook Tab 10) were reporting a SW_LID
> capability, because EC_MKBP_POWER_BUTTON and EC_MKBP_LID_OPEN happen to
> share the same bit.
>
> (This has comedic effect on a tablet, in which a power-management daemon
> then thinks this "lid" is closed, and so puts the system to sleep as
> soon as it boots!)
>
> To fix this, check both the 'ev_type' and 'bit' fields before reporting
> the capability.
>
> Tested with a lid (Kevin / Samsung Chromebook Plus) and without a lid
> (Scarlet / Acer Chromebook Tab 10).
>
> This error got introduced when porting the feature from the downstream
> Chromium OS kernel to be upstreamed.
>
> Fixes: cdd7950e7aa4 ("input: cros_ec_keyb: Add non-matrix buttons and switches")
> Cc: <stable@vger.kernel.org>
> Cc: Douglas Anderson <dianders@chromium.org>
> Cc: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> Signed-off-by: Brian Norris <briannorris@chromium.org>
Applied, thank you.
> ---
> drivers/input/keyboard/cros_ec_keyb.c | 3 ++-
> 1 file changed, 2 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/keyboard/cros_ec_keyb.c b/drivers/input/keyboard/cros_ec_keyb.c
> index 81be6f781f0b..d56001181598 100644
> --- a/drivers/input/keyboard/cros_ec_keyb.c
> +++ b/drivers/input/keyboard/cros_ec_keyb.c
> @@ -493,7 +493,8 @@ static int cros_ec_keyb_register_bs(struct cros_ec_keyb *ckdev)
> for (i = 0; i < ARRAY_SIZE(cros_ec_keyb_bs); i++) {
> const struct cros_ec_bs_map *map = &cros_ec_keyb_bs[i];
>
> - if (buttons & BIT(map->bit))
> + if ((map->ev_type == EV_KEY && (buttons & BIT(map->bit))) ||
> + (map->ev_type == EV_SW && (switches & BIT(map->bit))))
> input_set_capability(idev, map->ev_type, map->code);
> }
>
> --
> 2.19.1.930.g4563a0d9d0-goog
>
--
Dmitry
next prev parent reply other threads:[~2018-11-12 19:24 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2018-11-07 22:38 [PATCH] input: cros_ec_keyb: fix button/switch capability reports Brian Norris
2018-11-08 8:55 ` Heiko Stuebner
2018-11-12 19:24 ` Dmitry Torokhov [this message]
-- strict thread matches above, loose matches on Subject: below --
2018-11-07 22:27 Brian Norris
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=20181112192420.GC192687@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=briannorris@chromium.org \
--cc=dianders@chromium.org \
--cc=enric.balletbo@collabora.co.uk \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@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).