From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: Marijn Suijten <marijn.suijten@somainline.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
Stephan Gerhold <stephan@gerhold.net>,
Konrad Dybcio <konrad.dybcio@linaro.org>
Subject: [PATCH 0/2] Add read-only RCG2 ops
Date: Mon, 12 Jun 2023 11:22:46 +0200 [thread overview]
Message-ID: <20230612-topic-rcg2_ro-v1-0-e7d824aeb628@linaro.org> (raw)
Some of the clocks are managed by remote cores and we're not supposed
to alter their parameters. Monitoring them may still be useful, e.g.
for getting the correct rates of their children. This series attempts
to solve this problem without compromising on either of them.
Signed-off-by: Konrad Dybcio <konrad.dybcio@linaro.org>
---
Konrad Dybcio (2):
clk: qcom: rcg2: Introduce read-only RCG2 ops
clk: qcom: gcc-msm8996: Use read-only RCG ops for RPM bus clocks
drivers/clk/qcom/clk-rcg.h | 1 +
drivers/clk/qcom/clk-rcg2.c | 8 ++++++++
drivers/clk/qcom/gcc-msm8996.c | 6 +++---
3 files changed, 12 insertions(+), 3 deletions(-)
---
base-commit: 53ab6975c12d1ad86c599a8927e8c698b144d669
change-id: 20230612-topic-rcg2_ro-1450a076eda9
Best regards,
--
Konrad Dybcio <konrad.dybcio@linaro.org>
next reply other threads:[~2023-06-12 9:28 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-12 9:22 Konrad Dybcio [this message]
2023-06-12 9:22 ` [PATCH 1/2] clk: qcom: rcg2: Introduce read-only RCG2 ops Konrad Dybcio
2023-06-12 9:22 ` [PATCH 2/2] clk: qcom: gcc-msm8996: Use read-only RCG ops for RPM bus clocks Konrad Dybcio
2023-06-12 10:17 ` Stephan Gerhold
2023-06-12 11:46 ` Konrad Dybcio
2023-06-12 12:23 ` Stephan Gerhold
2023-06-12 12:25 ` Konrad Dybcio
2023-06-13 17:56 ` Bjorn Andersson
2023-06-13 17:54 ` Konrad Dybcio
2023-07-31 11:01 ` Konrad Dybcio
2023-08-24 10:27 ` Konrad Dybcio
2023-08-24 11:32 ` Dmitry Baryshkov
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=20230612-topic-rcg2_ro-v1-0-e7d824aeb628@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.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=marijn.suijten@somainline.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=stephan@gerhold.net \
/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