On Sat, 2013-01-05 at 12:01 +0100, Oliver Neukum wrote:
On Friday 04 January 2013 19:26:33 Dan Williams wrote:
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
On Fri, 2013-01-11 at 11:06 +0800, Ming Lei wrote:
On Sat, Jan 5, 2013 at 9:26 AM, Dan Williams d...@redhat.com wrote:
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
On Tue, Jan 15, 2013 at 1:23 AM, Dan Williams d...@redhat.com wrote:
On Fri, 2013-01-11 at 11:06 +0800, Ming Lei wrote:
I am curious who are interested in the 'custom Restart indication'
information after the interface is closed.
It's actually before the interface is even opened. It's really
On Sat, Jan 5, 2013 at 9:26 AM, Dan Williams d...@redhat.com wrote:
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
On Sat, 2013-01-05 at 12:01 +0100, Oliver Neukum wrote:
On Friday 04 January 2013 19:26:33 Dan Williams wrote:
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
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
