From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Bjorn Andersson <andersson@kernel.org>,
Mahadevan P <mahadevan.p@oss.qualcomm.com>,
Douglas Anderson <dianders@chromium.org>
Cc: Konrad Dybcio <konradybcio@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
cros-qcom-dts-watchers@chromium.org,
linux-arm-msm@vger.kernel.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org,
Mahadevan P <mahap@qti.qualcomm.com>
Subject: Re: [PATCH v2 0/3] arm64: dts: qcom: kodiak: Enable 4-lane DP via QMP Combo PHY
Date: Fri, 19 Jun 2026 17:34:05 +0200 [thread overview]
Message-ID: <84ed2c32-16d0-4c29-a06a-9242eeb8e86e@oss.qualcomm.com> (raw)
In-Reply-To: <ag_QL5DIo7MxsdYU@baldur>
On 5/22/26 5:41 AM, Bjorn Andersson wrote:
> On Wed, Apr 29, 2026 at 12:10:39PM +0530, Mahadevan P wrote:
>> This series enables full 4-lane DisplayPort operation on SC7280/kodiak
>> platforms by wiring up the QMP Combo PHY correctly and consolidating
>> the DP endpoint configuration in the SoC dtsi.
>>
>> Patch 1 adds mode-switch to the QMP Combo PHY node in kodiak.dtsi,
>> which is required for the PHY to respond to USB-C Alternate Mode
>> negotiation and switch into 4-lane DP configuration.
>>
>> Patch 2 moves the data-lanes property from individual board files into
>> kodiak.dtsi since the PHY-to-controller wiring is fixed in silicon.
>> It also removes redundant remote-endpoint and orientation-switch
>> overrides from qcs6490-rb3gen2 and qcs6490-thundercomm-rubikpi3 that
>> are already covered by the SoC dtsi.
>>
>> Patch 3 updates data-lanes from <0 1> to <0 1 2 3> in kodiak.dtsi now
>> that mode-switch is in place, enabling the full 4-lane DP link.
>
> Are you sure that herobrine has 4 lanes routed on the PCB?
+Doug any chance you still have schematics for that old boy?
Bjorn, perhaps we could switch to a model where we define the max
capabilities (i.e. 4-lane 8.1 GHz link) in the SoC DTs and only limit
them as necessary? Not meeting these is borderline a board defect anyway
Konrad
next prev parent reply other threads:[~2026-06-19 15:34 UTC|newest]
Thread overview: 18+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-04-29 6:40 Mahadevan P
2026-04-29 6:40 ` [PATCH v2 1/3] arm64: dts: qcom: kodiak: allow mode-switch events to reach the " Mahadevan P
2026-05-15 10:57 ` Konrad Dybcio
2026-04-29 6:40 ` [PATCH v2 2/3] arm64: dts: qcom: kodiak: move dp data-lanes to SoC dtsi Mahadevan P
2026-06-26 20:50 ` Dmitry Baryshkov
2026-06-28 2:26 ` Bjorn Andersson
2026-06-28 11:17 ` Dmitry Baryshkov
2026-07-15 19:57 ` Bjorn Andersson
2026-04-29 6:40 ` [PATCH v2 3/3] arm64: dts: qcom: kodiak: Set up 4-lane DP Mahadevan P
2026-06-26 20:51 ` Dmitry Baryshkov
2026-06-28 2:28 ` Bjorn Andersson
2026-06-28 12:21 ` Dmitry Baryshkov
2026-06-29 6:53 ` Mahadevan P
2026-05-22 3:41 ` [PATCH v2 0/3] arm64: dts: qcom: kodiak: Enable 4-lane DP via QMP Combo PHY Bjorn Andersson
2026-06-19 15:34 ` Konrad Dybcio [this message]
2026-06-21 22:11 ` Doug Anderson
2026-06-26 16:02 ` Konrad Dybcio
2026-06-26 20:49 ` 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=84ed2c32-16d0-4c29-a06a-9242eeb8e86e@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=cros-qcom-dts-watchers@chromium.org \
--cc=devicetree@vger.kernel.org \
--cc=dianders@chromium.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mahadevan.p@oss.qualcomm.com \
--cc=mahap@qti.qualcomm.com \
--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