On Tue, Dec 11, 2001, David Brownell <[EMAIL PROTECTED]> wrote: > > > 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.
Yes, but you're making this complicated now. Allocate devrequest when you allocate the device and it'll work in 99% of the cases people care about, which is 100% of existing drivers. There will almost always be exceptions to the rule. BTW - Another 2.5 thing I'd like to see is someone scold me for the case of the name and elements of devrequest and then change it to be similar to the USB specs and the rest of the structures in the Linux USB code :) JE _______________________________________________ [EMAIL PROTECTED] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
