Vitaly Wool <vitalywool@xxxxxxxxx> writes: > Hi Kevin, > >> Therefore, what is ideally needed is the ability for A's suspend to >> simply call pm_runtime_suspend() so the subsystem can do the work. >> However, since runtime transitions are locked out by this time, that >> doesn't work. ÂIOW, what is needed is a way for a system suspend to say >> "please finish the runtime suspend that was already requested." >> >> What I've done to work around this in driver A is to manually check >> pm_runtime_suspended() and directly call the subsystem's runtime >> suspend/resume (patch below[1]. ÂNOTE, I've used the _noirq methods to >> ensure device A is available when device B needs it.) > > suppose this driver runs on a platform that has runtime PM disabled. > How is it going to work then? > Then pm_runtime_suspended() will be false, and the bus methods will suspend the device. Kevin -- 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
