[<prev] [next>] [<thread-prev] [day] [month] [year] [list]
Message-ID: <x6p3me4zf26y23loq7mvveuoqp6xbqj4nea2wbveghxd7yrh6d@6nkjp56o5z4a>
Date: Sun, 16 Nov 2025 13:39:08 +0200
From: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
To: Alexey Minnekhanov <alexeymin@...tmarketos.org>
Cc: Bjorn Andersson <andersson@...nel.org>, Stephen Boyd <sboyd@...nel.org>,
Rob Herring <robh@...nel.org>,
Krzysztof Kozlowski <krzk+dt@...nel.org>,
Conor Dooley <conor+dt@...nel.org>,
Konrad Dybcio <konradybcio@...nel.org>, linux-arm-msm@...r.kernel.org,
linux-clk@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org, stable@...r.kernel.org,
~postmarketos/upstreaming@...ts.sr.ht
Subject: Re: [PATCH v2 3/3] arm64: dts: qcom: sdm630: Add missing MDSS reset
On Sun, Nov 16, 2025 at 04:12:35AM +0300, Alexey Minnekhanov wrote:
> 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.
>
> It fixes display init issue appeared in Linux v6.17: without reset
> device boots into black screen and you need to turn display off/on
> to "fix" it. Also sometimes it can boot into solid blue color
> with these messages in kernel log:
>
> hw recovery is not complete for ctl:2
> [drm:dpu_encoder_phys_vid_prepare_for_kickoff:569] [dpu error]enc33
> intf1 ctl 2 reset failure: -22
> [drm:dpu_encoder_frame_done_timeout:2727] [dpu error]enc33 frame
> done timeout
>
> Fixes: 0e789b491ba0 ("pmdomain: core: Leave powered-on genpds on until sync_state")
> Cc: <stable@...r.kernel.org> # 6.17
> Signed-off-by: Alexey Minnekhanov <alexeymin@...tmarketos.org>
> ---
> arch/arm64/boot/dts/qcom/sdm630.dtsi | 1 +
> 1 file changed, 1 insertion(+)
>
Reviewed-by: Dmitry Baryshkov <dmitry.baryshkov@....qualcomm.com>
--
With best wishes
Dmitry
Powered by blists - more mailing lists