From mboxrd@z Thu Jan 1 00:00:00 1970 From: Dan Williams Subject: Re: [PATCH 1/2] usbnet: allow status interrupt URB to always be active Date: Fri, 04 Jan 2013 19:26:33 -0600 Message-ID: <1357349193.19684.3.camel@dcbw.foobar.com> References: <20110727141246.GC29616@orbit.nwl.cc> <1357318096.5370.15.camel@dcbw.foobar.com> <2212516.GkG3xP33yG@linux-5eaq.site> Mime-Version: 1.0 Content-Type: text/plain; charset="UTF-8" Content-Transfer-Encoding: 7bit Cc: Elina Pasheva , netdev@vger.kernel.org, linux-usb@vger.kernel.org, Rory Filer , Phil Sutter To: Oliver Neukum Return-path: Received: from mx1.redhat.com ([209.132.183.28]:9725 "EHLO mx1.redhat.com" rhost-flags-OK-OK-OK-OK) by vger.kernel.org with ESMTP id S1755254Ab3AEBYT (ORCPT ); Fri, 4 Jan 2013 20:24:19 -0500 In-Reply-To: <2212516.GkG3xP33yG@linux-5eaq.site> Sender: netdev-owner@vger.kernel.org List-ID: On Fri, 2013-01-04 at 23:16 +0100, Oliver Neukum wrote: > On Friday 04 January 2013 10:48:16 Dan Williams wrote: > > Some drivers (ex sierra_net) need the status interrupt URB > > active even when the device is closed, because they receive > > custom indications from firmware. Allow sub-drivers to set > > a flag that submits the status interrupt URB on probe and > > keeps the URB alive over device open/close. The URB is still > > killed/re-submitted for suspend/resume, as before. > > > > Signed-off-by: Dan Williams > > --- > > Oliver: alternatively, is there a problem with *always* > > submitting the interrupt URB, and then simply not calling > > the subdriver's .status function when the netdev is > > closed? That would be a much simpler patch. > > That is quite radical. We have no idea what a device > does when we do not react to a status update. I would > much prefer to not take the risk. > Besides, we don't use bandwidth if we don't have to. Ok, so scratch the alternative. Thus, does the posted patch look like the right course of action? If I wasn't clear enough before, sierra_net needs to listen to the status interrupt URB to receive the custom Restart indication as part of the driver's device setup. Thus for sierra_net at least, tying the status interrupt URB submission to device open/close isn't right. I'd previously done a patch to handle this all in sierra_net, but the problem there is suspend/resume: without directly accessing the usbnet structure's ->suspend_count member (icky!) sierra_net can't correctly kill/submit the URB itself. So I went with a flag to usbnet that Sierra can set. Dan