On Tue, 11 Oct 2005, Franck wrote: > still tracking my bug...I just have 2 questions, I looked at uhci hcd > to have an idea on how interrupts and locks must be handled in > hcd->urb_enqueue method. uhci hcd simply disables IT in this method, > so every allocations are atomic and mem_flags parameters is simply > discarded.
That's right. > Furthermore it doesn't held urb->lock when using > urb->status field for example. Be more careful here. It doesn't hold urb->lock while _reading_ urb->status; there's no point. But it does hold urb->lock while _writing_ urb->status. That is necessary. > Are these 2 points are correct ? Can I > do the same in my hcd ? Subject to the restriction about writing urb->status, yes. Alan Stern ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ linux-usb-devel@lists.sourceforge.net To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
