From: Stephen Boyd <sboyd@codeaurora.org>
To: Kiran Gunda <kgunda@codeaurora.org>
Cc: gregkh@linuxfoundation.org,
Abhijeet Dharmapurikar <adharmap@codeaurora.org>,
Christophe JAILLET <christophe.jaillet@wanadoo.fr>,
Nicholas Troast <ntroast@codeaurora.org>,
linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org
Subject: Re: [PATCH V2 5/5] spmi: pmic-arb: use irq_chip callback to set spmi irq wakeup capability
Date: Mon, 10 Jul 2017 18:22:36 -0700 [thread overview]
Message-ID: <20170711012236.GN22780@codeaurora.org> (raw)
In-Reply-To: <1499690549-30765-6-git-send-email-kgunda@codeaurora.org>
On 07/10, Kiran Gunda wrote:
> Currently the driver sets the pmic arbiter core interrupt as wakeup capable
> irrespective of the child irqs which causes the system to wakeup
> unnecessarily. To fix this, set the core interrupt as wakeup capable
> only if any of the child irqs request for it. Do this by marking it as
> wakeup capable in the irq_set_wake callback.
>
> Signed-off-by: Kiran Gunda <kgunda@codeaurora.org>
> ---
Reviewed-by: Stephen Boyd <sboyd@codeaurora.org>
--
Qualcomm Innovation Center, Inc. is a member of Code Aurora Forum,
a Linux Foundation Collaborative Project
prev parent reply other threads:[~2017-07-11 1:22 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-07-10 12:42 [PATCH V2 0/5]: spmi: pmic-arb: Fixup patches Kiran Gunda
2017-07-10 12:42 ` [PATCH V2 1/5] spmi: pmic-arb: remove the read/write access checks Kiran Gunda
2017-07-10 12:42 ` [PATCH V2 2/5] spmi: pmic-arb: rename pa_xx to pmic_arb_xx and other code cleanup Kiran Gunda
2017-07-14 18:20 ` Stephen Boyd
2017-07-18 4:52 ` kgunda
2017-07-10 12:42 ` [PATCH V2 3/5] spmi: pmic-arb: replace the writel_relaxed with __raw_writel Kiran Gunda
2017-07-10 12:42 ` [PATCH V2 4/5] spmi: pmic-arb: return the value instead of passing by pointer Kiran Gunda
2017-07-10 12:42 ` [PATCH V2 5/5] spmi: pmic-arb: use irq_chip callback to set spmi irq wakeup capability Kiran Gunda
2017-07-11 1:22 ` Stephen Boyd [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=20170711012236.GN22780@codeaurora.org \
--to=sboyd@codeaurora.org \
--cc=adharmap@codeaurora.org \
--cc=christophe.jaillet@wanadoo.fr \
--cc=gregkh@linuxfoundation.org \
--cc=kgunda@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=ntroast@codeaurora.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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox