On Thu, 16 Aug 2012, Bruno Prémont wrote: > > I don't really understand this explanation. Once usb_kill_urb() returns, > > the URB should be available for future use (and therefore all queues > > completely drained). > > I won't have time today to check, though my guess is that on each > echo $usb-id > bind; echo $usb-id > unbind > under /sys/bus/hid/drivers/hid-picolcd/ the USB urb queue fills a bit does > not get cleared. > > Is usb_kill_urb() called when unbinding just the specific hid driver? Yup, through hid_hw_stop() -> usbhid_stop(). > If so my short timing between bind/unbind must be triggering something > else... > > Otherwise I'm missing something as at first time I got no "output queue full" > messages, but as I repeated the bind/unbind sequences the prints per bind/unbind > iteration increased in number. > > Anyhow, on Friday evening/week-end I will continue digging and report back with my > findings. Thank you, Bruno. -- Jiri Kosina SUSE Labs -- To unsubscribe from this list: send the line "unsubscribe linux-input" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
