From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: "Satya Priya Kakitapalli (Temp)" <quic_skakitap@quicinc.com>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: dmitry.baryshkov@linaro.org, stable@vger.kernel.org,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: Re: [PATCH] clk: qcom: camcc-sc8280xp: Remove always-on GDSC hard-coding
Date: Sat, 20 Jul 2024 09:33:43 +0100 [thread overview]
Message-ID: <610efa39-e476-45ae-bd2b-3a0b8ea485dc@linaro.org> (raw)
In-Reply-To: <dd588276-8f1c-4389-7b3a-88f483b7072e@quicinc.com>
On 19/07/2024 08:25, Satya Priya Kakitapalli (Temp) wrote:
>>
>> What is the use-case to keep that clock always-on unless/util someone
>> wants camss ?
>>
>
> The clock also has dependency on MMCX rail, this rail anyway will be OFF
> until there is a use-case. So the clock will also be OFF.
arch/arm64/boot/dts/qcom/sc8280xp.dtsi
camcc: clock-controller@ad00000 {
power-domains = <&rpmhpd SC8280XP_MMCX>;
};
>
>
>> I've tested this patch on sc8280xp and it works just fine.
>>
>
> Is the cam_cc_gdsc_clk clock ON after the boot up?
I have no idea. Why does it matter ?
---
bod
next prev parent reply other threads:[~2024-07-20 8:33 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-15 14:59 [PATCH] clk: qcom: camcc-sc8280xp: Remove always-on GDSC hard-coding Bryan O'Donoghue
2024-07-17 6:32 ` Satya Priya Kakitapalli (Temp)
2024-07-17 8:49 ` Bryan O'Donoghue
2024-07-17 11:08 ` Satya Priya Kakitapalli (Temp)
2024-07-17 11:11 ` Bryan O'Donoghue
2024-07-19 7:25 ` Satya Priya Kakitapalli (Temp)
2024-07-20 8:33 ` Bryan O'Donoghue [this message]
2024-07-22 8:57 ` Satya Priya Kakitapalli (Temp)
2024-07-23 9:29 ` Bryan O'Donoghue
2024-07-23 11:37 ` Satya Priya Kakitapalli (Temp)
2024-07-23 11:49 ` Dmitry Baryshkov
2024-07-26 7:01 ` Satya Priya Kakitapalli (Temp)
2024-07-26 20:31 ` Bryan O'Donoghue
2024-07-29 10:57 ` Satya Priya Kakitapalli (Temp)
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=610efa39-e476-45ae-bd2b-3a0b8ea485dc@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=andersson@kernel.org \
--cc=dmitry.baryshkov@linaro.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=quic_skakitap@quicinc.com \
--cc=sboyd@kernel.org \
--cc=stable@vger.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