From: Barry Song <21cnbao@gmail.com>
To: "linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: DL-SHA-WorkGroupLinux <workgroup.linux@csr.com>, Andy.Sun@csr.com
Subject: [RFC PATCH] Input: gpio_keys - trigger input event if key is pressed in boot stage
Date: Wed, 20 May 2015 18:02:36 +0800 [thread overview]
Message-ID: <CAGsJ_4z-CZShfCQ2JNgOKX1dtfGksX+Naj++4tugPCriiY=ESg@mail.gmail.com> (raw)
sometimes we press a key to boot, and the boot stage need to get this
event.
the current codes use edge trigger, so we have no chance to report
the cold-touch event.
but our user sceneries like Linux navigator does need it.
Signed-off-by: Barry Song <Baohua.Song@csr.com>
---
-RFC: for the moment, only an idea
drivers/input/keyboard/gpio_keys.c | 13 +++++++++++++
1 file changed, 13 insertions(+)
diff --git a/drivers/input/keyboard/gpio_keys.c
b/drivers/input/keyboard/gpio_keys.c
index ddf4045..77fe0dd 100644
--- a/drivers/input/keyboard/gpio_keys.c
+++ b/drivers/input/keyboard/gpio_keys.c
@@ -766,6 +766,19 @@ static int gpio_keys_probe(struct platform_device *pdev)
device_init_wakeup(&pdev->dev, wakeup);
+ /* if the key is pressed while system boot, force an interrupt */
+ for (i = 0; i < pdata->nbuttons; i++) {
+ const struct gpio_keys_button *button = &pdata->buttons[i];
+ struct gpio_button_data *bdata = &ddata->data[i];
+ int state;
+
+ if (gpio_is_valid(button->gpio)) {
+ state = (gpio_get_value_cansleep(button->gpio) ? 1 : 0) ^
button->active_low;
+ if (state)
+ gpio_keys_gpio_isr(bdata->irq, bdata);
+ }
+ }
+
return 0;
err_remove_group:
--
1.9.1
next reply other threads:[~2015-05-20 10:02 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-05-20 10:02 Barry Song [this message]
2015-05-20 16:37 ` [RFC PATCH] Input: gpio_keys - trigger input event if key is pressed in boot stage Dmitry Torokhov
2015-05-20 22:44 ` Barry Song
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='CAGsJ_4z-CZShfCQ2JNgOKX1dtfGksX+Naj++4tugPCriiY=ESg@mail.gmail.com' \
--to=21cnbao@gmail.com \
--cc=Andy.Sun@csr.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=workgroup.linux@csr.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).