From: "Barnabás Czémán" <barnabas.czeman@mainlining.org>
To: Bjorn Andersson <andersson@kernel.org>,
Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
Martin Botka <martin.botka@somainline.org>,
Konrad Dybcio <konradybcio@kernel.org>,
AngeloGioacchino Del Regno
<angelogioacchino.delregno@somainline.org>,
Adam Skladowski <a_skl39@protonmail.com>,
Sireesh Kodali <sireeshkodali@protonmail.com>,
Vladimir Lypak <junak.pub@gmail.com>
Cc: linux-arm-msm@vger.kernel.org, linux-clk@vger.kernel.org,
linux-kernel@vger.kernel.org,
"Barnabás Czémán" <barnabas.czeman@mainlining.org>,
"Vladimir Lypak" <vladimir.lypak@gmail.com>
Subject: [PATCH 0/2] SDM660/MSM8953 Fix video core clock status stuck
Date: Sat, 15 Mar 2025 16:26:16 +0100 [thread overview]
Message-ID: <20250315-clock-fix-v1-0-2efdc4920dda@mainlining.org> (raw)
On SDM660 and MSM8953 video_subcore0 and venus0_core0 clocks are stuck
at off. This patch series fixes them.
Signed-off-by: Barnabás Czémán <barnabas.czeman@mainlining.org>
---
Barnabás Czémán (1):
clk: qcom: mmcc-sdm660: fix stuck video_subcore0 clock
Vladimir Lypak (1):
clk: qcom: gcc-msm8953: fix stuck venus0_core0 clock
drivers/clk/qcom/gcc-msm8953.c | 2 +-
drivers/clk/qcom/mmcc-sdm660.c | 2 +-
2 files changed, 2 insertions(+), 2 deletions(-)
---
base-commit: da920b7df701770e006928053672147075587fb2
change-id: 20250315-clock-fix-a5f72db5a416
Best regards,
--
Barnabás Czémán <barnabas.czeman@mainlining.org>
next reply other threads:[~2025-03-15 15:26 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-03-15 15:26 Barnabás Czémán [this message]
2025-03-15 15:26 ` [PATCH 1/2] clk: qcom: mmcc-sdm660: fix stuck video_subcore0 clock Barnabás Czémán
2025-03-15 15:26 ` [PATCH 2/2] clk: qcom: gcc-msm8953: fix stuck venus0_core0 clock Barnabás Czémán
2025-03-17 2:55 ` [PATCH 0/2] SDM660/MSM8953 Fix video core clock status stuck Bjorn Andersson
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=20250315-clock-fix-v1-0-2efdc4920dda@mainlining.org \
--to=barnabas.czeman@mainlining.org \
--cc=a_skl39@protonmail.com \
--cc=andersson@kernel.org \
--cc=angelogioacchino.delregno@somainline.org \
--cc=junak.pub@gmail.com \
--cc=konradybcio@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=martin.botka@somainline.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@kernel.org \
--cc=sireeshkodali@protonmail.com \
--cc=vladimir.lypak@gmail.com \
/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