From: Laxman Dewangan <ldewangan@nvidia.com>
To: robh+dt@kernel.org, dmitry.torokhov@gmail.com
Cc: pawel.moll@arm.com, mark.rutland@arm.com,
ijc+devicetree@hellion.org.uk, galak@codeaurora.org,
linus.walleij@linaro.org, bjorn.andersson@sonymobile.com,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
linux-input@vger.kernel.org,
Laxman Dewangan <ldewangan@nvidia.com>
Subject: [PATCH 2/2] input: gpio-keys: add support to name the gpio-keys
Date: Tue, 12 Jan 2016 17:02:50 +0530 [thread overview]
Message-ID: <1452598370-28509-2-git-send-email-ldewangan@nvidia.com> (raw)
In-Reply-To: <1452598370-28509-1-git-send-email-ldewangan@nvidia.com>
Add support from DT to name the gpio-keys driver to have
desired key name for this input system.
This helps userspace code to get name and perform proper
event to key mapping in some of cases. In android, the
user space map the key code to application code using
key character layout and for this it uses the name of
input system.
Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
---
Documentation/devicetree/bindings/input/gpio-keys.txt | 1 +
drivers/input/keyboard/gpio_keys.c | 2 ++
2 files changed, 3 insertions(+)
diff --git a/Documentation/devicetree/bindings/input/gpio-keys.txt b/Documentation/devicetree/bindings/input/gpio-keys.txt
index cf1333d..2e6bcd2 100644
--- a/Documentation/devicetree/bindings/input/gpio-keys.txt
+++ b/Documentation/devicetree/bindings/input/gpio-keys.txt
@@ -4,6 +4,7 @@ Required properties:
- compatible = "gpio-keys";
Optional properties:
+ - gpio-keys,name: String, name of the gpio-keys input system.
- autorepeat: Boolean, Enable auto repeat feature of Linux input
subsystem.
diff --git a/drivers/input/keyboard/gpio_keys.c b/drivers/input/keyboard/gpio_keys.c
index cf068cb..c95dc3b 100644
--- a/drivers/input/keyboard/gpio_keys.c
+++ b/drivers/input/keyboard/gpio_keys.c
@@ -628,6 +628,8 @@ gpio_keys_get_devtree_pdata(struct device *dev)
pdata->rep = !!of_get_property(node, "autorepeat", NULL);
+ of_property_read_string(node, "gpio-keys,name", &pdata->name);
+
i = 0;
for_each_child_of_node(node, pp) {
enum of_gpio_flags flags;
--
2.1.4
next prev parent reply other threads:[~2016-01-12 11:43 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-12 11:32 [PATCH 1/2] input: gpio-keys: add support for disable button from DT Laxman Dewangan
2016-01-12 11:32 ` Laxman Dewangan [this message]
2016-01-12 14:43 ` [PATCH 2/2] input: gpio-keys: add support to name the gpio-keys Rob Herring
2016-01-12 14:55 ` Laxman Dewangan
[not found] ` <569513E6.60608-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-01-12 15:23 ` Rob Herring
2016-01-12 15:24 ` Laxman Dewangan
2016-01-14 9:16 ` Linus Walleij
2016-01-12 21:19 ` [PATCH 1/2] input: gpio-keys: add support for disable button from DT Dmitry Torokhov
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=1452598370-28509-2-git-send-email-ldewangan@nvidia.com \
--to=ldewangan@nvidia.com \
--cc=bjorn.andersson@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.torokhov@gmail.com \
--cc=galak@codeaurora.org \
--cc=ijc+devicetree@hellion.org.uk \
--cc=linus.walleij@linaro.org \
--cc=linux-input@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mark.rutland@arm.com \
--cc=pawel.moll@arm.com \
--cc=robh+dt@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).