> Our test-module only gets the expected timeout error, when the DATA > transfer fails (neither NAK nor ACK) and the following two PINGs too. > > If only one PING is failing, and this is where I gave up, the transfer is > executed again. I wasn't able to figure out, if the retry is done by the > ehci-hcd-driver or if it is done in hardware. :/
It's done in hardware. For PING details, see the USB 2.0 spec. > I would highly appreciate if someone could tell me where and how I can > disable retrying (so that a transfer immediatly fails) or where I can > query the number of retries done automagically or the number of failed > PING-transfers? The only tunable thing is EHCI_TUNE_CERR; you could reduce the number of retries from three to one. But those should affect only error cases. - Dave ------------------------------------------------------- This SF.Net email is sponsored by: Power Architecture Resource Center: Free content, downloads, discussions, and more. http://solutions.newsforge.com/ibmarch.tmpl _______________________________________________ [email protected] To unsubscribe, use the last form field at: https://lists.sourceforge.net/lists/listinfo/linux-usb-devel
