From mboxrd@z Thu Jan 1 00:00:00 1970 From: Ville =?iso-8859-1?Q?Syrj=E4l=E4?= Subject: Re: [rft]power management for usbtouch Date: Fri, 27 Jun 2008 23:20:27 +0300 Message-ID: <20080627202027.GG19430@sci.fi> References: <200806261557.19095.oliver@neukum.org> <200806271050.02579.oliver@neukum.org> <20080627161036.GE19430@sci.fi> <200806272107.14934.oliver@neukum.org> Mime-Version: 1.0 Content-Type: text/plain; charset=iso-8859-1 Content-Transfer-Encoding: QUOTED-PRINTABLE Return-path: Received: from smtp4.pp.htv.fi ([213.243.153.38]:52115 "EHLO smtp4.pp.htv.fi" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1756281AbYF0UU2 (ORCPT ); Fri, 27 Jun 2008 16:20:28 -0400 Content-Disposition: inline In-Reply-To: <200806272107.14934.oliver@neukum.org> Sender: linux-input-owner@vger.kernel.org List-Id: linux-input@vger.kernel.org To: Oliver Neukum Cc: daniel.ritz@gmx.ch, Dmitry Torokhov , Jiri Kosina , linux-usb@vger.kernel.org, linux-input@vger.kernel.org On Fri, Jun 27, 2008 at 09:07:13PM +0200, Oliver Neukum wrote: > Am Freitag 27 Juni 2008 18:10:36 schrieb Ville Syrj=E4l=E4: > > On Fri, Jun 27, 2008 at 10:50:00AM +0200, Oliver Neukum wrote: > > > @@ -820,20 +824,34 @@ exit: > > > static int usbtouch_open(struct input_dev *input) > > > { > > > struct usbtouch_usb *usbtouch =3D input_get_drvdata(input); > > > + int rv; > > > =20 > > > + rv =3D usb_autopm_get_interface(usbtouch->intf); > > > + if (rv < 0) > > > + goto bail; > > > + mutex_lock(&usbtouch->lock); > > > usbtouch->irq->dev =3D usbtouch->udev; > > > =20 > > > - if (usb_submit_urb(usbtouch->irq, GFP_KERNEL)) > > > - return -EIO; > > > - > > > - return 0; > > > + if (usb_submit_urb(usbtouch->irq, GFP_KERNEL)) { > > > + rv =3D -EIO; > > > + usb_autopm_put_interface(usbtouch->intf); > > > + } else { > > > + usbtouch->open =3D 1; > > > + } > > > + mutex_unlock(&usbtouch->lock); > > > +bail: > > > + return rv; > > > } > >=20 > > What if the device is already suspended when open() is called? > >=20 >=20 > It cannot be. usb_autopm_get_interface() is called, which will resume > the device. Ah, so it resumes the device even if it was not autosuspended but suspended for another reason? If I understood correctly usb_autpm_get_interface() will only prevent further autosuspend requests. But is there anything protecting this against another (non-auto) suspend request coming in between usb_autopm_get_interface() and mutex_lock()? --=20 Ville Syrj=E4l=E4 syrjala@sci.fi http://www.sci.fi/~syrjala/ -- To unsubscribe from this list: send the line "unsubscribe linux-input" = in the body of a message to majordomo@vger.kernel.org More majordomo info at http://vger.kernel.org/majordomo-info.html