Am Samstag, 5. Mai 2007 17:30 schrieb Alan Stern:
> > What makes you sure it is abnormal? What would impose an upper bound
> > on the time a device may have data?
>
> The bound isn't on the time a device may have data -- it's on the time
> allowed for a transfer to complete. And the upper bound would be imposed
> by the driver. How long is it willing to hold up suspend processing
> because of ongoing I/O? The driver must decide one way or another.
>
> (There's always an alternative; the driver could abort the suspend if I/O
> is pending. But that's the only choice: Either the suspend carries on and
> the I/O fails, or the I/O succeeds and the suspend fails.)
>
> The case you have in mind is usb-skeleton, where write requests are
> submitted and then forgotten. I think it makes perfect sense to put an
> upper limit on the how much time the device has to accept the data.
OK, I'll do it that way.
Regards
Oliver
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
[email protected]
To unsubscribe, use the last form field at:
https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
