From: Maulik Shah <mkshah@codeaurora.org>
To: andy.gross@linaro.org, david.brown@linaro.org,
linux-arm-msm@vger.kernel.org
Cc: linux-kernel@vger.kernel.org, linux-pm@vger.kernel.org,
bjorn.andersson@linaro.org, evgreen@chromium.org,
dianders@chromium.org, swboyd@chromium.org,
rnayak@codeaurora.org, ilina@codeaurora.org,
lsrao@codeaurora.org, mkshah@codeaurora.org
Subject: [PATCH 0/2] Introduce SoC sleep stats driver
Date: Thu, 8 Aug 2019 11:42:26 +0530 [thread overview]
Message-ID: <20190808061228.16573-1-mkshah@codeaurora.org> (raw)
Qualcomm Technologies Inc's (QTI) chipsets support SoC level low power modes.
SoCs Always On Processor/Resource Power Manager produces statistics of the SoC
sleep modes involving lowering or powering down of the backbone rails - Cx and
Mx and the oscillator clock, XO.
Statistics includes SoC sleep mode type, number of times LPM entered, time of
last entry, exit, and accumulated sleep duration.
This series adds a driver to read the stats produced by remote processor and
exports using sysfs.
Maulik Shah (2):
dt-bindings: Introduce soc sleep stats bindings for Qualcomm SoCs
drivers: qcom: Add SoC sleep stats driver
.../bindings/soc/qcom/soc-sleep-stats.txt | 36 +++
drivers/soc/qcom/Kconfig | 9 +
drivers/soc/qcom/Makefile | 1 +
drivers/soc/qcom/soc_sleep_stats.c | 249 ++++++++++++++++++
4 files changed, 295 insertions(+)
create mode 100644 Documentation/devicetree/bindings/soc/qcom/soc-sleep-stats.txt
create mode 100644 drivers/soc/qcom/soc_sleep_stats.c
--
QUALCOMM INDIA, on behalf of Qualcomm Innovation Center, Inc. is a member of the Code Aurora Forum, hosted by The Linux Foundation.
next reply other threads:[~2019-08-08 6:13 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-08-08 6:12 Maulik Shah [this message]
2019-08-08 6:12 ` [PATCH 1/2] dt-bindings: Introduce soc sleep stats bindings for Qualcomm SoCs Maulik Shah
2019-08-08 16:20 ` Stephen Boyd
2020-02-21 5:57 ` Maulik Shah
2019-08-08 6:12 ` [PATCH 2/2] drivers: qcom: Add SoC sleep stats driver Maulik Shah
2019-08-08 18:40 ` Stephen Boyd
2020-02-21 6:04 ` Maulik Shah
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=20190808061228.16573-1-mkshah@codeaurora.org \
--to=mkshah@codeaurora.org \
--cc=andy.gross@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=david.brown@linaro.org \
--cc=dianders@chromium.org \
--cc=evgreen@chromium.org \
--cc=ilina@codeaurora.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-pm@vger.kernel.org \
--cc=lsrao@codeaurora.org \
--cc=rnayak@codeaurora.org \
--cc=swboyd@chromium.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;
as well as URLs for NNTP newsgroup(s).