Hi Johan, On Monday 11 June 2012 11:40:11 Johan Hedberg wrote: > It's there a risk that this ends up in an infinite loop if the kernel is > in some state where it always keeps sending STATUS_BUSY? Would it make > sense to add a counter for retries and give up after 5 or 10 attempts? That would meant host didn't get command complete for set COD command (meaning something else is badly broken), but I guess adding counter 'just in case' wouldn't hurt much. > Would it also make sense to add a small delay before resending the > command? I'm not sure up to how long can setting COD take, on my pc it takes <100ms for `hciconfig hci0 class 0x540100` with USB dongle. Does g_timeout_add with timeout ~50ms make sense? -- Szymon K. Janc szymon@xxxxxxxxxxx -- To unsubscribe from this list: send the line "unsubscribe linux-bluetooth" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
