public inbox for devicetree@vger.kernel.org
 help / color / mirror / Atom feed
From: Krzysztof Kozlowski <krzk@kernel.org>
To: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Krzysztof Kozlowski <krzysztof.kozlowski@oss.qualcomm.com>,
	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: linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
	linux-kernel@vger.kernel.org,
	Abel Vesa <abel.vesa@oss.qualcomm.com>
Subject: Re: [PATCH RFC 0/2] arm64: dts: qcom: eliza: Add display
Date: Tue, 31 Mar 2026 17:01:11 +0200	[thread overview]
Message-ID: <b3b96c87-83dd-422b-a67c-cfe41ae94a35@kernel.org> (raw)
In-Reply-To: <e4cad76c-09ad-45e9-8725-ec156c121bb8@oss.qualcomm.com>

On 31/03/2026 16:49, Konrad Dybcio wrote:
> On 3/31/26 4:02 PM, Krzysztof Kozlowski wrote:
>> Dependency
>> ==========
>> Depends on USB patches, which are being reviewed, therefore marking it
>> as RFC as it cannot be applied.
>> https://lore.kernel.org/all/20260331-eliza-adsp-usb-v1-0-d8a251be20c3@oss.qualcomm.com/
>>
>> Unmerged bindings used here
>> ===========================
>> dispcc: https://lore.kernel.org/all/20260319-clk-qcom-dispcc-eliza-v3-0-d1f2b19a6e6b@oss.qualcomm.com/
>> (DRM MDSS bindings were applied)
>>
>> Description
>> ===========
>> I did not enable DisplayPort because it does not work on my board and I
>> don't know why. I double checked QMP combo phy and other bits, and
>> everything is looking fine, but still no USB display, so maybe I miss
>> some other dependencies as this is early upstream.
> 
> What was the furthest that you got? We can certainly try to help..
> 
> Got USB Type-C mode mux events?
> PHY initialized and configured to 2/4-lane DP mode?
> Are the AUX transfers failling?

[   43.975329] msm_dpu ae01000.display-controller: [drm:drm_dp_dpcd_access] dpu_dp_aux: Too many retries, giving up. First error: -110
[   43.975410] msm_dpu ae01000.display-controller: [drm:drm_dp_dpcd_probe] dpu_dp_aux: 0x00102 AUX -> (ret=-110)
[   45.780383] msm_dpu ae01000.display-controller: [drm:drm_dp_dpcd_access] dpu_dp_aux: Too many retries, giving up. First error: -110
[   45.780463] msm_dpu ae01000.display-controller: [drm:drm_dp_dpcd_probe] dpu_dp_aux: 0x00102 AUX -> (ret=-110)
[   45.780521] msm_dpu ae01000.display-controller: [drm:msm_dp_pm_runtime_suspend] type=10 core_init=1 phy_init=1

pastebin: https://pastebin.com/BVXy3Qeq

Abel pointed me to the phy problems, so I focused on that.
HSR says it is exactly same programming sequence as SM8650
and such was used.

Just note, that we have ADSP remoteproc up, but no audio including USB mux,
although that should not affect this, AFAIU.

Best regards,
Krzysztof

  reply	other threads:[~2026-03-31 15:01 UTC|newest]

Thread overview: 14+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-31 14:02 [PATCH RFC 0/2] arm64: dts: qcom: eliza: Add display Krzysztof Kozlowski
2026-03-31 14:02 ` [PATCH RFC 1/2] arm64: dts: qcom: eliza: Add display (MDSS) with Display CC Krzysztof Kozlowski
2026-03-31 18:01   ` Dmitry Baryshkov
2026-04-02  9:42   ` Konrad Dybcio
2026-04-02  9:49     ` Krzysztof Kozlowski
2026-03-31 14:02 ` [PATCH RFC 2/2] arm64: dts: qcom: eliza-mtp: Enable DSI display panel Krzysztof Kozlowski
2026-03-31 18:01   ` Dmitry Baryshkov
2026-03-31 14:05 ` [PATCH RFC 0/2] arm64: dts: qcom: eliza: Add display Krzysztof Kozlowski
2026-03-31 14:49 ` Konrad Dybcio
2026-03-31 15:01   ` Krzysztof Kozlowski [this message]
2026-03-31 15:03     ` Konrad Dybcio
2026-03-31 15:06       ` Krzysztof Kozlowski
2026-03-31 15:23         ` Konrad Dybcio
2026-03-31 15:27           ` Krzysztof Kozlowski

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=b3b96c87-83dd-422b-a67c-cfe41ae94a35@kernel.org \
    --to=krzk@kernel.org \
    --cc=abel.vesa@oss.qualcomm.com \
    --cc=andersson@kernel.org \
    --cc=conor+dt@kernel.org \
    --cc=devicetree@vger.kernel.org \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=konradybcio@kernel.org \
    --cc=krzk+dt@kernel.org \
    --cc=krzysztof.kozlowski@oss.qualcomm.com \
    --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