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-0b1b44215...@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
