From: Shawn Guo <shawn.guo@linaro.org>
To: Stephen Boyd <sboyd@kernel.org>
Cc: Bjorn Andersson <bjorn.andersson@linaro.org>,
Loic Poulain <loic.poulain@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, Shawn Guo <shawn.guo@linaro.org>
Subject: [PATCH 0/3] clk: qcom: smd-rpm: Report enable state to framework
Date: Tue, 9 Nov 2021 10:25:55 +0800 [thread overview]
Message-ID: <20211109022558.14529-1-shawn.guo@linaro.org> (raw)
Currently the enable state of smd-rpm clocks are not properly reported
back to framework due to missing .is_enabled and .is_prepared hooks.
This causes a couple of issues.
- All those unused clocks are not voted for off, because framework has
no knowledge that they are unused. It becomes a problem for vlow
power mode support, as we do not have every single RPM clock claimed
and voted for off by client devices, and rely on clock framework to
disable those unused RPM clocks.
- The clk_summary in debugfs doesn't show a correct enable state for
RPM clocks.
Shawn Guo (3):
clk: qcom: smd-rpm: Mark clock enabled in clk_smd_rpm_handoff()
clk: qcom: smd-rpm: Add .is_enabled hook
clk: qcom: smd-rpm: Add .is_prepared hook
drivers/clk/qcom/clk-smd-rpm.c | 20 ++++++++++++++++++++
1 file changed, 20 insertions(+)
--
2.17.1
next reply other threads:[~2021-11-09 2:26 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-11-09 2:25 Shawn Guo [this message]
2021-11-09 2:25 ` [PATCH 1/3] clk: qcom: smd-rpm: Mark clock enabled in clk_smd_rpm_handoff() Shawn Guo
2021-11-09 2:25 ` [PATCH 2/3] clk: qcom: smd-rpm: Add .is_enabled hook Shawn Guo
2021-11-09 2:25 ` [PATCH 3/3] clk: qcom: smd-rpm: Add .is_prepared hook Shawn Guo
2021-11-09 10:26 ` [PATCH 0/3] clk: qcom: smd-rpm: Report enable state to framework Stephan Gerhold
2021-11-09 15:56 ` Bjorn Andersson
2021-11-10 13:15 ` Shawn Guo
2021-11-10 13:48 ` Bjorn Andersson
2021-11-11 9:39 ` Shawn Guo
2021-12-06 15:42 ` Bjorn Andersson
2021-11-10 14:09 ` Stephan Gerhold
2021-11-10 14:58 ` Bjorn Andersson
2021-12-09 9:10 ` Stephen Boyd
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=20211109022558.14529-1-shawn.guo@linaro.org \
--to=shawn.guo@linaro.org \
--cc=bjorn.andersson@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=sboyd@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 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).