Seeing the $subj, I asking myself why do I use `b4 --reflect`...
Anyway, if the patch will be good enough, feel free to strip
`needsreview!`, or I'll sent v2 ;-)
David
On 12/01/2026 13:33, David Heidelberg via B4 Relay wrote:
From: David Heidelberg <[email protected]>
If the OS does not support recovering the state left by the
bootloader it needs a way to reset display hardware, so that it can
start from a clean state. Add a reference to the relevant reset.
Signed-off-by: David Heidelberg <[email protected]>
---
It efficiently fixes nothing for us (at least what we're aware), so I
assume the state left by bootloader is good enough
I sending this as a something "which seems right" and works for us in
sdm845-next tree.
David
---
arch/arm64/boot/dts/qcom/sdm845.dtsi | 1 +
1 file changed, 1 insertion(+)
diff --git a/arch/arm64/boot/dts/qcom/sdm845.dtsi
b/arch/arm64/boot/dts/qcom/sdm845.dtsi
index bf2f9c04adba7..75c192eddc57c 100644
--- a/arch/arm64/boot/dts/qcom/sdm845.dtsi
+++ b/arch/arm64/boot/dts/qcom/sdm845.dtsi
@@ -4550,6 +4550,7 @@ mdss: display-subsystem@ae00000 {
reg-names = "mdss";
power-domains = <&dispcc MDSS_GDSC>;
+ resets = <&dispcc DISP_CC_MDSS_RSCC_BCR>;
clocks = <&dispcc DISP_CC_MDSS_AHB_CLK>,
<&dispcc DISP_CC_MDSS_MDP_CLK>;
---
base-commit: f417b7ffcbef7d76b0d8860518f50dae0e7e5eda
change-id: 20260112-mdss-reset-06988f05af96
Best regards,
--
David Heidelberg
