Return-Path: Received: (majordomo@vger.kernel.org) by vger.kernel.org via listexpand id S935548Ab0BZIMY (ORCPT ); Fri, 26 Feb 2010 03:12:24 -0500 Received: from mail-yw0-f197.google.com ([209.85.211.197]:40105 "EHLO mail-yw0-f197.google.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S935455Ab0BZIMW (ORCPT ); Fri, 26 Feb 2010 03:12:22 -0500 DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=gamma; h=date:from:to:cc:subject:message-id:references:mime-version :content-type:content-disposition:in-reply-to:user-agent; b=Ds7uRPjoHcXmQCiRL+OLrH6o08X2w0uPpBwf2s9qEf8hwtu1lXmDtjfHYf2kK7jtTZ WuL4+LRtEaEyY/meeNFAsMI9TTRXgk33lnAqeXQiiXeb66YoxQzobY3pYfXSilB66TcB guPbvegZuY0bP/31IZDOiWBVEYb7rk+onMUQk= Date: Fri, 26 Feb 2010 00:12:17 -0800 From: Dmitry Torokhov To: "Rick L. Vinyard, Jr." Cc: Jiri Kosina , Oliver Neukum , Bruno =?iso-8859-1?Q?Pr=C3=A9mont?= , linux-input@vger.kernel.org, linux-usb@vger.kernel.org, linux-fbdev@vger.kernel.org, linux-kernel@vger.kernel.org, Nicu Pavel Subject: Re: [PATCH 1/3] picolcd: driver for PicoLCD HID device Message-ID: <20100226081217.GA17444@core.coreip.homeip.net> References: <20100221002001.0a7e05a7@neptune.home> <20100224170049.0d04af3c@neptune.home> <201002241927.53532.oliver@neukum.org> <7316226fbd1cb53b7f90965c54acd343.squirrel@intranet.cs.nmsu.edu> MIME-Version: 1.0 Content-Type: text/plain; charset=us-ascii Content-Disposition: inline In-Reply-To: <7316226fbd1cb53b7f90965c54acd343.squirrel@intranet.cs.nmsu.edu> User-Agent: Mutt/1.5.20 (2009-08-17) Sender: linux-kernel-owner@vger.kernel.org List-ID: X-Mailing-List: linux-kernel@vger.kernel.org Content-Length: 1683 Lines: 39 On Thu, Feb 25, 2010 at 08:34:42AM -0700, Rick L. Vinyard, Jr. wrote: > Jiri Kosina wrote: > > On Wed, 24 Feb 2010, Rick L. Vinyard, Jr. wrote: > > > >> The key difference is the replacement of spin_lock() with spin_trylock() > >> such that if the non-interrupt code has already obtained the lock, the > >> interrupt will not deadlock but instead take the else path and schedule > >> a > >> framebuffer update at the next interval. > > > > Why is _irqsave() and/or deferred work not enough? The aproach with > > _trylock() seems to be overly complicated for no good reason (I personally > > become very suspicious every time I see code that is using _trylock()). > > > > I was concerned about _irqsave() because the lock is split across two > functions to protect the urb after it is handed off to the usb subsystem > with usb_submit_urb(). It's locked in g13_fb_send() and unlocked in the > urb completion callback. > > As for deferred work, the g13_fb_send() is the I/O portion of the deferred > framebuffer callback. I was concerned that without a lock one deferred > update could hand the urb off to the usb subsystem and a second could try > to access it before it was handed back to the driver. > > In this case the _trylock() would fail and in the else patch we would > defer yet again until the next update cycle. > What you are looking for here is called test_and_set_bit(). Do not muddy the waters with a lock. -- Dmitry -- To unsubscribe from this list: send the line "unsubscribe linux-kernel" in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html Please read the FAQ at http://www.tux.org/lkml/