From: Maulik Shah <quic_mkshah@quicinc.com>
To: Shawn Guo <shawn.guo@linaro.org>
Cc: Marc Zyngier <maz@kernel.org>,
Thomas Gleixner <tglx@linutronix.de>,
"Bjorn Andersson" <bjorn.andersson@linaro.org>,
Rob Herring <robh+dt@kernel.org>,
Loic Poulain <loic.poulain@linaro.org>,
<devicetree@vger.kernel.org>, <linux-arm-msm@vger.kernel.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 2/2] irqchip: Add Qualcomm MPM controller driver
Date: Tue, 30 Nov 2021 13:56:02 +0530 [thread overview]
Message-ID: <519ac97a-6bff-ee93-58c6-63559c3a6cb6@quicinc.com> (raw)
In-Reply-To: <20211129134459.GC10105@dragon>
Hi,
On 11/29/2021 7:15 PM, Shawn Guo wrote:
>> This is not limited to suspend, you will need to notify RPM during deepest
>> cpu idle state entry as well, since MPM may be monitoring interrupts in that
>> case too.
> Yeah, I was trying to test this MPM driver with cpuidle, but failed to
> see the SoC get into vlow/vmin state from cpuidle.
In a few cases SoC can enter vmin/vlow from cpuidle one is from static
screen on.
> Do you have any
> suggestion how I should test it properly?
Suspend resume (use "s2idle" and not "deep" mode on upstream kernel) is
one good method, but you will have to make sure all drivers have removed
votes on xo clock when entering suspend.
Also need to make sure other subsystem like modem is in power collaspe
(look at the internal master stats driver to know if other subsystems
entering to low power mode or not).
Thanks,
Maulik
next prev parent reply other threads:[~2021-11-30 8:26 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-26 9:35 [PATCH v2 0/2] Add Qualcomm MPM irqchip driver support Shawn Guo
2021-11-26 9:35 ` [PATCH v2 1/2] dt-bindings: interrupt-controller: Add Qualcomm MPM support Shawn Guo
2021-12-01 23:02 ` Rob Herring
2021-11-26 9:35 ` [PATCH v2 2/2] irqchip: Add Qualcomm MPM controller driver Shawn Guo
2021-11-26 15:13 ` Marc Zyngier
2021-11-26 19:19 ` Marc Zyngier
2021-11-29 13:33 ` Shawn Guo
2021-11-29 15:24 ` Marc Zyngier
2021-11-30 2:31 ` Shawn Guo
2021-11-30 8:42 ` Marc Zyngier
2021-11-30 9:17 ` Shawn Guo
2021-11-30 10:44 ` Marc Zyngier
2021-12-01 7:36 ` Shawn Guo
[not found] ` <2e821841-a921-3fda-9ee6-3d5127653033@quicinc.com>
2021-11-30 8:31 ` Shawn Guo
2021-11-30 8:52 ` Marc Zyngier
2021-11-30 8:54 ` Maulik Shah
2021-11-30 8:47 ` Marc Zyngier
2021-11-27 7:49 ` kernel test robot
2021-11-27 7:49 ` kernel test robot
2021-11-29 7:23 ` Maulik Shah
2021-11-29 13:45 ` Shawn Guo
2021-11-30 8:26 ` Maulik Shah [this message]
2021-11-30 8:44 ` Shawn Guo
2021-11-30 9:04 ` Maulik Shah
2021-11-30 9:26 ` Shawn Guo
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=519ac97a-6bff-ee93-58c6-63559c3a6cb6@quicinc.com \
--to=quic_mkshah@quicinc.com \
--cc=bjorn.andersson@linaro.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=maz@kernel.org \
--cc=robh+dt@kernel.org \
--cc=shawn.guo@linaro.org \
--cc=tglx@linutronix.de \
/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.