From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Jesse Casco <jesse.casco@gmail.com>, Abel Vesa <abel.vesa@linaro.org>
Cc: Abel Vesa <abel.vesa@oss.qualcomm.com>,
Yongxing Mou <yongxing.mou@oss.qualcomm.com>,
Dmitry Baryshkov <lumag@kernel.org>,
Vinod Koul <vkoul@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Rob Clark <robin.clark@oss.qualcomm.com>,
Abhinav Kumar <abhinav.kumar@linux.dev>,
linux-phy@lists.infradead.org, linux-arm-msm@vger.kernel.org,
dri-devel@lists.freedesktop.org, linux-kernel@vger.kernel.org
Subject: Re: glymur eDP PHY (v8): link trains only at HBR3, all lower rates fail
Date: Tue, 18 Aug 2026 12:39:00 +0200 [thread overview]
Message-ID: <9fab8686-d0fa-40df-a6d0-75349861d78a@oss.qualcomm.com> (raw)
In-Reply-To: <20260808171321.133028-1-jesse.casco@gmail.com>
On 8/8/26 7:13 PM, Jesse Casco wrote:
> Hi Abel,
>
> On an ASUS Zenbook A16 (UX3607OA, Snapdragon X2 Elite Extreme) the internal
> eDP panel never comes up on mainline. It is the link rate: the v8 eDP PHY
> appears to bring up a usable link only at HBR3.
>
> Tested on linux-next next-20260713, next-20260803 and next-20260807, where
> phy-qcom-edp.c is byte-identical -- so not a recent regression, and the May
> 2026 series (eDP low-vdiff LDO config, unified swing/pre-emphasis tables,
> eDP/DP mode switch) is present in the tree tested here. The sweep below is
> from next-20260803; the machine has since run next-20260807 as its daily
> driver, where HBR3 still trains every boot.
I mentioned in my submission that this series is required on top:
https://lore.kernel.org/linux-arm-msm/20260622-glymur-edp-phy-v1-0-814b45089ac9@oss.qualcomm.com/
Konrad
next prev parent reply other threads:[~2026-08-18 10:39 UTC|newest]
Thread overview: 3+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-08 17:13 Jesse Casco
2026-08-18 10:39 ` Konrad Dybcio [this message]
2026-08-19 20:00 ` Jesse Casco
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=9fab8686-d0fa-40df-a6d0-75349861d78a@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@linaro.org \
--cc=abel.vesa@oss.qualcomm.com \
--cc=abhinav.kumar@linux.dev \
--cc=dri-devel@lists.freedesktop.org \
--cc=jesse.casco@gmail.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=lumag@kernel.org \
--cc=neil.armstrong@linaro.org \
--cc=robin.clark@oss.qualcomm.com \
--cc=vkoul@kernel.org \
--cc=yongxing.mou@oss.qualcomm.com \
/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®