From: Neil Armstrong <neil.armstrong@linaro.org>
To: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org, devicetree@vger.kernel.org
Subject: Re: [PATCH 1/7] clk: qcom: dispcc-sm8550: fix several supposed typos
Date: Wed, 17 Jul 2024 10:08:24 +0200 [thread overview]
Message-ID: <d60cd97b-a1da-4dbd-910d-92cd62762afd@linaro.org> (raw)
In-Reply-To: <20240717-dispcc-sm8550-fixes-v1-1-efb4d927dc9a@linaro.org>
Hi,
On 16/07/2024 23:13, Dmitry Baryshkov wrote:
> Fix seveal odd-looking places in SM8550's dispcc driver:
>
> - duplicate entries in disp_cc_parent_map_4 and disp_cc_parent_map_5
> - using &disp_cc_mdss_dptx0_link_div_clk_src as a source for
> disp_cc_mdss_dptx1_usb_router_link_intf_clk
>
> The SM8650 driver has been used as a reference.
>
> Fixes: 90114ca11476 ("clk: qcom: add SM8550 DISPCC driver")
> Signed-off-by: Dmitry Baryshkov <dmitry.baryshkov@linaro.org>
> ---
> drivers/clk/qcom/dispcc-sm8550.c | 6 +++---
> 1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/clk/qcom/dispcc-sm8550.c b/drivers/clk/qcom/dispcc-sm8550.c
> index 31ae46f180a5..09e4b1e40e20 100644
> --- a/drivers/clk/qcom/dispcc-sm8550.c
> +++ b/drivers/clk/qcom/dispcc-sm8550.c
> @@ -196,7 +196,7 @@ static const struct clk_parent_data disp_cc_parent_data_3[] = {
> static const struct parent_map disp_cc_parent_map_4[] = {
> { P_BI_TCXO, 0 },
> { P_DP0_PHY_PLL_LINK_CLK, 1 },
> - { P_DP1_PHY_PLL_VCO_DIV_CLK, 2 },
> + { P_DP0_PHY_PLL_VCO_DIV_CLK, 2 },
> { P_DP3_PHY_PLL_VCO_DIV_CLK, 3 },
> { P_DP1_PHY_PLL_VCO_DIV_CLK, 4 },
> { P_DP2_PHY_PLL_VCO_DIV_CLK, 6 },
I checked and it's the right fix. Acked
> @@ -213,7 +213,7 @@ static const struct clk_parent_data disp_cc_parent_data_4[] = {
>
> static const struct parent_map disp_cc_parent_map_5[] = {
> { P_BI_TCXO, 0 },
> - { P_DSI0_PHY_PLL_OUT_BYTECLK, 4 },
> + { P_DSI0_PHY_PLL_OUT_BYTECLK, 2 },
> { P_DSI1_PHY_PLL_OUT_BYTECLK, 4 },
> };
Same here, right fix. Acked
>
> @@ -1146,7 +1146,7 @@ static struct clk_branch disp_cc_mdss_dptx1_usb_router_link_intf_clk = {
> .hw.init = &(struct clk_init_data) {
> .name = "disp_cc_mdss_dptx1_usb_router_link_intf_clk",
> .parent_hws = (const struct clk_hw*[]) {
> - &disp_cc_mdss_dptx0_link_div_clk_src.clkr.hw,
> + &disp_cc_mdss_dptx1_link_div_clk_src.clkr.hw,
> },
> .num_parents = 1,
> .flags = CLK_SET_RATE_PARENT,
>
This one is NAK, I checked and on SM8550 the parent of disp_cc_mdss_dptx1_usb_router_link_intf_clk is really disp_cc_mdss_dptx0_link_div_clk_src
I checked on the SM8650 side, and disp_cc_mdss_dptx1_link_div_clk_src is the parent of disp_cc_mdss_dptx1_usb_router_link_intf_clk,
so it's different on both platforms.
Neil
next prev parent reply other threads:[~2024-07-17 8:08 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-07-16 21:13 [PATCH 0/7] clk: qcom: merge SM8550 and SM8650 display clock controller drivers Dmitry Baryshkov
2024-07-16 21:13 ` [PATCH 1/7] clk: qcom: dispcc-sm8550: fix several supposed typos Dmitry Baryshkov
2024-07-17 8:08 ` Neil Armstrong [this message]
2024-07-17 9:49 ` Dmitry Baryshkov
2024-07-16 21:13 ` [PATCH 2/7] clk: qcom: dispcc-sm8550: use rcg2_ops for mdss_dptx1_aux_clk_src Dmitry Baryshkov
2024-07-17 8:09 ` Neil Armstrong
2024-07-17 10:05 ` Dmitry Baryshkov
2024-07-16 21:13 ` [PATCH 3/7] clk: qcom: dispcc-sm8550: make struct clk_init_data const Dmitry Baryshkov
2024-07-17 8:09 ` Neil Armstrong
2024-07-16 21:13 ` [PATCH 4/7] clk: qcom: dispcc-sm8650: Update the GDSC flags Dmitry Baryshkov
2024-07-17 8:10 ` Neil Armstrong
2024-07-16 21:13 ` [PATCH 5/7] clk: qcom: dispcc-sm8550: use rcg2_shared_ops for ESC RCGs Dmitry Baryshkov
2024-07-17 8:09 ` Neil Armstrong
2024-07-16 21:13 ` [PATCH 6/7] clk: qcom: fold dispcc-sm8650 info dispcc-sm8550 Dmitry Baryshkov
2024-07-16 21:13 ` [PATCH 7/7] dt-bindings: clock: qcom,sm8650-dispcc: replace with symlink Dmitry Baryshkov
2024-07-16 21:24 ` Dmitry Baryshkov
2024-07-17 6:57 ` Krzysztof Kozlowski
2024-07-17 9:53 ` 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=d60cd97b-a1da-4dbd-910d-92cd62762afd@linaro.org \
--to=neil.armstrong@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@linaro.org \
--cc=konrad.dybcio@linaro.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=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;
as well as URLs for NNTP newsgroup(s).