> > - flush any pending data > > - handle any line discipline shutdown > > - fix up the carrier state > > OK, I see. Can we get away at least with ignoring throttle/unthrottle > if a shutdown has already begun? That depends how you implement flow control and hardware flow control lines in the driver. Assuming you remember to correct the hardware flow lines when initialising so you don't leave the hardware flow signals as "throttled" I don't see any reason for a specific driver to care. It seems to me to be mostly an implementation thing - it may also of course be that the best time to do the final hardware takedown on USB is the async callback made after the final kref is dropped ? Alan -- 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
