From mboxrd@z Thu Jan 1 00:00:00 1970 From: Tejun Heo Subject: Re: Re: Re: Re: Re: [PATCH v4 11/18] input: Add initial support for TWL6040 vibrator Date: Wed, 15 Jun 2011 10:23:01 +0200 Message-ID: <20110615082301.GN8141@htj.dyndns.org> References: <1307706876-4768-1-git-send-email-peter.ujfalusi@ti.com> <4476185.bf2jyafmHt@barack> <20110614081836.GG8141@htj.dyndns.org> <100646074.zaKeYdXKr4@barack> <20110615081858.GM8141@htj.dyndns.org> Mime-Version: 1.0 Content-Type: text/plain; charset=us-ascii Return-path: Content-Disposition: inline In-Reply-To: <20110615081858.GM8141@htj.dyndns.org> Sender: linux-omap-owner@vger.kernel.org To: =?iso-8859-1?Q?P=E9ter?= Ujfalusi Cc: Dmitry Torokhov , "Girdwood, Liam" , Tony Lindgren , Mark Brown , Samuel Ortiz , "linux-input@vger.kernel.org" , "linux-omap@vger.kernel.org" , "linux-kernel@vger.kernel.org" , "alsa-devel@alsa-project.org" , "Lopez Cruz, Misael" List-Id: linux-input@vger.kernel.org On Wed, Jun 15, 2011 at 10:18:58AM +0200, Tejun Heo wrote: > No human being can feel 120usec difference and I can't see how using > HIGHPRI is justified here (which is what the code is doing > _accidentally_ by using singlethread_workqueue). Ooh, one more thing, and even if you insist on using HIGHPRI (please don't), you don't need to create workqueue for each device. You can just create one for the whole driver in init and destroy it from exit. What matters is the HIGHPRI attribute of the workqueue. The number of workqueues is completely irrelevant. Thank you. -- tejun