[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <f790b655-4192-bcad-07af-814a359a351a@linaro.org>
Date: Tue, 16 May 2023 17:35:24 +0200
From: Krzysztof Kozlowski <krzysztof.kozlowski@...aro.org>
To: Konrad Dybcio <konrad.dybcio@...aro.org>,
Andy Gross <agross@...nel.org>,
Bjorn Andersson <andersson@...nel.org>,
Rob Herring <robh+dt@...nel.org>,
Krzysztof Kozlowski <krzysztof.kozlowski+dt@...aro.org>,
Conor Dooley <conor+dt@...nel.org>,
linux-arm-msm@...r.kernel.org, devicetree@...r.kernel.org,
linux-kernel@...r.kernel.org
Cc: Neil Armstrong <neil.armstrong@...aro.org>,
"Signed-off-by : Abel Vesa" <abel.vesa@...aro.org>
Subject: Re: [PATCH] arm64: dts: qcom: sm8550-qrd: add display and panel
On 16/05/2023 17:26, Konrad Dybcio wrote:
>>>> +&mdss_mdp {
>>>> + status = "okay";
>>>> +};
>>> This should also be enabled by default, MDSS is useless when MDP is
>>> disabled.
>>
>> But don't we want to disable both when display is not used (not connected)?
> The MDSS bus device only has a 0x1000 slice of the 0x90000-long "full MDSS",
> the rest is probed with MDP/DPU. It also calls of_something_populate that
> make DSI, DSIPHY and DP/HDMI probe. But all of them ultimately need a graph
> handle to MDP.
>
> If we have a display (of any kind), MDP has to be enabled (or the display
> engine will not have a way to be programmed).
>
> If we don't, enabling MDSS makes no sense as all of the hardware will be
> shut down right after probing.
>
> So I'd say either both or none.
Yes, so the current state - both disabled - is matching it.
Best regards,
Krzysztof
Powered by blists - more mailing lists