linux-input.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Dmitry Torokhov <dmitry.torokhov@gmail.com>
To: thesven73@gmail.com
Cc: linux-input@vger.kernel.org, linux-kernel@vger.kernel.org,
	Tejun Heo <tj@kernel.org>
Subject: Re: [PATCH] Input: qt2160 - remove redundant spinlock
Date: Mon, 11 Feb 2019 14:16:12 -0800	[thread overview]
Message-ID: <20190211221612.GB149505@dtor-ws> (raw)
In-Reply-To: <20190211023222.29168-1-TheSven73@gmail.com>

On Sun, Feb 10, 2019 at 09:32:22PM -0500, thesven73@gmail.com wrote:
> From: Sven Van Asbroeck <TheSven73@gmail.com>
> 
> Remove a spinlock which prevents schedule_delayed_work() and
> mod_delayed_work() from executing concurrently.
> 
> This was required back when mod_delayed_work() did not exist,
> and had to be implemented with a cancel + schedule. See
> commit e7c2f967445d ("workqueue: use mod_delayed_work() instead of
> __cancel + queue")
> 
> schedule_delayed_work() and mod_delayed_work() can now be used
> concurrently. So the spinlock is no longer needed.
> 
> Cc: Tejun Heo <tj@kernel.org>
> Signed-off-by: Sven Van Asbroeck <TheSven73@gmail.com>

Applied, thank you.

> ---
>  drivers/input/keyboard/qt2160.c | 9 ---------
>  1 file changed, 9 deletions(-)
> 
> diff --git a/drivers/input/keyboard/qt2160.c b/drivers/input/keyboard/qt2160.c
> index 43b86482dda0..23dc7c0c7d78 100644
> --- a/drivers/input/keyboard/qt2160.c
> +++ b/drivers/input/keyboard/qt2160.c
> @@ -69,7 +69,6 @@ struct qt2160_data {
>  	struct i2c_client *client;
>  	struct input_dev *input;
>  	struct delayed_work dwork;
> -	spinlock_t lock;        /* Protects canceling/rescheduling of dwork */
>  	unsigned short keycodes[ARRAY_SIZE(qt2160_key2code)];
>  	u16 key_matrix;
>  #ifdef CONFIG_LEDS_CLASS
> @@ -221,22 +220,15 @@ static int qt2160_get_key_matrix(struct qt2160_data *qt2160)
>  static irqreturn_t qt2160_irq(int irq, void *_qt2160)
>  {
>  	struct qt2160_data *qt2160 = _qt2160;
> -	unsigned long flags;
> -
> -	spin_lock_irqsave(&qt2160->lock, flags);
>  
>  	mod_delayed_work(system_wq, &qt2160->dwork, 0);
>  
> -	spin_unlock_irqrestore(&qt2160->lock, flags);
> -
>  	return IRQ_HANDLED;
>  }
>  
>  static void qt2160_schedule_read(struct qt2160_data *qt2160)
>  {
> -	spin_lock_irq(&qt2160->lock);
>  	schedule_delayed_work(&qt2160->dwork, QT2160_CYCLE_INTERVAL);
> -	spin_unlock_irq(&qt2160->lock);
>  }
>  
>  static void qt2160_worker(struct work_struct *work)
> @@ -406,7 +398,6 @@ static int qt2160_probe(struct i2c_client *client,
>  	qt2160->client = client;
>  	qt2160->input = input;
>  	INIT_DELAYED_WORK(&qt2160->dwork, qt2160_worker);
> -	spin_lock_init(&qt2160->lock);
>  
>  	input->name = "AT42QT2160 Touch Sense Keyboard";
>  	input->id.bustype = BUS_I2C;
> -- 
> 2.17.1
> 

-- 
Dmitry

      reply	other threads:[~2019-02-11 22:16 UTC|newest]

Thread overview: 2+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-02-11  2:32 [PATCH] Input: qt2160 - remove redundant spinlock thesven73
2019-02-11 22:16 ` Dmitry Torokhov [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=20190211221612.GB149505@dtor-ws \
    --to=dmitry.torokhov@gmail.com \
    --cc=linux-input@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=thesven73@gmail.com \
    --cc=tj@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).