mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Abhinav Kumar <quic_abhinavk@quicinc.com>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>,
	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>
Cc: Jessica Zhang <jesszhan@quicinc.com>,
	Abhinav Kumar <abhinavk@quicinc.com>,
	Abel Vesa <abel.vesa@linaro.org>, <linux-arm-msm@vger.kernel.org>,
	<devicetree@vger.kernel.org>, <linux-kernel@vger.kernel.org>
Subject: Re: [PATCH RFC/WIP 1/4] arm64: dts: qcom: sm8750: Add display (MDSS) with Display CC
Date: Tue, 29 Apr 2025 16:07:24 -0700	[thread overview]
Message-ID: <97ae84c6-0807-4b19-a474-ba76cc049da9@quicinc.com> (raw)
In-Reply-To: <81205948-ae43-44ee-aa07-e490ea3bba23@oss.qualcomm.com>



On 4/28/2025 2:31 PM, Konrad Dybcio wrote:
> On 4/24/25 3:04 PM, Krzysztof Kozlowski wrote:
>> Add device nodes for entire display: MDSS, DPU, DSI, DSI PHYs,
>> DisplayPort and Display Clock Controller.
>>
>> Signed-off-by: Krzysztof Kozlowski <krzysztof.kozlowski@linaro.org>
>>
>> ---
> 
> [...]
> 
>> +				mdp_opp_table: opp-table {
>> +					compatible = "operating-points-v2";
>> +
> 
> The computer tells me there's also a 156 MHz rate @ SVS_D1
> 
> Maybe Abhinav could chime in whether we should add it or not
> 

Yes I also see a 156Mhz for LOW_SVS_D1 but we had a similar entry even 
for sm8650 and did not publish it in the dt.

It was present till sm8450.dtsi but dropped in sm8550/sm8650 even though 
LOW_SVS_D1 is present even on those.

I think the reason could be that the displays being used on the 
reference boards will need a pixel clock of atleast >= low_svs and the 
MDP clock usually depends on the value of the DSI pixel clock (which has 
a fixed relationship to the byte clock) to maintain the data rate. So as 
a result perhaps even if we add it, for most displays this level will be 
unused.

If we end up using displays which are so small that the pixel clock 
requirement will be even lower than low_svs, we can add those.

OR as an alternative, we can leave this patch as it is and add the 
low_svs_d1 for all chipsets which support it together in another series 
that way it will have the full context of why we are adding it otherwise 
it will look odd again of why sm8550/sm8650 was left out but added in 
sm8750.

> [...]
> 
>> +				mdss_dsi_opp_table: opp-table {
>> +					compatible = "operating-points-v2";
>> +
> 
> Similarly there's a 140.63 MHz rate at SVS_D1, but it seems odd
> with the decimals

For this one, yes its true that LOW_SVS_D1 is 140.63Mhz for sm8750 but 
this voltage corner was somehow never used for DSI byte clock again I am 
thinking this is because for the display resolutions we use, we will 
always be >= low_svs so the low_svs_d1 will never hit even if we add it.


> 
> Konrad
> 


  reply	other threads:[~2025-04-29 23:07 UTC|newest]

Thread overview: 31+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-04-24 13:04 [PATCH RFC/WIP 0/4] arm64: dts: qcom: sm8750: Enable display Krzysztof Kozlowski
2025-04-24 13:04 ` [PATCH RFC/WIP 1/4] arm64: dts: qcom: sm8750: Add display (MDSS) with Display CC Krzysztof Kozlowski
2025-04-24 13:14   ` Krzysztof Kozlowski
2025-04-28 21:31   ` Konrad Dybcio
2025-04-29 23:07     ` Abhinav Kumar [this message]
2025-04-30  7:46       ` Konrad Dybcio
2025-05-05  6:49         ` Krzysztof Kozlowski
2025-05-05  7:25           ` Krzysztof Kozlowski
2025-05-03  5:51       ` Dmitry Baryshkov
2025-05-03 19:59         ` Abhinav Kumar
2025-05-03 21:01           ` Dmitry Baryshkov
2025-05-04  0:37             ` Abhinav Kumar
2025-10-29  7:40   ` Abel Vesa
2025-10-29  7:45     ` Krzysztof Kozlowski
2025-10-29  7:58       ` Abel Vesa
2025-04-24 13:04 ` [PATCH RFC/WIP 2/4] arm64: dts: qcom: sm8750-mtp: Enable display Krzysztof Kozlowski
2025-04-24 13:04 ` [PATCH RFC/WIP 3/4] arm64: dts: qcom: sm8750-mtp: Enable USB headset and Type-C altmode Krzysztof Kozlowski
2025-04-24 13:51   ` neil.armstrong
2025-04-24 14:39   ` Krzysztof Kozlowski
2025-04-24 13:04 ` [PATCH RFC/WIP 4/4] arm64: dts: qcom: sm8750-mtp: Enable DisplayPort over USB Krzysztof Kozlowski
2025-04-24 13:52   ` neil.armstrong
2025-04-25 19:34 ` [PATCH RFC/WIP 0/4] arm64: dts: qcom: sm8750: Enable display Dmitry Baryshkov
2025-04-25 19:54   ` Abhinav Kumar
2025-04-25 19:54   ` Krzysztof Kozlowski
2025-04-25 22:07     ` Dmitry Baryshkov
     [not found]     ` <32eb3b4f-b2c4-4895-8b48-ade319fd83de@oss.qualcomm.com>
2025-10-29  6:27       ` Krzysztof Kozlowski
2025-10-30  6:59         ` Jessica Zhang
2025-10-30 11:16       ` Dmitry Baryshkov
2025-10-30 12:21         ` Mahadevan P
2025-10-30 16:30           ` Krzysztof Kozlowski
2025-10-30 17:56           ` Dmitry Baryshkov

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=97ae84c6-0807-4b19-a474-ba76cc049da9@quicinc.com \
    --to=quic_abhinavk@quicinc.com \
    --cc=abel.vesa@linaro.org \
    --cc=abhinavk@quicinc.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=jesszhan@quicinc.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@linaro.org \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=robh@kernel.org \
    /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

all inboxes | Powered by JetHome®