From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Enric Balletbo i Serra <enric.balletbo@collabora.com>
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
Phil Blundell <pb@handhelds.org>,
groeck@chromium.org, Joseph Lo <josephl@nvidia.com>
Subject: Re: [PATCH RESEND] input: gpio_keys: handle the missing key press event in resume phase
Date: Sun, 2 Jul 2017 13:39:48 -0700 [thread overview]
Message-ID: <20170702203948.GB3935@dtor-ws> (raw)
In-Reply-To: <20170628102940.15670-1-enric.balletbo@collabora.com>
On Wed, Jun 28, 2017 at 12:29:40PM +0200, Enric Balletbo i Serra wrote:
> From: Joseph Lo <josephl@nvidia.com>
>
> The GPIO key press event might be missed in the resume phase, if the key
> had been released before the system had been resumed to the stage that it
> could capture the press event. So we simulate the wakeup key press event
> in case the key had been released by the time we got interrupt handler
> to run.
>
> Signed-off-by: Joseph Lo <josephl@nvidia.com>
> Signed-off-by: Enric Balletbo i Serra <enric.balletbo@collabora.com>
> ---
> This patch was sent long time ago [1] but apparently did not receive feedback
> and seems that nobody take care of it. I think might be interesting have this
> upstream so I resend this version just rebased on top of mainline and tested
> on a veyron device.
Applied, thank you.
>
> [1] https://patchwork.kernel.org/patch/7157201/
>
> drivers/input/keyboard/gpio_keys.c | 17 ++++++++++++++++-
> 1 file changed, 16 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/keyboard/gpio_keys.c b/drivers/input/keyboard/gpio_keys.c
> index da3d362..a047b9a 100644
> --- a/drivers/input/keyboard/gpio_keys.c
> +++ b/drivers/input/keyboard/gpio_keys.c
> @@ -48,6 +48,7 @@ struct gpio_button_data {
> spinlock_t lock;
> bool disabled;
> bool key_pressed;
> + bool suspended;
> };
>
> struct gpio_keys_drvdata {
> @@ -396,8 +397,20 @@ static irqreturn_t gpio_keys_gpio_isr(int irq, void *dev_id)
>
> BUG_ON(irq != bdata->irq);
>
> - if (bdata->button->wakeup)
> + if (bdata->button->wakeup) {
> + const struct gpio_keys_button *button = bdata->button;
> +
> pm_stay_awake(bdata->input->dev.parent);
> + if (bdata->suspended &&
> + (button->type == 0 || button->type == EV_KEY)) {
> + /*
> + * Simulate wakeup key press in case the key has
> + * already released by the time we got interrupt
> + * handler to run.
> + */
> + input_report_key(bdata->input, button->code, 1);
> + }
> + }
>
> mod_delayed_work(system_wq,
> &bdata->work,
> @@ -855,6 +868,7 @@ static int __maybe_unused gpio_keys_suspend(struct device *dev)
> struct gpio_button_data *bdata = &ddata->data[i];
> if (bdata->button->wakeup)
> enable_irq_wake(bdata->irq);
> + bdata->suspended = true;
> }
> } else {
> mutex_lock(&input->mutex);
> @@ -878,6 +892,7 @@ static int __maybe_unused gpio_keys_resume(struct device *dev)
> struct gpio_button_data *bdata = &ddata->data[i];
> if (bdata->button->wakeup)
> disable_irq_wake(bdata->irq);
> + bdata->suspended = false;
> }
> } else {
> mutex_lock(&input->mutex);
> --
> 2.9.3
>
--
Dmitry
prev parent reply other threads:[~2017-07-02 20:39 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-06-28 10:29 [PATCH RESEND] input: gpio_keys: handle the missing key press event in resume phase Enric Balletbo i Serra
2017-07-02 20:39 ` Dmitry Torokhov [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=20170702203948.GB3935@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=enric.balletbo@collabora.com \
--cc=groeck@chromium.org \
--cc=josephl@nvidia.com \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=pb@handhelds.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