[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <161647039218.3012082.1225143087605342937@swboyd.mtv.corp.google.com>
Date: Mon, 22 Mar 2021 20:33:12 -0700
From: Stephen Boyd <swboyd@...omium.org>
To: Deepak Kumar Singh <deesin@...eaurora.org>,
bjorn.andersson@...aro.org, clew@...eaurora.org
Cc: linux-kernel@...r.kernel.org, linux-arm-msm@...r.kernel.org,
linux-remoteproc@...r.kernel.org,
Deepak Kumar Singh <deesin@...eaurora.org>,
Andy Gross <agross@...nel.org>
Subject: Re: [PATCH V1 1/1] soc: qcom: smp2p: Add enable_irq_wake to SMP2P IRQ
Quoting Deepak Kumar Singh (2021-03-18 11:37:04)
> SMP2P interrupts are expected to wake the processor from suspend.
> Use enable_irq_wake to mark it wakeup capable from suspend.
>
> Signed-off-by: Chris Lew <clew@...eaurora.org>
> Signed-off-by: Deepak Kumar Singh <deesin@...eaurora.org>
> ---
> drivers/soc/qcom/smp2p.c | 1 +
> 1 file changed, 1 insertion(+)
>
> diff --git a/drivers/soc/qcom/smp2p.c b/drivers/soc/qcom/smp2p.c
> index 2df4883..df47ee6 100644
> --- a/drivers/soc/qcom/smp2p.c
> +++ b/drivers/soc/qcom/smp2p.c
> @@ -538,6 +538,7 @@ static int qcom_smp2p_probe(struct platform_device *pdev)
> goto unwind_interfaces;
> }
>
> + enable_irq_wake(irq);
>
Can this use device_init_wakeup() and dev_pm_set_wake_irq() instead? I
think that will help us recognize that this irq woke up the CPU and
allow userspace to indicate that it doesn't want to get this wakeup for
some reason.
> return 0;
>
Powered by blists - more mailing lists