> > You might also want to prealloc a scratch buffer or > > stuff one in your per instance structure for said usb device and use that. > > This is a fine idea.
A fine typical-case optimization, yes. > You can only do one control transfer at a time anyway. Actually there's no technical reason device shouldn't handle multiple queued control transfers, and I could see it happening in cases where more than one driver needs to talk to the device at a time. Whether drivers want to impose a exclusionary policy about control transfers is orthogonal to mutual exclusion for the use of such a buffer. - Dave _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
