diff options
| author | Kevin Cernekee <[email protected]> | 2012-08-09 11:23:52 +0300 |
|---|---|---|
| committer | Felipe Balbi <[email protected]> | 2012-08-23 11:04:19 +0300 |
| commit | 974e9323deefbab923d7aa8f0e4bcf9066c2ec97 (patch) | |
| tree | 8498d854cb728eddb03b1cf71611e2da6e2c70dc /tools/perf/scripts/python | |
| parent | d3091cfff73ce44c6b0cb61b25074f0ac648604f (diff) | |
usb: gadget: udc-core: Race between disconnect/unbind and setup
usb_gadget_remove_driver() runs through a four-step sequence to shut down
the gadget driver. For the case of a composite gadget + at91 UDC, this
would look like:
udc->driver->disconnect(udc->gadget); // composite_disconnect()
usb_gadget_disconnect(udc->gadget); // at91_pullup(gadget, 0)
udc->driver->unbind(udc->gadget); // composite_unbind()
usb_gadget_udc_stop(udc->gadget, udc->driver); // at91_stop()
The UDC driver can receive SETUP packets from the host up until the
point when usb_gadget_disconnect() returns. On rare occasions, the
gadget driver may see this sequence:
udc->driver->disconnect(udc->gadget); // composite_disconnect()
udc->driver->setup(udc->gadget, &ctrl); // composite_setup()
udc->driver->unbind(udc->gadget); // composite_unbind()
Some gadget drivers, such as composite, assume this will never happen
and crash as a result.
The fix is to quiesce the UDC hardware (via usb_gadget_disconnect)
before running the gadget driver through the disconnect/unbind sequence.
Reviewed-by: Peter Chen <[email protected]>
Signed-off-by: Kevin Cernekee <[email protected]>
Signed-off-by: Felipe Balbi <[email protected]>
Diffstat (limited to 'tools/perf/scripts/python')
0 files changed, 0 insertions, 0 deletions