From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] clk: qcom: gdsc: Add pm_runtime hooks
Date: Wed, 20 Nov 2024 17:09:08 +0000 [thread overview]
Message-ID: <7a52ca1f-303e-44ae-b750-6aaa521516c3@linaro.org> (raw)
In-Reply-To: <zhhna2wni4yqhnc2tqfc2ugril3h4kzbyr3ix6vpwrgghwytfa@kjfpff5zdl4z>
On 19/11/2024 15:34, Bjorn Andersson wrote:
> What I think you want is two things:
> 1) When you're accessing the registers, you want the clock controller's
> power-domain to be on.
> 2) When the client vote for a GDSC, you want to have the PM framework
> also ensure that parent power-domains are kept on.
> For the single case, this is handled by the pm_genpd_add_subdomain()
> call below. This, or something along those lines, seems like the
> appropriate solution.
Yes.
I'm finding with this patch reverted but, keeping the first patch that
it pretty much works as you'd want with the caveat that gdsc_register ->
gdsc_en -> gdsc_toggle fails the first time.
After that I see the GDSCs on/off as excpected
cat /sys/kernel/debug/pm_genpd/cam_cc_titan_top_gdsc/current_state
off-0
cat /sys/kernel/debug/pm_genpd/cam_cc_ife_0_gdsc/current_state
off-0
cam -c 1 --capture=10 --file
cat /sys/kernel/debug/pm_genpd/cam_cc_titan_top_gdsc/current_state
off-0
cat /sys/kernel/debug/pm_genpd/cam_cc_ife_0_gdsc/current_state
off-0
Perhaps we just need to fix the probe path @ gdsc_register()
---
bod
next prev parent reply other threads:[~2024-11-20 17:09 UTC|newest]
Thread overview: 25+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-11-18 2:24 [PATCH 0/2] clk: qcom: Add support for multiple power-domains for a clock controller Bryan O'Donoghue
2024-11-18 2:24 ` [PATCH 1/2] clk: qcom: common: Add support for power-domain attachment Bryan O'Donoghue
2024-11-18 13:03 ` Dmitry Baryshkov
2024-11-18 13:17 ` Bryan O'Donoghue
2024-11-18 22:17 ` Vladimir Zapolskiy
2024-11-18 22:52 ` Bryan O'Donoghue
2024-11-19 15:41 ` Bjorn Andersson
2024-11-20 16:49 ` Bryan O'Donoghue
2024-11-21 21:59 ` Dmitry Baryshkov
2024-11-21 23:25 ` Bryan O'Donoghue
2024-11-18 2:24 ` [PATCH 2/2] clk: qcom: gdsc: Add pm_runtime hooks Bryan O'Donoghue
2024-11-18 13:10 ` Dmitry Baryshkov
2024-11-18 13:19 ` Bryan O'Donoghue
2024-11-18 13:39 ` Dmitry Baryshkov
2024-11-18 13:47 ` Bryan O'Donoghue
2024-11-19 15:34 ` Bjorn Andersson
2024-11-20 17:09 ` Bryan O'Donoghue [this message]
2024-11-26 17:23 ` Bjorn Andersson
2024-11-26 23:45 ` Bryan O'Donoghue
2024-11-18 13:15 ` [PATCH 0/2] clk: qcom: Add support for multiple power-domains for a clock controller Dmitry Baryshkov
2024-11-18 13:22 ` Bryan O'Donoghue
2024-11-18 13:46 ` Bryan O'Donoghue
2024-11-19 6:08 ` Taniya Das
2024-11-19 9:46 ` Bryan O'Donoghue
2024-11-19 15:28 ` Bjorn Andersson
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=7a52ca1f-303e-44ae-b750-6aaa521516c3@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--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