From: Gabor Juhos <juhosg@openwrt.org>
To: Dmitry Torokhov <dmitry.torokhov@gmail.com>
Cc: linux-input@vger.kernel.org,
Alexandre Pereira da Silva <aletes.xgr@gmail.com>,
stable@vger.kernel.org
Subject: Re: [PATCH] Input: gpio_keys_polled - defer probing if GPIO probing is deferred
Date: Sun, 23 Dec 2012 18:51:05 +0100 [thread overview]
Message-ID: <50D74489.2030000@openwrt.org> (raw)
In-Reply-To: <20121223100625.GB17407@core.coreip.homeip.net>
2012.12.23. 11:06 keltezéssel, Dmitry Torokhov írta:
> Well spotted, thanks. However I think the patch should look like the one
> below as we should propagate all errors, not only -EPROBE_DEFER, up the
> stack.
>
> Thanks.
>
>
> Input: gpio_keys_polled - defer probing if GPIO probing is deferred
>
> From: Gabor Juhos <juhosg@openwrt.org>
>
> If GPIO probing is deferred, the driver tries to claim an invalid GPIO line
> which leads to an error message like this:
>
> gpio-keys-polled buttons.2: unable to claim gpio 4294966779, err=-22
> gpio-keys-polled: probe of buttons.2 failed with error -22
>
> The patch ensures that error code returned by of_get_gpio_flags (including
> -EPROBE_DEFER) is propagated up the stack.
>
> Cc: stable@vger.kernel.org
> Signed-off-by: Gabor Juhos <juhosg@openwrt.org>
> Signed-off-by: Dmitry Torokhov <dmitry.torokhov@gmail.com>
> ---
> drivers/input/keyboard/gpio_keys_polled.c | 13 ++++++++++++-
> 1 file changed, 12 insertions(+), 1 deletion(-)
>
> diff --git a/drivers/input/keyboard/gpio_keys_polled.c b/drivers/input/keyboard/gpio_keys_polled.c
> index f686fd9..e75ca6b 100644
> --- a/drivers/input/keyboard/gpio_keys_polled.c
> +++ b/drivers/input/keyboard/gpio_keys_polled.c
> @@ -135,6 +135,7 @@ static struct gpio_keys_platform_data *gpio_keys_polled_get_devtree_pdata(struct
>
> i = 0;
> for_each_child_of_node(node, pp) {
> + int gpio;
> enum of_gpio_flags flags;
>
> if (!of_find_property(pp, "gpios", NULL)) {
> @@ -143,9 +144,19 @@ static struct gpio_keys_platform_data *gpio_keys_polled_get_devtree_pdata(struct
> continue;
> }
>
> + gpio = of_get_gpio_flags(pp, 0, &flags);
> + if (gpio < 0) {
> + error = gpio;
> + if (error != -EPROBE_DEFER)
> + dev_err(dev,
> + "Failed to get gpio flags, error: %d\n",
> + error);
> + goto err_free_pdata;
> + }
> +
> button = &pdata->buttons[i++];
>
> - button->gpio = of_get_gpio_flags(pp, 0, &flags);
> + button->gpio = gpio;
> button->active_low = flags & OF_GPIO_ACTIVE_LOW;
>
> if (of_property_read_u32(pp, "linux,code", &button->code)) {
Yes, this looks saner. I have replaced my patch with this, and it is working as
intended. The kernel says this:
platform buttons.2: Driver gpio-keys-polled requests probe deferral
BTW, it seems that the gpio-keys driver needs a similar fix.
-Gabor
--
To unsubscribe from this list: send the line "unsubscribe linux-input" in
the body of a message to majordomo@vger.kernel.org
More majordomo info at http://vger.kernel.org/majordomo-info.html
prev parent reply other threads:[~2012-12-23 17:51 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2012-12-23 8:32 [PATCH] Input: gpio_keys_polled - defer probing if GPIO probing is deferred Gabor Juhos
2012-12-23 10:06 ` Dmitry Torokhov
2012-12-23 17:51 ` Gabor Juhos [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=50D74489.2030000@openwrt.org \
--to=juhosg@openwrt.org \
--cc=aletes.xgr@gmail.com \
--cc=dmitry.torokhov@gmail.com \
--cc=linux-input@vger.kernel.org \
--cc=stable@vger.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).