From: Taniya Das <quic_tdas@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>, Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Philipp Zabel <p.zabel@pengutronix.de>,
Konrad Dybcio <konradybcio@kernel.org>
Cc: <linux-arm-msm@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH v2 07/11] clk: qcom: rpmh: add support for SAR2130P
Date: Tue, 22 Oct 2024 12:03:57 +0530 [thread overview]
Message-ID: <73abe2b9-ad72-449f-b3e3-a96128cf75a4@quicinc.com> (raw)
In-Reply-To: <20241021-sar2130p-clocks-v2-7-383e5eb123a2@linaro.org>
On 10/21/2024 4:00 PM, Dmitry Baryshkov wrote:
> Define clocks as supported by the RPMh on the SAR2130P platform. It
> seems that on this platform RPMh models only CXO clock.
>
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/clk/qcom/clk-rpmh.c | 11 +++++++++++
> 1 file changed, 11 insertions(+)
>
> diff --git a/drivers/clk/qcom/clk-rpmh.c b/drivers/clk/qcom/clk-rpmh.c
> index 4acde937114af3d7fdc15f3d125a72d42d0fde21..8cb15430d0171a8ed6b05e51d1901af63a4564c4 100644
> --- a/drivers/clk/qcom/clk-rpmh.c
> +++ b/drivers/clk/qcom/clk-rpmh.c
> @@ -389,6 +389,16 @@ DEFINE_CLK_RPMH_BCM(ipa, "IP0");
> DEFINE_CLK_RPMH_BCM(pka, "PKA0");
> DEFINE_CLK_RPMH_BCM(qpic_clk, "QP0");
>
> +static struct clk_hw *sar2130p_rpmh_clocks[] = {
> + [RPMH_CXO_CLK] = &clk_rpmh_bi_tcxo_div1.hw,
> + [RPMH_CXO_CLK_A] = &clk_rpmh_bi_tcxo_div1_ao.hw,
> +};
> +
Dimtry, could you please add these clocks as well?
DEFINE_CLK_RPMH_VRM-- > rf_clk1, rf_clk1_ao, "clka1", 1
DEFINE_CLK_RPMH_VRM --> ln_bb_clk7, ln_bb_clk7_ao, "clka7", 2
DEFINE_CLK_RPMH_VRM --> ln_bb_clk8, ln_bb_clk8_ao, "clka8", 4
DEFINE_CLK_RPMH_VRM --> ln_bb_clk9, ln_bb_clk9_ao, "clka9", 2
> +static const struct clk_rpmh_desc clk_rpmh_sar2130p = {
> + .clks = sar2130p_rpmh_clocks,
> + .num_clks = ARRAY_SIZE(sar2130p_rpmh_clocks),
> +};
> +
--
Thanks & Regards,
Taniya Das.
next prev parent reply other threads:[~2024-10-22 6:34 UTC|newest]
Thread overview: 19+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-10-21 10:30 [PATCH v2 00/11] clk: qcom: add support for clock controllers on the SAR2130P platform Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 01/11] dt-bindings: clock: qcom,rpmhcc: Add SAR2130P compatible Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 02/11] dt-bindings: clock: qcom: document SAR2130P Global Clock Controller Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 03/11] dt-bindings: clock: qcom,sm8550-tcsr: Add SAR2130P compatible Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 04/11] dt-bindings: clock: qcom,sm8550-dispcc: " Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 05/11] dt-bindings: clk: qcom,sm8450-gpucc: add SAR2130P compatibles Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 06/11] clk: qcom: rcg2: add clk_rcg2_shared_floor_ops Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 07/11] clk: qcom: rpmh: add support for SAR2130P Dmitry Baryshkov
2024-10-22 6:33 ` Taniya Das [this message]
2024-10-22 9:42 ` Dmitry Baryshkov
2024-10-25 14:53 ` Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 08/11] clk: qcom: add support for GCC on SAR2130P Dmitry Baryshkov
2024-10-22 7:10 ` Taniya Das
2024-10-21 10:30 ` [PATCH v2 09/11] clk: qcom: tcsrcc-sm8550: add SAR2130P support Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 10/11] clk: qcom: dispcc-sm8550: enable support for SAR2130P Dmitry Baryshkov
2024-10-21 10:30 ` [PATCH v2 11/11] clk: qcom: add SAR2130P GPU Clock Controller support Dmitry Baryshkov
2024-10-29 8:33 ` Taniya Das
2024-10-21 11:07 ` [PATCH v2 00/11] clk: qcom: add support for clock controllers on the SAR2130P platform Konrad Dybcio
2024-10-21 13:14 ` 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=73abe2b9-ad72-449f-b3e3-a96128cf75a4@quicinc.com \
--to=quic_tdas@quicinc.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.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=neil.armstrong@linaro.org \
--cc=p.zabel@pengutronix.de \
--cc=robh@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
all inboxes | Powered by JetHome®