[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <20160419080150.GB13933@dtor-ws>
Date: Tue, 19 Apr 2016 01:01:50 -0700
From: Dmitry Torokhov <dmitry.torokhov@...il.com>
To: "H. Nikolaus Schaller" <hns@...delico.com>
Cc: Fabio Estevam <fabio.estevam@...escale.com>,
Peter Ujfalusi <peter.ujfalusi@...com>,
linux-input@...r.kernel.org, linux-kernel@...r.kernel.org,
kernel@...a-handheld.com, letux-kernel@...nphoenux.org
Subject: Re: [PATCH 5/5] input: twl6040-vibra: remove mutex
On Tue, Apr 19, 2016 at 09:49:01AM +0200, H. Nikolaus Schaller wrote:
>
> > Am 18.04.2016 um 23:20 schrieb Dmitry Torokhov <dmitry.torokhov@...il.com>:
> >
> > On Mon, Apr 18, 2016 at 09:55:41PM +0200, H. Nikolaus Schaller wrote:
> >> The mutex does not seem to be needed.
> >
> > twl6040_vibra_suspend() and vibra_play_work() may run concurrently, no?
>
> Hm. I don't know about the rule that would give an answer to this question...
Sorry, that was actually a statement, not really a question. It is
possible (although very unlikely) that userspace posts play request and
workqueue will not run until after suspend callback.
Thinking about it some more I wonder if we better do what
twl6040_vibra_close() does and cancel the work before shutting off the
device, so that there is no chance of work executing after suspend
callback and reenabling the device. This way we can indeed remove the
mutex.
Thanks.
--
Dmitry
Powered by blists - more mailing lists