Thread (34 messages) flat view 34 messages, 5 authors, 2012-09-19

Re: [PATCH 0/7] HID: picoLCD updates

From: Jiri Kosina <hidden>
Date: 2012-08-16 16:47:15
Also in: linux-input, lkml

On Thu, 16 Aug 2012, Bruno Prémont wrote:
quoted
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
Keyboard shortcuts
hback out one level
jnext message in thread
kprevious message in thread
ldrill in
Escclose help / fold thread tree
?toggle this help