* Possible problem with btusb suspend resume handling
@ 2013-10-09 15:10 Hans de Goede
0 siblings, 0 replies; only message in thread
From: Hans de Goede @ 2013-10-09 15:10 UTC (permalink / raw)
To: linux-bluetooth
Hi,
While reviewing all users of usb_anchor-s (because of some
usb_anchor fixes I've been writing), I noticed that btusb normally
puts to be transmitted urbs on an anchor called tx_anchor and then
submits them, unless suspended, then they are put on an anchor called
deferred without being submitted.
On resume any urbs on the deferred anchor get removed from the deferred
anchor, and submitted to the device.
But unlike other drivers which similar constructs, btusb does not
move put them on the tx_anchor when submitting then from the resume
handler.
So after a resume with deferred transmits, there will be tx urbs in
flight which are not anchored on the tx_anchor. I believe this is
a bug, but I don't know the code well enough to be sure.
Regards,
Hans
^ permalink raw reply [flat|nested] only message in thread
only message in thread, other threads:[~2013-10-09 15:10 UTC | newest]
Thread overview: (only message) (download: mbox.gz follow: Atom feed
-- links below jump to the message on this page --
2013-10-09 15:10 Possible problem with btusb suspend resume handling Hans de Goede
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox