On Thu, Jul 4, 2013 at 8:32 AM, Daniel Drake <dsd@xxxxxxxxxx> wrote: > I cannot see how the driver behaviour matches the above description > for when the card is removed as the system is suspended. For example I > cannot see where the SHUTDOWN command gets sent in such cases. > > Also, at which point do we wait upon all async commands to complete > before shutting down? I walked through all the driver code in the > codepaths hit when the card is removed as the system is going into > suspend, and I found no such point. (This is why interrupts then > arrive later, because those commands are completing.) Also, from a more general standpoint, I would say it is bad practice/design to leave an interrupt handler running but in a state where it does not ACK interrupts. You're just asking for trouble. If you really don't expect interrupts beyond a certain point, and bad things would happen if interrupts *were* to arrive for any valid or invalid reason, disable the interrupt and remove the handler at that point. Daniel -- To unsubscribe from this list: send the line "unsubscribe linux-wireless" in the body of a message to majordomo@xxxxxxxxxxxxxxx More majordomo info at http://vger.kernel.org/majordomo-info.html
