Am Dienstag, 6. Februar 2007 18:39 schrieb Alan Stern:
> On Tue, 6 Feb 2007, Oliver Neukum wrote:
>
> > > With this infrastructure in place, all you have to do is
> > >
> > > set_bit(USB_DF_DEVICE_BUSY, &hid_to_usb_dev(hid)->dflags);
> > >
> > > whenever an event occurs. No messing around with extra timers.
> >
> > If you make USB_AUTOSUSPEND_DELAY a per interface variable,
> > I'll use this infrastructure.
>
> Okay, I'll do it. There will also be a per-device delay variable, whose
> value will be settable via sysfs.
>
> The question then becomes, with all those different delay values, what
> delay should the timer actually use? The simplest answer is to use the
> maximum of the delays. Does that sound right?
Hm, no. An interface may or may not use the "busy" facility, eg. a closed
hid devices would better simply be always suspended, but if it is opened,
it'll need its own timeout used.
So the answer would not be the largest delay, but the largest delay
currently requested to be active.
Regards
Oliver
-------------------------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier.
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid=120709&bid=263057&dat=121642
_______________________________________________
linux-usb-devel@lists.sourceforge.net
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
