From: Stephen Boyd <swboyd@chromium.org>
To: Konrad Dybcio <konrad.dybcio@linaro.org>,
Bjorn Andersson <andersson@kernel.org>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-arm-msm@vger.kernel.org,
patches@lists.linux.dev, linux-clk@vger.kernel.org,
Amit Pundir <amit.pundir@linaro.org>,
Taniya Das <quic_tdas@quicinc.com>
Subject: [PATCH 0/2] clk: qcom: gcc-sm8550: Fix shared clk parking breakage
Date: Mon, 19 Aug 2024 16:36:25 -0700 [thread overview]
Message-ID: <20240819233628.2074654-1-swboyd@chromium.org> (raw)
Amit Pundir reported[1] that a recent commit 01a0a6cc8cfd ("clk: qcom:
Park shared RCGs upon registration") broke USB and audio on sm8550-hdk.
These two patches fix the issue by skipping the parking bit of the
shared RCGs for devices that can't run so slow.
[1] https://lore.kernel.org/CAMi1Hd1KQBE4kKUdAn8E5FV+BiKzuv+8FoyWQrrTHPDoYTuhgA@mail.gmail.com/
Stephen Boyd (2):
clk: qcom: gcc-sm8550: Don't use parking clk_ops for QUPs
clk: qcom: gcc-sm8550: Don't park the USB RCG at registration time
drivers/clk/qcom/clk-rcg.h | 1 +
drivers/clk/qcom/clk-rcg2.c | 30 +++++++++++++++++++
drivers/clk/qcom/gcc-sm8550.c | 54 +++++++++++++++++------------------
3 files changed, 58 insertions(+), 27 deletions(-)
base-commit: 8400291e289ee6b2bf9779ff1c83a291501f017b
--
https://chromeos.dev
next reply other threads:[~2024-08-19 23:36 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-19 23:36 Stephen Boyd [this message]
2024-08-19 23:36 ` [PATCH 1/2] clk: qcom: gcc-sm8550: Don't use parking clk_ops for QUPs Stephen Boyd
2024-08-27 18:04 ` Stephen Boyd
2024-08-19 23:36 ` [PATCH 2/2] clk: qcom: gcc-sm8550: Don't park the USB RCG at registration time Stephen Boyd
2024-08-27 18:04 ` Stephen Boyd
2024-08-27 18:12 ` Stephen Boyd
2024-08-30 12:24 ` Konrad Dybcio
2024-08-30 17:59 ` Stephen Boyd
2025-01-03 13:17 ` Konrad Dybcio
2024-08-21 15:34 ` [PATCH 0/2] clk: qcom: gcc-sm8550: Fix shared clk parking breakage Amit Pundir
2024-08-21 15:44 ` neil.armstrong
2024-08-23 20:33 ` Stephen Boyd
2024-08-26 9:55 ` neil.armstrong
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=20240819233628.2074654-1-swboyd@chromium.org \
--to=swboyd@chromium.org \
--cc=amit.pundir@linaro.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=patches@lists.linux.dev \
--cc=quic_tdas@quicinc.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