From: Bjorn Andersson <andersson@kernel.org>
To: linux-clk@vger.kernel.org, "Otto Pflüger" <otto.pflueger@abscue.de>
Cc: Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.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>,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 0/2] clk: qcom: gcc-msm8917: Enable GPLL0_SLEEP_CLK_SRC
Date: Sun, 13 Aug 2023 20:27:40 -0700 [thread overview]
Message-ID: <169198364319.2443702.10110671002846666656.b4-ty@kernel.org> (raw)
In-Reply-To: <20230802170317.205112-1-otto.pflueger@abscue.de>
On Wed, 02 Aug 2023 19:03:15 +0200, Otto Pflüger wrote:
> I left this clock disabled for some reason and this made GPLL0_EARLY
> report a zero rate because it has this clock set as the parent clock.
>
> This is fixed in this series by adding the clock to qcom,gcc-msm8917.h
> and the clock list. The clock definition is also changed to use the
> correct enable/disable operations for this type of clock.
>
> [...]
Applied, thanks!
[1/2] dt-bindings: clock: gcc-msm8917: Add definition for GPLL0_SLEEP_CLK_SRC
commit: 593576a369ec885275a1a368a6838844b78b4f35
[2/2] clk: qcom: gcc-msm8917: Enable GPLL0_SLEEP_CLK_SRC
commit: d863492886930a1a6f7c0d9dda8f728077b540f0
Best regards,
--
Bjorn Andersson <andersson@kernel.org>
prev parent reply other threads:[~2023-08-14 3:25 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-08-02 17:03 [PATCH 0/2] clk: qcom: gcc-msm8917: Enable GPLL0_SLEEP_CLK_SRC Otto Pflüger
2023-08-02 17:03 ` [PATCH 1/2] dt-bindings: clock: gcc-msm8917: Add definition for GPLL0_SLEEP_CLK_SRC Otto Pflüger
2023-08-03 15:53 ` Conor Dooley
2023-08-02 17:03 ` [PATCH 2/2] clk: qcom: gcc-msm8917: Enable GPLL0_SLEEP_CLK_SRC Otto Pflüger
2023-08-14 3:27 ` Bjorn Andersson [this message]
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=169198364319.2443702.10110671002846666656.b4-ty@kernel.org \
--to=andersson@kernel.org \
--cc=agross@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=otto.pflueger@abscue.de \
--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