From: Konrad Dybcio <konrad.dybcio@linaro.org>
To: Imran Shaik <quic_imrashai@quicinc.com>,
Andy Gross <agross@kernel.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>
Cc: Taniya Das <quic_tdas@quicinc.com>,
Melody Olvera <quic_molvera@quicinc.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org,
Jagadeesh Kona <quic_jkona@quicinc.com>,
Satya Priya Kakitapalli <quic_skakitap@quicinc.com>,
Ajit Pandey <quic_ajipan@quicinc.com>
Subject: Re: [PATCH V2 3/5] clk: qcom: gcc-qdu1000: Update GCC clocks as per the latest hw version
Date: Thu, 6 Jul 2023 12:59:59 +0200 [thread overview]
Message-ID: <7d335f1d-ef2c-ffe6-e364-c3dc47479929@linaro.org> (raw)
In-Reply-To: <05f3459f-a2cd-3e4d-bbc6-f0109dbae778@quicinc.com>
On 6.07.2023 12:51, Imran Shaik wrote:
>
>
> On 6/28/2023 4:36 PM, Konrad Dybcio wrote:
>> On 28.06.2023 11:28, Imran Shaik wrote:
>>> Add support for gcc_ddrss_ecpri_gsi_clk and update the GCC clkref clocks
>>> as per the latest hardware version of QDU1000 and QRU100 SoCs.
>>>
>>> Co-developed-by: Taniya Das <quic_tdas@quicinc.com>
>>> Signed-off-by: Taniya Das <quic_tdas@quicinc.com>
>>> Signed-off-by: Imran Shaik <quic_imrashai@quicinc.com>
>>> ---
[...]
>>> .enable_reg = 0x9c004,
>>> .enable_mask = BIT(0),
>>> .hw.init = &(const struct clk_init_data) {
>>> .name = "gcc_pcie_0_clkref_en",
>>> - .ops = &clk_branch_ops,
>>> + .ops = &clk_branch2_ops,
>> This sounds like a separate fix, clk_branch_ops seems to only concern
>> 10+yo chips.
>>
>> Konrad
>
> Sure, will split this patch and push the next series.
One more nit, I noticed that a lot of QUIC folks respond to the comments
to their revision-N and send revision-(N+1) like 5 seconds later..
This maybe does not concern this message, as all you did is said "ok willfix",
but if you have some sort of a company-wide "upstream best practices" board,
you may add something like "wait a bit to let others respond to your email"
Konrad
>
> Thanks,
> Imran
>
>>> },
>>> },
>>> };
>>> @@ -2274,14 +2293,13 @@ static struct clk_branch gcc_tsc_etu_clk = {
>>> static struct clk_branch gcc_usb2_clkref_en = {
>>> .halt_reg = 0x9c008,
>>> - .halt_bit = 31,
>>> - .halt_check = BRANCH_HALT_ENABLE,
>>> + .halt_check = BRANCH_HALT,
>>> .clkr = {
>>> .enable_reg = 0x9c008,
>>> .enable_mask = BIT(0),
>>> .hw.init = &(const struct clk_init_data) {
>>> .name = "gcc_usb2_clkref_en",
>>> - .ops = &clk_branch_ops,
>>> + .ops = &clk_branch2_ops,
>>> },
>>> },
>>> };
>>> @@ -2523,6 +2541,8 @@ static struct clk_regmap *gcc_qdu1000_clocks[] = {
>>> [GCC_AGGRE_NOC_ECPRI_GSI_CLK] = &gcc_aggre_noc_ecpri_gsi_clk.clkr,
>>> [GCC_PCIE_0_PHY_AUX_CLK_SRC] = &gcc_pcie_0_phy_aux_clk_src.clkr,
>>> [GCC_PCIE_0_PIPE_CLK_SRC] = &gcc_pcie_0_pipe_clk_src.clkr,
>>> + [GCC_GPLL1_OUT_EVEN] = &gcc_gpll1_out_even.clkr,
>>> + [GCC_DDRSS_ECPRI_GSI_CLK] = &gcc_ddrss_ecpri_gsi_clk.clkr,
>>> };
>>> static const struct qcom_reset_map gcc_qdu1000_resets[] = {
next prev parent reply other threads:[~2023-07-06 11:00 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-06-28 9:28 [PATCH V2 0/5] Update GCC clocks for QDU1000 and QRU1000 SoCs Imran Shaik
2023-06-28 9:28 ` [PATCH V2 1/5] dt-bindings: clock: " Imran Shaik
2023-06-28 10:18 ` Rob Herring
2023-06-28 15:50 ` Rob Herring
2023-06-28 9:28 ` [PATCH V2 2/5] clk: qcom: gcc-qdu1000: Fix gcc_pcie_0_pipe_clk_src clock handling Imran Shaik
2023-06-28 11:03 ` Konrad Dybcio
2023-06-28 9:28 ` [PATCH V2 3/5] clk: qcom: gcc-qdu1000: Update GCC clocks as per the latest hw version Imran Shaik
2023-06-28 11:06 ` Konrad Dybcio
2023-07-06 10:51 ` Imran Shaik
2023-07-06 10:59 ` Konrad Dybcio [this message]
2023-06-28 9:28 ` [PATCH V2 4/5] clk: qcom: gcc-qdu1000: Add support for GDSCs Imran Shaik
2023-06-28 11:08 ` Konrad Dybcio
2023-06-28 9:28 ` [PATCH V2 5/5] clk: qcom: gcc-qdu1000: Update the RCGs ops Imran Shaik
2023-06-28 11:08 ` Konrad Dybcio
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=7d335f1d-ef2c-ffe6-e364-c3dc47479929@linaro.org \
--to=konrad.dybcio@linaro.org \
--cc=agross@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=krzysztof.kozlowski+dt@linaro.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=quic_ajipan@quicinc.com \
--cc=quic_imrashai@quicinc.com \
--cc=quic_jkona@quicinc.com \
--cc=quic_molvera@quicinc.com \
--cc=quic_skakitap@quicinc.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