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 1/2] input: gpio-keys: add support for disable button from DT
Date: Tue, 12 Jan 2016 23:06:09 -0800 [thread overview]
Message-ID: <20160113070609.GB8906@dtor-ws> (raw)
In-Reply-To: <1452665657-9412-1-git-send-email-ldewangan@nvidia.com>
On Wed, Jan 13, 2016 at 11:44:16AM +0530, Laxman Dewangan wrote:
> Add support to disable the button from DT via status property
> if given button is not supporting on given platforms.
>
> This will help to re-use the existing dtsi file with status
> enable/disable across platforms.
>
> Signed-off-by: Laxman Dewangan <ldewangan@nvidia.com>
> ---
> Changes from V1:
> - Converted print to dev_dbg.
>
> drivers/input/keyboard/gpio_keys.c | 8 ++++++++
> 1 file changed, 8 insertions(+)
>
> diff --git a/drivers/input/keyboard/gpio_keys.c b/drivers/input/keyboard/gpio_keys.c
> index bef317f..08bada8 100644
> --- a/drivers/input/keyboard/gpio_keys.c
> +++ b/drivers/input/keyboard/gpio_keys.c
> @@ -632,6 +632,14 @@ gpio_keys_get_devtree_pdata(struct device *dev)
> for_each_child_of_node(node, pp) {
> enum of_gpio_flags flags;
>
> + /* Ignore the button if status of node is disabled */
> + error = of_device_is_available(pp);
> + if (!error) {
> + dev_dbg(dev, "Button %s is ignored\n", pp->name);
> + pdata->nbuttons--;
Looking at this some more, maybe we should be using
of_get_available_child_count() when calculating pdata->nbuttons (and do
not decrement it here) and maybe even use
for_each_available_child_of_node() in this loop and forego manual check.
> + continue;
> + }
> +
> button = &pdata->buttons[i++];
>
> button->gpio = of_get_gpio_flags(pp, 0, &flags);
> --
> 2.1.4
>
Thanks.
--
Dmitry
next prev parent reply other threads:[~2016-01-13 7:06 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
2016-01-13 7:06 ` Dmitry Torokhov [this message]
2016-01-13 7:07 ` [PATCH V2 1/2] input: gpio-keys: add support for disable button from DT 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=20160113070609.GB8906@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