On Fri, 18 Sep 2009, Sarah Sharp wrote: > Make the USB core check the bandwidth when switching from one > interface alternate setting to another. Also check the bandwidth > when resetting a configuration (so that alt setting 0 is used). If > this check fails, the device's state is unchanged. If the device > refuses the new alt setting, re-instate the old alt setting in the > host controller hardware. > > I'm not entirely sure how to handle this race condition: > > Device A has one interface with two alt settings: > alt setting 0 has an interrupt endpoint with max packet size 32 > alt setting 1 has an interrupt endpoint with max packet size 64 > > Device A currently uses alt setting 1, but the driver wants to switch > back to alt setting 0. > > 1. USB core sets up alt setting 0 for device A, which succeeds on > the xHCI hardware side. > 2. A new USB device gets plugged in, and consumes the rest of the bus > bandwidth. Or another driver asks for a different alt setting that > consumes more bandwidth. > 3. USB core sends the USB_REQ_SET_INTERFACE control transfer, which > fails due to electrical noise. > > If the USB core tries to re-instate alt setting 1, the xHCI hardware > will reject it because it takes up too much bandwidth. So it seems > like there needs to be some sort of bus lock whenever the USB core > starts to install a new configuration or alt setting. Alternatively when switching configurations or altsettings, you could temporarily reserve the maximum of the old and the new bandwidths. Then after the switch succeeded or failed, you could release any excess bandwidth. 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
