Linux ARM-MSM sub-architecture
 help / color / mirror / Atom feed
From: Val Packett <val@packett.cool>
To: Bjorn Andersson <andersson@kernel.org>,
	Konrad Dybcio <konradybcio@kernel.org>,
	Rob Herring <robh@kernel.org>,
	Krzysztof Kozlowski <krzk+dt@kernel.org>,
	Conor Dooley <conor+dt@kernel.org>,
	Adam Skladowski <a39.skl@gmail.com>
Cc: linux-arm-msm@vger.kernel.org, phone-devel@vger.kernel.org,
	~postmarketos/upstreaming@lists.sr.ht,
	Val Packett <val@packett.cool>,
	devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 5/6] arm64: dts: qcom: sm6115: Add missing MDSS core reset
Date: Mon, 16 Feb 2026 20:25:23 -0300	[thread overview]
Message-ID: <20260216233600.13098-7-val@packett.cool> (raw)
In-Reply-To: <20260216233600.13098-2-val@packett.cool>

To make sure the display subsystem starts in a predictable state, we
need to reset it. Otherwise, unpredictable issues can happen, e.g.
on the motorola-guamp smartphone DSI would not transmit anything.

Wire up the reset to fix.

Fixes: 705e50427d81 ("arm64: dts: qcom: sm6115: Add mdss/dpu node")
Signed-off-by: Val Packett <val@packett.cool>
---
 arch/arm64/boot/dts/qcom/sm6115.dtsi | 2 ++
 1 file changed, 2 insertions(+)

diff --git a/arch/arm64/boot/dts/qcom/sm6115.dtsi b/arch/arm64/boot/dts/qcom/sm6115.dtsi
index e9336adbc391..3a9a1ad8d581 100644
--- a/arch/arm64/boot/dts/qcom/sm6115.dtsi
+++ b/arch/arm64/boot/dts/qcom/sm6115.dtsi
@@ -1864,6 +1864,8 @@ mdss: display-subsystem@5e00000 {
 				 <&gcc GCC_DISP_HF_AXI_CLK>,
 				 <&dispcc DISP_CC_MDSS_MDP_CLK>;
 
+			resets = <&dispcc DISP_CC_MDSS_CORE_BCR>;
+
 			interrupts = <GIC_SPI 186 IRQ_TYPE_LEVEL_HIGH>;
 			interrupt-controller;
 			#interrupt-cells = <1>;
-- 
2.52.0


  parent reply	other threads:[~2026-02-16 23:39 UTC|newest]

Thread overview: 18+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-16 23:25 [PATCH 0/6] SM6115/SM6125 MDSS core reset Val Packett
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 ` Val Packett [this message]
2026-02-17  7:37   ` [PATCH 5/6] arm64: dts: qcom: sm6115: Add missing MDSS core reset 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-7-val@packett.cool \
    --to=val@packett.cool \
    --cc=a39.skl@gmail.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=phone-devel@vger.kernel.org \
    --cc=robh@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