The remoteproc framework keeps interrupts disabled until it powers on a remote proc to prevent spurious interrupts. There is a case where the remote proc can finish booting before remoteproc enables the interrupt. If this happens, the remoteproc framework will miss the notification and eventually timeout waiting for the remoteproc to finish "booting". Add support into smp2p to retrigger an interrupt if it was missed while the interrupt was disabled. The interrupt should retrigger once the interrupt is enabled. This will make the bootup sequence for remoteproc less racy. Chris Lew (3): soc: qcom: smp2p: Introduce pending state for virtual irq soc: qcom: smp2p: Add proper retrigger detection soc: qcom: smp2p: Add memory barrier for irq_pending Tao Zhang (1): soc: qcom: smp2p: Add remote_id into irq name drivers/soc/qcom/smp2p.c | 42 ++++++++++++++++++++++++++++++++++++------ 1 file changed, 36 insertions(+), 6 deletions(-) -- 2.7.4
