From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: Laxman Dewangan <ldewangan@nvidia.com>
Cc: robh+dt@kernel.org, pawel.moll@arm.com, mark.rutland@arm.com,
galak@codeaurora.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-input@vger.kernel.org,
linus.walleij@linaro.org, bjorn.andersson@sonymobile.com
Subject: Re: [PATCH V2 2/2] input: gpio-keys: add support to name the gpio-keys
Date: Tue, 12 Jan 2016 23:02:33 -0800 [thread overview]
Message-ID: <20160113070233.GA8906@dtor-ws> (raw)
In-Reply-To: <1452665657-9412-2-git-send-email-ldewangan@nvidia.com>
On Wed, Jan 13, 2016 at 11:44:17AM +0530, Laxman Dewangan wrote:
> 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>
Applied, thank you.
> ---
> Changes from V1:
> - Use standard property "label" instead of custom property "gpio-keys,name"
>
> 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..f23bfa1 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:
> + - label: 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 08bada8..448f38f 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, "label", &pdata->name);
> +
> i = 0;
> for_each_child_of_node(node, pp) {
> enum of_gpio_flags flags;
> --
> 2.1.4
>
--
Dmitry
next prev parent reply other threads:[~2016-01-13 7:02 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-01-13 6:14 [PATCH V2 1/2] input: gpio-keys: add support for disable button from DT Laxman Dewangan
2016-01-13 6:14 ` [PATCH V2 2/2] input: gpio-keys: add support to name the gpio-keys Laxman Dewangan
2016-01-13 7:02 ` Dmitry Torokhov [this message]
[not found] ` <1452665657-9412-1-git-send-email-ldewangan-DDmLM1+adcrQT0dZR+AlfA@public.gmane.org>
2016-01-13 7:06 ` [PATCH V2 1/2] input: gpio-keys: add support for disable button from DT Dmitry Torokhov
2016-01-13 7:07 ` Laxman Dewangan
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=20160113070233.GA8906@dtor-ws \
--to=dmitry.torokhov@gmail.com \
--cc=bjorn.andersson@sonymobile.com \
--cc=devicetree@vger.kernel.org \
--cc=galak@codeaurora.org \
--cc=ldewangan@nvidia.com \
--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).