From: "Barnabás Czémán" <trabarni@gmail.com>
To: Bjorn Andersson <andersson@kernel.org>,
Andy Gross <agross@kernel.org>,
Konrad Dybcio <konrad.dybcio@linaro.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: "Barnabás Czémán" <trabarni@gmail.com>
Subject: [PATCH] clk: qcom: gcc-msm8953: fix stuck gcc_usb30_master_clk
Date: Mon, 2 Oct 2023 19:00:21 +0200 [thread overview]
Message-ID: <20231002170021.192740-1-trabarni@gmail.com> (raw)
According to downstream dwc3-msm source this clock has FSM dependency on
gcc_pcnoc_usb30_clk so enabling it would fail if latter isn't enabled.
This patch add works around this issue by changing parent of
gcc_usb30_master_clk to gcc_pcnoc_usb30_clk. This is acceptable because
both clocks have same parent and are branches/gates.
Signed-off-by: Barnabás Czémán <trabarni@gmail.com>
---
drivers/clk/qcom/gcc-msm8953.c | 2 +-
1 file changed, 1 insertion(+), 1 deletion(-)
diff --git a/drivers/clk/qcom/gcc-msm8953.c b/drivers/clk/qcom/gcc-msm8953.c
index 3e5a8cb14d4d..20639340e8a6 100644
--- a/drivers/clk/qcom/gcc-msm8953.c
+++ b/drivers/clk/qcom/gcc-msm8953.c
@@ -3645,7 +3645,7 @@ static struct clk_branch gcc_usb30_master_clk = {
.hw.init = &(struct clk_init_data) {
.name = "gcc_usb30_master_clk",
.parent_hws = (const struct clk_hw*[]){
- &usb30_master_clk_src.clkr.hw,
+ &gcc_pcnoc_usb3_axi_clk.clkr.hw,
},
.num_parents = 1,
.ops = &clk_branch2_ops,
--
2.42.0
next reply other threads:[~2023-10-02 17:00 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-10-02 17:00 Barnabás Czémán [this message]
2023-10-06 23:50 ` [PATCH] clk: qcom: gcc-msm8953: fix stuck gcc_usb30_master_clk Konrad Dybcio
2023-10-24 2:59 ` Stephen Boyd
2023-11-18 0:48 ` Konrad Dybcio
2023-11-22 6:09 ` Krishna Kurapati PSSNV
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=20231002170021.192740-1-trabarni@gmail.com \
--to=trabarni@gmail.com \
--cc=agross@kernel.org \
--cc=andersson@kernel.org \
--cc=konrad.dybcio@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=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