From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Johan Hovold <johan@kernel.org>
Cc: Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Conor Dooley <conor+dt@kernel.org>,
Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH v5 03/12] clk: qcom: gcc-sm6375: Unregister critical clocks
Date: Thu, 4 Jan 2024 10:55:28 +0100 [thread overview]
Message-ID: <7f2f738b-a2a7-43ba-b63a-bba59e76bae4@linaro.org> (raw)
In-Reply-To: <ZZZt1fV9WYJ6P-xE@hovoldconsulting.com>
On 4.01.2024 09:35, Johan Hovold wrote:
> On Wed, Jan 03, 2024 at 02:36:01PM +0100, Konrad Dybcio wrote:
>> Some clocks need to be always-on, but we don't really do anything
>> with them, other than calling enable() once and telling Linux they're
>> enabled.
>>
>> Unregister them to save a couple of bytes and, perhaps more
>> importantly, allow for runtime suspend of the clock controller device,
>> as CLK_IS_CRITICAL prevents the latter.
>>
>> Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
>
>> @@ -3886,6 +3797,11 @@ static int gcc_sm6375_probe(struct platform_device *pdev)
>> qcom_branch_set_clk_en(regmap, 0x17028); /* GCC_CAMERA_XO_CLK */
>> qcom_branch_set_clk_en(regmap, 0x2b004); /* GCC_CPUSS_GNOC_CLK */
>> qcom_branch_set_clk_en(regmap, 0x1702c); /* GCC_DISP_XO_CLK */
>> + qcom_branch_set_clk_en(regmap, 0x17008); /* GCC_CAMERA_AHB_CLK */
>> + qcom_branch_set_clk_en(regmap, 0x1700c); /* GCC_DISP_AHB_CLK */
>> + qcom_branch_set_clk_en(regmap, 0x36004); /* GCC_GPU_CFG_AHB_CLK */
>> + qcom_branch_set_clk_en(regmap, 0x79004); /* GCC_SYS_NOC_CPUSS_AHB_CLK */
>> + qcom_branch_set_clk_en(regmap, 0x17004); /* GCC_VIDEO_AHB_CLK */
>
> Shouldn't you keep the above sorted by offset or at least try to group
> them by subsystem (e.g. keep the camera clocks together)?
Guess I assumed order-of-appearance sorting was fine when I made this
patch.
I can group it by hw block, though.
Konrad
next prev parent reply other threads:[~2024-01-04 9:55 UTC|newest]
Thread overview: 16+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-01-03 13:35 [PATCH v5 00/12] Unregister critical branch clocks + some RPM Konrad Dybcio
2024-01-03 13:35 ` [PATCH v5 01/12] clk: qcom: branch: Add a helper for setting the enable bit Konrad Dybcio
2024-01-03 13:36 ` [PATCH v5 02/12] clk: qcom: Use qcom_branch_set_clk_en() Konrad Dybcio
2024-01-04 8:30 ` Johan Hovold
2024-01-03 13:36 ` [PATCH v5 03/12] clk: qcom: gcc-sm6375: Unregister critical clocks Konrad Dybcio
2024-01-04 8:35 ` Johan Hovold
2024-01-04 9:55 ` Konrad Dybcio [this message]
2024-01-03 13:36 ` [PATCH v5 04/12] clk: qcom: gpucc-sm6375: " Konrad Dybcio
2024-01-03 13:36 ` [PATCH v5 05/12] clk: qcom: gpucc-sm6115: " Konrad Dybcio
2024-01-03 13:36 ` [PATCH v5 06/12] clk: qcom: gpucc-sm6115: Add runtime PM Konrad Dybcio
2024-01-03 13:36 ` [PATCH v5 07/12] clk: qcom: gcc-sm6115: Unregister critical clocks Konrad Dybcio
2024-01-03 13:36 ` [PATCH v5 08/12] clk: qcom: gcc-qcm2290: " Konrad Dybcio
2024-01-03 13:36 ` [PATCH v5 09/12] arm64: dts: qcom: sm6375: Add VDD_CX to GCC Konrad Dybcio
2024-01-03 13:36 ` [PATCH v5 10/12] arm64: dts: qcom: qcm2290: " Konrad Dybcio
2024-01-03 13:36 ` [PATCH v5 11/12] arm64: dts: qcom: sm6115: " Konrad Dybcio
2024-01-03 13:36 ` [PATCH v5 12/12] arm64: dts: qcom: sm6115: Add VDD_CX to GPU_CC Konrad Dybcio
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=7f2f738b-a2a7-43ba-b63a-bba59e76bae4@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=johan@kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marijn.suijten@somainline.org \
--cc=mturquette@baylibre.com \
--cc=robh+dt@kernel.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).