mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Yongxing Mou <yongxing.mou@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>
Cc: 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 1/3] phy: qcom: edp: Correct and clean up eDP/DP combo PHY configuration values
Date: Tue, 10 Feb 2026 18:17:07 +0800	[thread overview]
Message-ID: <23e007dc-4145-4260-8810-1e98e533b1b5@oss.qualcomm.com> (raw)
In-Reply-To: <w3vmcgeh5bw7lfuyv7ziiw3oxpxtjyqmojddamjo5alz4nv7ld@ytgjwdhecfua>



On 2/9/2026 8:47 PM, Dmitry Baryshkov wrote:
> On Mon, Feb 09, 2026 at 05:52:22PM +0800, Yongxing Mou wrote:
>>
>>
>> On 2/7/2026 6:22 PM, Dmitry Baryshkov wrote:
>>> On Thu, Feb 05, 2026 at 05:20:53PM +0800, Yongxing Mou wrote:
>>>> According to the current HPG settings, most eDP/DP combo PHYs can reuse the
>>>> same configuration values.
>>>> DP mode:
>>>> 	-sa8775p/sc7280/sc8280xp/x1e80100
>>>> 	-glymur
>>>> eDP mode(low vdiff):
>>>> 	-glymur/sa8775p/sc8280xp/x1e80100
>>>> 	-sc7280
>>>> The current driver still keeps multiple versions of these tables and
>>>> doesn't fully support every combo PHY mode. This patch removes the
>>>
>>> See Documentation/process/submitting-patches.rst, "This patch".
>>>
>> Sure. got it thanks, will remove "This patch".
>>>> redundant configs and keeps only the sets we actually use, matching the
>>>> platforms listed above.
>>>
>>> Should it be combined with the 3rd patch? There you sort out all the
>>> tables, it makes more sense to review all programming together.
>>>
>> Hi, if this would help with your review work, I’m very happy to do it.
>> My original intention was to do some cleanup in this patch—correct the table
>> values so that more platforms can reuse the same table.
> 
> Fixed should come before cleanups (so that they can be backported to
> stable kernels).
> 
Hi, do you mean the second LDO patch should come before the first 
patch?In fact, maybe three patches should go into the stable branch. The 
LDO patch cannot be used on its own. On both sa8775p and hamoa, their 
eDP/DP modes do not match the tables they are currently using (hamoa 
should use the eDP table, while sa8775p should use the DP table). If 
only the LDO patch is applied, it may cause link training to fail.
>>  From Konard’s comments, it seems that the HPG table may not be the most
>> appropriate one either.
>> Maybe shoud first determine what the correct table values should be.
> 
> Please follow the tables for each SKU separately (that's the 'fix'
> part).
> 
Sure.


  reply	other threads:[~2026-02-10 10:17 UTC|newest]

Thread overview: 26+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-02-05  9:20 [PATCH 0/3] phy: qcom: edp: Add DP/eDP switch for phys Yongxing Mou
2026-02-05  9:20 ` [PATCH 1/3] phy: qcom: edp: Correct and clean up eDP/DP combo PHY configuration values Yongxing Mou
2026-02-06 10:47   ` Konrad Dybcio
2026-02-09  9:00     ` Yongxing Mou
2026-02-09 12:46       ` Dmitry Baryshkov
2026-02-10  6:13         ` Yongxing Mou
2026-02-13 11:08       ` Konrad Dybcio
2026-02-07 10:22   ` Dmitry Baryshkov
2026-02-09  9:52     ` Yongxing Mou
2026-02-09 12:47       ` Dmitry Baryshkov
2026-02-10 10:17         ` Yongxing Mou [this message]
2026-02-10 12:33           ` Dmitry Baryshkov
2026-02-05  9:20 ` [PATCH 2/3] phy: qcom: edp: Add per-version LDO configuration callback Yongxing Mou
2026-02-06 10:52   ` Konrad Dybcio
2026-02-10 10:19     ` Yongxing Mou
2026-02-12  9:04     ` Yongxing Mou
2026-02-13 11:14       ` Konrad Dybcio
2026-02-25  7:21         ` Yongxing Mou
2026-02-07 10:17   ` Dmitry Baryshkov
2026-02-10 10:21     ` Yongxing Mou
2026-02-05  9:20 ` [PATCH 3/3] phy: qcom: edp: Add eDP phy mode switch support Yongxing Mou
2026-02-06 11:02   ` Konrad Dybcio
2026-02-10 10:29     ` Yongxing Mou
2026-02-13 11:06       ` Konrad Dybcio
2026-02-25  8:00         ` Yongxing Mou
2026-02-07 10:20   ` 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=23e007dc-4145-4260-8810-1e98e533b1b5@oss.qualcomm.com \
    --to=yongxing.mou@oss.qualcomm.com \
    --cc=dmitry.baryshkov@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®