linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Alek Du <alek.du@intel.com>
Cc: "dmitry.torokhov@gmail.com" <dmitry.torokhov@gmail.com>,
	"linux-kernel@vger.kernel.org" <linux-kernel@vger.kernel.org>,
	"linux-input@vger.kernel.org" <linux-input@vger.kernel.org>,
	"soni.trilok@gmail.com" <soni.trilok@gmail.com>,
	"ben-linux@fluff.org" <ben-linux@fluff.org>,
	"ext-phil.2.carmody@nokia.com" <ext-phil.2.carmody@nokia.com>,
	"ext-jani.1.nikula@nokia.com" <ext-jani.1.nikula@nokia.com>
Subject: Re: [PATCH 2/2] input: gpio-keys: avoid possibility of sleeping in timer function
Date: Mon, 29 Jun 2009 18:30:38 +0800	[thread overview]
Message-ID: <20090629183038.000009c1@unknown> (raw)
In-Reply-To: <7dbf3c1888fe61729b6c9e399971012611122a28.1246015395.git.ext-jani.1.nikula@nokia.com>

On Fri, 26 Jun 2009 20:15:18 +0800
Jani Nikula <ext-jani.1.nikula@nokia.com> wrote:

> The gpio_get_value function may sleep, so it should not be called in a
> timer function. Move gpio_get_value calls to workqueue.
> 
> Signed-off-by: Jani Nikula <ext-jani.1.nikula@nokia.com>
> ---
>  drivers/input/keyboard/gpio_keys.c |   17 ++++++++++++-----
>  1 files changed, 12 insertions(+), 5 deletions(-)
> 
> diff --git a/drivers/input/keyboard/gpio_keys.c
> b/drivers/input/keyboard/gpio_keys.c index 9767213..efed0c9 100644
> --- a/drivers/input/keyboard/gpio_keys.c
> +++ b/drivers/input/keyboard/gpio_keys.c
> @@ -22,6 +22,7 @@
>  #include <linux/platform_device.h>
>  #include <linux/input.h>
>  #include <linux/gpio_keys.h>
> +#include <linux/workqueue.h>
>  
>  #include <asm/gpio.h>
>  
> @@ -29,6 +30,7 @@ struct gpio_button_data {
>  	struct gpio_keys_button *button;
>  	struct input_dev *input;
>  	struct timer_list timer;
> +	struct work_struct work;
>  };
>  
>  struct gpio_keys_drvdata {
> @@ -36,8 +38,10 @@ struct gpio_keys_drvdata {
>  	struct gpio_button_data data[0];
>  };
>  
> -static void gpio_keys_report_event(struct gpio_button_data *bdata)
> +static void gpio_keys_report_event(struct work_struct *work)
>  {
> +	struct gpio_button_data *bdata =
> +		container_of(work, struct gpio_button_data, work);
>  	struct gpio_keys_button *button = bdata->button;
>  	struct input_dev *input = bdata->input;
>  	unsigned int type = button->type ?: EV_KEY;
> @@ -47,11 +51,11 @@ static void gpio_keys_report_event(struct
> gpio_button_data *bdata) input_sync(input);
>  }
>  
> -static void gpio_check_button(unsigned long _data)
> +static void gpio_keys_timer(unsigned long _data)
>  {
>  	struct gpio_button_data *data = (struct gpio_button_data
> *)_data; 
> -	gpio_keys_report_event(data);
> +	schedule_work(&data->work);
>  }
>  
>  static irqreturn_t gpio_keys_isr(int irq, void *dev_id)
> @@ -65,7 +69,7 @@ static irqreturn_t gpio_keys_isr(int irq, void
> *dev_id) mod_timer(&bdata->timer,
>  			jiffies +
> msecs_to_jiffies(button->debounce_interval)); else
> -		gpio_keys_report_event(bdata);
> +		schedule_work(&bdata->work);
>  
>  	return IRQ_HANDLED;
>  }
> @@ -113,7 +117,8 @@ static int __devinit gpio_keys_probe(struct
> platform_device *pdev) bdata->input = input;
>  		bdata->button = button;
>  		setup_timer(&bdata->timer,
> -			    gpio_check_button, (unsigned long)bdata);
> +			    gpio_keys_timer, (unsigned long)bdata);
> +		INIT_WORK(&bdata->work, gpio_keys_report_event);
>  
>  		error = gpio_request(button->gpio, button->desc ?:
> "gpio_keys"); if (error < 0) {
> @@ -174,6 +179,7 @@ static int __devinit gpio_keys_probe(struct
> platform_device *pdev) free_irq(gpio_to_irq(pdata->buttons[i].gpio),
> &ddata->data[i]); if (pdata->buttons[i].debounce_interval)
>  			del_timer_sync(&ddata->data[i].timer);
> +		cancel_work_sync(&ddata->data[i].work);
>  		gpio_free(pdata->buttons[i].gpio);
>  	}
>  
> @@ -199,6 +205,7 @@ static int __devexit gpio_keys_remove(struct
> platform_device *pdev) free_irq(irq, &ddata->data[i]);
>  		if (pdata->buttons[i].debounce_interval)
>  			del_timer_sync(&ddata->data[i].timer);
> +		cancel_work_sync(&ddata->data[i].work);
>  		gpio_free(pdata->buttons[i].gpio);
>  	}
>  

Tested with my board, it works well. Dmitry, could you please consider
to apply it?

Tested-by: Alek Du <alek.du@intel.com>

  reply	other threads:[~2009-06-29 10:32 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2009-06-08  7:24 [PATCH]input: Change timer function to workqueue for gpio_keys driver Alek Du
2009-06-12 17:40 ` Trilok Soni
2009-06-25 10:29   ` Jani Nikula
2009-06-25 13:06     ` Alek Du
2009-06-25 13:31       ` Jani Nikula
2009-06-25 14:08         ` Alek Du
2009-06-25 14:52           ` Jani Nikula
2009-06-25 15:05             ` Jani Nikula
2009-06-25 15:09               ` Alek Du
2009-06-25 15:42                 ` Jani Nikula
2009-06-25 15:48                   ` Alek Du
2009-06-25 16:09                     ` Phil Carmody
2009-06-25 16:23                       ` Alek Du
2009-06-25 16:42                         ` Dmitry Torokhov
2009-06-26 12:15                         ` [PATCH 0/2] fix gpio-keys debouncing and timer sleep issues Jani Nikula
2009-06-26 12:15                           ` [PATCH 1/2] Revert "Input: gpio-keys - change timer to workqueue" Jani Nikula
2009-06-26 12:15                             ` [PATCH 2/2] input: gpio-keys: avoid possibility of sleeping in timer function Jani Nikula
2009-06-29 10:30                               ` Alek Du [this message]
2009-06-26 12:50                           ` [PATCH 0/2] fix gpio-keys debouncing and timer sleep issues Du, Alek
2009-06-29  5:59                           ` Dmitry Torokhov
2009-06-29 10:32                             ` Jani Nikula

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=20090629183038.000009c1@unknown \
    --to=alek.du@intel.com \
    --cc=ben-linux@fluff.org \
    --cc=dmitry.torokhov@gmail.com \
    --cc=ext-jani.1.nikula@nokia.com \
    --cc=ext-phil.2.carmody@nokia.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=soni.trilok@gmail.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).