From: Bjorn Andersson <bjorn.andersson@linaro.org>
To: Arun Kumar Neelakantam <aneela@codeaurora.org>
Cc: clew@codeaurora.org, Andy Gross <agross@kernel.org>,
"open list:ARM/QUALCOMM SUPPORT" <linux-arm-msm@vger.kernel.org>,
open list <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH] soc: qcom: aoss: Use wake_up_all() instead of wake_up_interruptible_all()
Date: Tue, 11 Feb 2020 22:31:54 -0800 [thread overview]
Message-ID: <20200212063154.GO3948@builder> (raw)
In-Reply-To: <1579681417-1155-1-git-send-email-aneela@codeaurora.org>
On Wed 22 Jan 00:23 PST 2020, Arun Kumar Neelakantam wrote:
> During the probe the task is waiting in TASK_UNINTERRUPTIBLE state which
> cannot be woken-up by wake_up_interruptible_all() function.
>
> Use wake_up_all() to wake-up both TASK_UNINTERRUPTIBLE and
> TASK_INTERRUPTIBLE state tasks.
>
> Signed-off-by: Arun Kumar Neelakantam <aneela@codeaurora.org>
Applied
Regards,
Bjorn
> ---
> drivers/soc/qcom/qcom_aoss.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/soc/qcom/qcom_aoss.c b/drivers/soc/qcom/qcom_aoss.c
> index 006ac40..fe79661 100644
> --- a/drivers/soc/qcom/qcom_aoss.c
> +++ b/drivers/soc/qcom/qcom_aoss.c
> @@ -200,7 +200,7 @@ static irqreturn_t qmp_intr(int irq, void *data)
> {
> struct qmp *qmp = data;
>
> - wake_up_interruptible_all(&qmp->event);
> + wake_up_all(&qmp->event);
>
> return IRQ_HANDLED;
> }
> --
> 1.9.1
prev parent reply other threads:[~2020-02-12 6:31 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-22 8:23 [PATCH] soc: qcom: aoss: Use wake_up_all() instead of wake_up_interruptible_all() Arun Kumar Neelakantam
2020-02-12 6:31 ` Bjorn Andersson [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20200212063154.GO3948@builder \
--to=bjorn.andersson@linaro.org \
--cc=agross@kernel.org \
--cc=aneela@codeaurora.org \
--cc=clew@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.