Hi Alan, Thank you for the suggestion. We independently ended up with the same workaround, but still weren't happy with it. The problem is we don't want to relinquish access to the device, but to do set-interface, you have to do release interface, and t's a little strange that you are releasing access to the device just to keep using it. While it is unlikely that we will have some other process come in and grab the interface, it still just strikes us as unclean. Yuliya On Wed, Oct 3, 2012 at 8:13 AM, Alan Stern <stern@xxxxxxxxxxxxxxxxxxx> wrote: > On Tue, 2 Oct 2012, Yuliya T wrote: > >> Our device goes through a software-directed firmware reset which >> clears the device-side toggle bits (or sequence numbers). The >> endpoint is not halted though. Therefore, we want a clean way to >> reset the toggle bits (or sequence numbers) on the host without having >> to reconnect to the device. For USB2 (EHCI) we have always related on >> ClearFeature(ENDPOINT_HALT). Do you have any suggestions, or for the >> sake of interoperability and consistency, do you think it might be a >> good idea to just pass the reset ep command down to the hardware and >> let it decide what to do? > > How about doing a Set-Interface or Set-Configuration instead? > > Alan Stern > -- To unsubscribe from this list: send the line "unsubscribe linux-usb" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
