From: Val Packett <val@packett.cool>
Cc: linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org,
~postmarketos/upstreaming@lists.sr.ht,
Val Packett <val@packett.cool>,
linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH 0/6] SM6115/SM6125 MDSS core reset
Date: Mon, 16 Feb 2026 20:25:18 -0300 [thread overview]
Message-ID: <20260216233600.13098-2-val@packett.cool> (raw)
Hi,
this series is like [1] but for these two SoCs.
Yeah: same person, different SoCs, same cause, different symptoms :)
On the SC7180 WoA device with DP out, it was causing faults+artifacts
due to EFI framebuffer scanout not stopping when Linux takes over.
This time, the reset was necessary for MIPI DSI display to work *at all*
on the sm6115-motorola-guamp (Moto G9 Play) phone (DTS coming very soon!)
With the state left by the bootloader, the display would stay gray. DCS
setup commands would go through fine, some `dsi_err_worker: status=4`
errors would be logged after setup a few times (not continuously) but
the display would not start working. With the reset, it works fine!
Since the SM6125 is closely related, I've done the same for it as well.
The QCM2290 already does have the reset.
[1]: https://lore.kernel.org/all/20260120-topic-7180_dispcc_bcr-v1-0-0b1b442156c3@oss.qualcomm.com/
Thanks,
~val
Val Packett (6):
dt-bindings: clock: qcom,sm6115-dispcc: Define MDSS resets
dt-bindings: clock: qcom,dispcc-sm6125: Define MDSS resets
clk: qcom: dispcc-sm6115: Add missing MDSS resets
clk: qcom: dispcc-sm6125: Add missing MDSS resets
arm64: dts: qcom: sm6115: Add missing MDSS core reset
arm64: dts: qcom: sm6125: Add missing MDSS core reset
arch/arm64/boot/dts/qcom/sm6115.dtsi | 2 ++
arch/arm64/boot/dts/qcom/sm6125.dtsi | 3 +++
drivers/clk/qcom/dispcc-sm6115.c | 7 +++++++
drivers/clk/qcom/dispcc-sm6125.c | 7 +++++++
include/dt-bindings/clock/qcom,dispcc-sm6125.h | 6 +++++-
include/dt-bindings/clock/qcom,sm6115-dispcc.h | 7 +++++--
6 files changed, 29 insertions(+), 3 deletions(-)
--
2.52.0
next reply other threads:[~2026-02-16 23:38 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-16 23:25 Val Packett [this message]
2026-02-16 23:25 ` [PATCH 1/6] dt-bindings: clock: qcom,sm6115-dispcc: Define MDSS resets Val Packett
2026-02-17 8:11 ` Krzysztof Kozlowski
2026-02-16 23:25 ` [PATCH 2/6] dt-bindings: clock: qcom,dispcc-sm6125: " Val Packett
2026-02-16 23:25 ` [PATCH 3/6] clk: qcom: dispcc-sm6115: Add missing " Val Packett
2026-02-17 7:36 ` Dmitry Baryshkov
2026-02-17 9:22 ` Konrad Dybcio
2026-02-16 23:25 ` [PATCH 4/6] clk: qcom: dispcc-sm6125: " Val Packett
2026-02-17 7:37 ` Dmitry Baryshkov
2026-02-17 8:12 ` Krzysztof Kozlowski
2026-02-17 9:22 ` Konrad Dybcio
2026-02-16 23:25 ` [PATCH 5/6] arm64: dts: qcom: sm6115: Add missing MDSS core reset Val Packett
2026-02-17 7:37 ` Dmitry Baryshkov
2026-02-17 9:22 ` Konrad Dybcio
2026-02-16 23:25 ` [PATCH 6/6] arm64: dts: qcom: sm6125: " Val Packett
2026-02-17 7:37 ` Dmitry Baryshkov
2026-02-17 9:23 ` Konrad Dybcio
2026-02-18 13:31 ` Yedaya Katsman
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=20260216233600.13098-2-val@packett.cool \
--to=val@packett.cool \
--cc=devicetree@vger.kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=phone-devel@vger.kernel.org \
--cc=~postmarketos/upstreaming@lists.sr.ht \
/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