mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Burke Cates <burke.cates@gmail.com>
To: ccortner@gmail.com
Cc: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>,
	Bjorn Andersson <bjorn.andersson@oss.qualcomm.com>,
	Vinod Koul <vkoul@kernel.org>,
	Neil Armstrong <neil.armstrong@linaro.org>,
	linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
	linux-kernel@vger.kernel.org
Subject: Re: [PATCH 2/2] phy: qcom: edp: update v8 power-on programming sequence
Date: Tue,  3 Nov 2026 23:27:37 -0800	[thread overview]
Message-ID: <20261104072737.3489383-1-burke.cates@gmail.com> (raw)
In-Reply-To: <179346367993.44447.8683103034067826560.x2e-share-edp@gmail.com>

On Sat, Oct 31, 2026 at 11:24:31AM -0500, Christian Cortner wrote:
> Writing the firmware values at the end of power-on, all 120 enables
> over two boots trained 4 lanes cleanly, and 10 of 10 resumes. Which
> register matters is not known. Happy to test a revision.

Same result on another Zenbook A16 (eDP at HBR2 x4): v7.4-rc1 with
Bjorn's v1 as posted (ldo_config 0xd0, not 0x91), out-of-tree Glymur
board patches, and your five values written after DCC. Link enables
with at least one failed training attempt, over fbdev blank/unblank
cycles and boots:

  without the values: 30 of 400 enables, 8 of 61 boots
  with the values:     0 of 500 enables, 0 of 162 boots

One dpu_encoder_virt_atomic_disable() "enc42 timeout pending" at a
blank (1 in 500) appeared only with the values; cause unknown.

AI coding assistants helped run these tests and draft this reply; the
results are from the hardware runs.

Thanks,
Burke

      reply	other threads:[~2026-11-04  7:27 UTC|newest]

Thread overview: 7+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-06-22 23:29 [PATCH 0/2] phy: qcom: edp: Update v8 " Bjorn Andersson
2026-06-22 23:29 ` [PATCH 1/2] phy: qcom: edp: split power-on sequencing by PHY version Bjorn Andersson
2026-06-23  7:37   ` Konrad Dybcio
2026-06-22 23:29 ` [PATCH 2/2] phy: qcom: edp: update v8 power-on programming sequence Bjorn Andersson
2026-06-23  9:10   ` Konrad Dybcio
2026-10-31 16:24     ` Christian Cortner
2026-11-04  7:27       ` Burke Cates [this message]

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=20261104072737.3489383-1-burke.cates@gmail.com \
    --to=burke.cates@gmail.com \
    --cc=bjorn.andersson@oss.qualcomm.com \
    --cc=ccortner@gmail.com \
    --cc=konrad.dybcio@oss.qualcomm.com \
    --cc=linux-arm-msm@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=linux-phy@lists.infradead.org \
    --cc=neil.armstrong@linaro.org \
    --cc=vkoul@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®