From: Simon Glass <sjg@chromium.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
Cc: Andy Gross <agross@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Stephen Boyd <sboyd@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Rob Herring <robh+dt@kernel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@linaro.org>,
Taniya Das <quic_tdas@quicinc.com>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: Re: [PATCH v3 0/8] clk: qcom: msm8996: add support for the CBF clock
Date: Fri, 20 Jan 2023 08:08:07 -0700 [thread overview]
Message-ID: <CAPnjgZ3MQ4E_3n_Z881QsdO-zELPkLaCm0cOFwz6Fds+u73OWg@mail.gmail.com> (raw)
In-Reply-To: <20230120061417.2623751-1-dmitry.baryshkov@linaro.org>
Hi Dmitry,
On Thu, 19 Jan 2023 at 23:14, Dmitry Baryshkov
<dmitry.baryshkov@linaro.org> wrote:
>
> On MSM8996 two CPU clusters are interconnected using the Core Bus
> Fabric (CBF). In order for the CPU clusters to function properly, it
> should be clocked following the core's frequencies to provide adequate
> bandwidth. On the other hand the CBF's clock rate can be used by other
> drivers (e.g. by the pending SPDM driver to provide input on the CPU
> performance).
>
> Thus register CBF as a clock (required for CPU to boot) and add a tiny
> interconnect layer on top of it to let cpufreq/opp scale the CBF clock.
>
> Dependencies: [1]
>
> [1] https://lore.kernel.org/linux-arm-msm/20230111191453.2509468-1-dmitry.baryshkov@linaro.org/
>
> Changes since v2:
> - Added interconnect-related bindings
> - Switched CPU and CBF clocks to RPM_SMD_XO_A_CLK_SRC
>
> Changes since v1:
> - Relicensed schema to GPL-2.0 + BSD-2-Clause (Krzysztof)
> - Changed clock driver to use parent_hws (Konrad)
> - Fixed indentation in CBF clock driver (Konrad)
> - Changed MODULE_LICENSE of CBF clock driver to GPL from GPL-v2
> - Switched CBF to use RPM_SMD_XO_CLK_SRC as one of the parents
> - Enabled RPM_SMD_XO_CLK_SRC on msm8996 platform and switch to it from
> RPM_SMD_BB_CLK1 clock
>
> Dmitry Baryshkov (8):
> dt-bindings: clock: qcom,msm8996-cbf: Describe the MSM8996 CBF clock
> controller
> dt-bindints: interconnect/msm8996-cbf: add defines to be used by CBF
> clk: qcom: add msm8996 Core Bus Framework (CBF) support
> clk: qcom: cbf-msm8996: scale CBF clock according to the CPUfreq
> clk: qcom: smd-rpm: provide RPM_SMD_XO_CLK_SRC on MSM8996 platform
> arm64: qcom: dts: msm8996 switch from RPM_SMD_BB_CLK1 to
> RPM_SMD_XO_CLK_SRC
> arm64: dts: qcom: msm8996: add CBF device entry
> arm64: dts: qcom: msm8996: scale CBF clock according to the CPUfreq
>
> .../bindings/clock/qcom,msm8996-cbf.yaml | 53 ++
> arch/arm64/boot/dts/qcom/msm8996.dtsi | 72 ++-
> drivers/clk/qcom/Makefile | 2 +-
> drivers/clk/qcom/clk-cbf-8996.c | 458 ++++++++++++++++++
> drivers/clk/qcom/clk-smd-rpm.c | 2 +
> .../interconnect/qcom,msm8996-cbf.h | 12 +
> 6 files changed, 591 insertions(+), 8 deletions(-)
> create mode 100644 Documentation/devicetree/bindings/clock/qcom,msm8996-cbf.yaml
> create mode 100644 drivers/clk/qcom/clk-cbf-8996.c
> create mode 100644 include/dt-bindings/interconnect/qcom,msm8996-cbf.h
>
> --
> 2.39.0
>
Could you please tell me which dev board this is targeting and where I
can get one? Also could you please point me to the SoC documentation?
Thanks,
Simon
next prev parent reply other threads:[~2023-01-20 15:08 UTC|newest]
Thread overview: 22+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-01-20 6:14 [PATCH v3 0/8] clk: qcom: msm8996: add support for the CBF clock Dmitry Baryshkov
2023-01-20 6:14 ` [PATCH v3 1/8] dt-bindings: clock: qcom,msm8996-cbf: Describe the MSM8996 CBF clock controller Dmitry Baryshkov
2023-01-20 6:14 ` [PATCH v3 2/8] dt-bindints: interconnect/msm8996-cbf: add defines to be used by CBF Dmitry Baryshkov
2023-01-20 8:05 ` Krzysztof Kozlowski
2023-01-20 6:14 ` [PATCH v3 3/8] clk: qcom: add msm8996 Core Bus Framework (CBF) support Dmitry Baryshkov
2023-01-20 6:14 ` [PATCH v3 4/8] clk: qcom: cbf-msm8996: scale CBF clock according to the CPUfreq Dmitry Baryshkov
2023-01-20 11:13 ` Konrad Dybcio
2023-01-20 22:11 ` Stephen Boyd
2023-01-20 22:53 ` Dmitry Baryshkov
2023-01-25 21:40 ` Stephen Boyd
2023-01-26 8:20 ` Dmitry Baryshkov
2023-01-27 18:19 ` Dmitry Baryshkov
2023-01-20 6:14 ` [PATCH v3 5/8] clk: qcom: smd-rpm: provide RPM_SMD_XO_CLK_SRC on MSM8996 platform Dmitry Baryshkov
2023-01-20 6:14 ` [PATCH v3 6/8] arm64: qcom: dts: msm8996 switch from RPM_SMD_BB_CLK1 to RPM_SMD_XO_CLK_SRC Dmitry Baryshkov
2023-01-20 6:14 ` [PATCH v3 7/8] arm64: dts: qcom: msm8996: add CBF device entry Dmitry Baryshkov
2023-01-20 11:14 ` Konrad Dybcio
2023-01-20 6:14 ` [PATCH v3 8/8] arm64: dts: qcom: msm8996: scale CBF clock according to the CPUfreq Dmitry Baryshkov
2023-01-20 15:08 ` Simon Glass [this message]
2023-01-20 22:18 ` [PATCH v3 0/8] clk: qcom: msm8996: add support for the CBF clock Dmitry Baryshkov
2023-01-20 22:22 ` Simon Glass
2023-01-20 22:34 ` Konrad Dybcio
2023-02-09 4:22 ` (subset) " 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=CAPnjgZ3MQ4E_3n_Z881QsdO-zELPkLaCm0cOFwz6Fds+u73OWg@mail.gmail.com \
--to=sjg@chromium.org \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.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=quic_tdas@quicinc.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).