From: Kathiravan T <quic_kathirav@quicinc.com>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
<krzysztof.kozlowski@linaro.org>, <agross@kernel.org>,
<andersson@kernel.org>, <konrad.dybcio@linaro.org>,
<robh+dt@kernel.org>, <krzysztof.kozlowski+dt@linaro.org>,
<mturquette@baylibre.com>, <sboyd@kernel.org>,
<linus.walleij@linaro.org>, <catalin.marinas@arm.com>,
<will@kernel.org>, <shawnguo@kernel.org>, <arnd@arndb.de>,
<marcel.ziswiler@toradex.com>, <nfraprado@collabora.com>,
<robimarko@gmail.com>, <quic_gurus@quicinc.com>,
<linux-arm-msm@vger.kernel.org>, <devicetree@vger.kernel.org>,
<linux-kernel@vger.kernel.org>, <linux-clk@vger.kernel.org>,
<linux-gpio@vger.kernel.org>,
<linux-arm-kernel@lists.infradead.org>
Cc: <quic_varada@quicinc.com>, <quic_srichara@quicinc.com>
Subject: Re: [PATCH V3 5/9] clk: qcom: add Global Clock controller (GCC) driver for IPQ5332 SoC
Date: Tue, 7 Feb 2023 09:59:57 +0530 [thread overview]
Message-ID: <4bcf4bd9-e638-22a2-044d-47fd5fd5d104@quicinc.com> (raw)
In-Reply-To: <019bf6ae-cdc4-8fa7-4d76-c39403d93b34@linaro.org>
Thanks Dmirty for the review!
On 2/6/2023 3:26 PM, Dmitry Baryshkov wrote:
> On 06/02/2023 09:12, Kathiravan T wrote:
> > Add support for the global clock controller found on IPQ5332 SoC.
> >
> > Signed-off-by: Kathiravan T <quic_kathirav@quicinc.com>
> > ---
> > Changes in V3:
> > - As I mentined the bindings, changes need to be done in V2 got
> > missed out and same has been done in V3, to call out
> > specifically dropped the CLK_IS_CRITICAL and dropped the
> > gcc_apss_ahb_clk, its source clock and gcc_apss_axi_clk
> > - Used gcc_parent_data_xo wherever applicable and dropped the
> > duplicate entries
> > - dropped the unused parent_map_10 and parent_data_10
> > - Used qcom_cc_probe instead of qcom_cc_really_probe
> > Changes in V2:
> > - Added the 'dependes on' for Kconfig symbol
> > - Dropped the CLK_IS_CRITICAL flag throughout the file
> > - Dropped the gcc_apss_ahb_clk and gcc_apss_axi_clk as these are
> > managed by bootloaders
>
>
> [skipped]
>
> > +static const struct freq_tbl ftbl_gcc_pcie_aux_clk_src[] = {
> > + F(2000000, P_XO, 12, 0, 0),
> > + { }
> > +};
> > +
> > +static struct clk_rcg2 gcc_pcie_aux_clk_src = {
> > + .cmd_rcgr = 0x28004,
> > + .mnd_width = 16,
> > + .hid_width = 5,
> > + .parent_map = gcc_parent_map_6,
> > + .freq_tbl = ftbl_gcc_pcie_aux_clk_src,
> > + .clkr.hw.init = &(const struct clk_init_data){
> > + .name = "gcc_pcie_aux_clk_src",
> > + .parent_data = gcc_parent_data_6,
> > + .num_parents = ARRAY_SIZE(gcc_parent_data_6),
> > + .ops = &clk_rcg2_ops,
> > + },
> > +};
> > +
> > +static struct clk_regmap_mux pcie3x2_pipe_clk_src = {
> > + .reg = 0x28064,
> > + .shift = 8,
> > + .width = 2,
> > + .parent_map = gcc_parent_map_14,
> > + .clkr = {
> > + .hw.init = &(struct clk_init_data){
> > + .name = "pcie3x2_phy_pipe_clk_src",
> > + .parent_data = gcc_parent_data_14,
> > + .num_parents = ARRAY_SIZE(gcc_parent_data_14),
> > + .ops = &clk_regmap_mux_closest_ops,
>
> Should we use clk_regmap_phy_mux_ops here instead?
Sure, I will check this one. Also looking at the commit, 74e4190cdebe
("clk: qcom: regmap: add PHY clock source implementation"), looks like I
can use the clk_regmap_phy_mux struct instead of clk_regmap_mux. I will
check into this and update accordingly.
>
> > + .flags = CLK_SET_RATE_PARENT,
> > + },
> > + },
> > +};
> > +
> > +static struct clk_regmap_mux pcie3x1_0_pipe_clk_src = {
> > + .reg = 0x29064,
> > + .shift = 8,
> > + .width = 2,
> > + .parent_map = gcc_parent_map_15,
> > + .clkr = {
> > + .hw.init = &(struct clk_init_data){
> > + .name = "pcie3x1_0_phy_pipe_clk_src",
> > + .parent_data = gcc_parent_data_15,
> > + .num_parents = ARRAY_SIZE(gcc_parent_data_15),
> > + .ops = &clk_regmap_mux_closest_ops,
>
> And clk_regmap_phy_mux_ops here too?
Ack.
>
> > + .flags = CLK_SET_RATE_PARENT,
> > + },
> > + },
> > +};
> > +
> > +static struct clk_regmap_mux pcie3x1_1_pipe_clk_src = {
> > + .reg = 0x2A064,
> > + .shift = 8,
> > + .width = 2,
> > + .parent_map = gcc_parent_map_16,
> > + .clkr = {
> > + .hw.init = &(struct clk_init_data){
> > + .name = "pcie3x1_1_phy_pipe_clk_src",
> > + .parent_data = gcc_parent_data_16,
> > + .num_parents = ARRAY_SIZE(gcc_parent_data_16),
> > + .ops = &clk_regmap_mux_closest_ops,
>
> And here?
Ack.
>
> > + .flags = CLK_SET_RATE_PARENT,
> > + },
> > + },
> > +};
> > +
>
> [skipped]
>
>
> > +
> > +static struct clk_branch gcc_pcie3x1_0_pipe_clk = {
> > + .halt_reg = 0x29068,
> > + .halt_check = BRANCH_HALT_DELAY,
> > + .clkr = {
> > + .enable_reg = 0x29068,
> > + .enable_mask = BIT(0),
> > + .hw.init = &(const struct clk_init_data){
> > + .name = "gcc_pcie3x1_0_pipe_clk",
> > + .parent_names = (const char *[]){
> > + "pcie3x1_0_pipe_clk_src"
> > + },
>
> Nooo. No parent_names please. You have several of them in the driver
I missed this. I will fix in next spin.
>
> > + .num_parents = 1,
> > + .flags = CLK_SET_RATE_PARENT,
> > + .ops = &clk_branch2_ops,
> > + },
> > + },
> > +};
> > +
>
next prev parent reply other threads:[~2023-02-07 4:30 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-02-06 7:12 [PATCH V3 0/9] Add minimal boot support for IPQ5332 Kathiravan T
2023-02-06 7:12 ` [PATCH V3 1/9] dt-bindings: pinctrl: qcom: add IPQ5332 pinctrl Kathiravan T
2023-02-06 8:26 ` Krzysztof Kozlowski
2023-02-06 7:12 ` [PATCH V3 2/9] pinctrl: qcom: Introduce IPQ5332 TLMM driver Kathiravan T
2023-02-07 3:34 ` Bjorn Andersson
2023-02-06 7:12 ` [PATCH V3 3/9] clk: qcom: Add STROMER PLUS PLL type for IPQ5332 Kathiravan T
2023-02-06 7:12 ` [PATCH V3 4/9] dt-bindings: clock: Add Qualcomm IPQ5332 GCC Kathiravan T
2023-02-06 8:26 ` Krzysztof Kozlowski
2023-02-06 9:52 ` Dmitry Baryshkov
2023-02-07 4:26 ` Kathiravan T
2023-02-07 10:05 ` Dmitry Baryshkov
2023-02-06 7:12 ` [PATCH V3 6/9] dt-bindings: qcom: add ipq5332 boards Kathiravan T
2023-02-06 8:27 ` Krzysztof Kozlowski
2023-02-06 7:12 ` [PATCH V3 7/9] dt-bindings: firmware: qcom,scm: document IPQ5332 SCM Kathiravan T
2023-02-06 7:12 ` [PATCH V3 8/9] arm64: dts: qcom: add IPQ5332 SoC and MI01.2 board support Kathiravan T
2023-02-06 7:12 ` [PATCH V3 9/9] arm64: defconfig: Enable IPQ5332 SoC base configs Kathiravan T
2023-02-06 9:53 ` Dmitry Baryshkov
[not found] ` <20230206071217.29313-6-quic_kathirav@quicinc.com>
2023-02-06 9:56 ` [PATCH V3 5/9] clk: qcom: add Global Clock controller (GCC) driver for IPQ5332 SoC Dmitry Baryshkov
2023-02-07 4:29 ` Kathiravan T [this message]
2023-02-07 3:41 ` Bjorn Andersson
2023-02-07 4:31 ` Kathiravan T
2023-02-06 11:25 ` [PATCH V3 0/9] Add minimal boot support for IPQ5332 Linus Walleij
2023-02-06 11:42 ` Kathiravan T
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=4bcf4bd9-e638-22a2-044d-47fd5fd5d104@quicinc.com \
--to=quic_kathirav@quicinc.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=arnd@arndb.de \
--cc=catalin.marinas@arm.com \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=krzysztof.kozlowski@linaro.org \
--cc=linus.walleij@linaro.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-gpio@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=marcel.ziswiler@toradex.com \
--cc=mturquette@baylibre.com \
--cc=nfraprado@collabora.com \
--cc=quic_gurus@quicinc.com \
--cc=quic_srichara@quicinc.com \
--cc=quic_varada@quicinc.com \
--cc=robh+dt@kernel.org \
--cc=robimarko@gmail.com \
--cc=sboyd@kernel.org \
--cc=shawnguo@kernel.org \
--cc=will@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