From: Konrad Dybcio <konrad.dybcio@oss.qualcomm.com>
To: Dmitry Baryshkov <dmitry.baryshkov@oss.qualcomm.com>,
Abel Vesa <abel.vesa@linaro.org>
Cc: Vinod Koul <vkoul@kernel.org>,
Kishon Vijay Abraham I <kishon@kernel.org>,
Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Bjorn Andersson <andersson@kernel.org>,
Dmitry Baryshkov <lumag@kernel.org>,
Konrad Dybcio <konradybcio@kernel.org>,
Neil Armstrong <neil.armstrong@linaro.org>,
Johan Hovold <johan@kernel.org>,
linux-arm-msm@vger.kernel.org, linux-phy@lists.infradead.org,
devicetree@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH v2 2/3] phy: qcom-qmp: qserdes-com: Add v8 DP-specific qserdes register offsets
Date: Tue, 9 Sep 2025 13:24:02 +0200 [thread overview]
Message-ID: <12ae186b-9816-4269-ab3a-7aacdc7cb954@oss.qualcomm.com> (raw)
In-Reply-To: <3xw54kzk36u7zrfhgva4p577nzle3ctzi3lyhcxapczv2bhceo@23zcaylkqoff>
On 9/9/25 1:19 PM, Dmitry Baryshkov wrote:
> On Tue, Sep 09, 2025 at 01:07:27PM +0300, Abel Vesa wrote:
>> Starting with Glymur, the PCIe and DP PHYs qserdes register offsets differ
>> for the same version number. So in order to be able to differentiate
>> between them, add these ones with DP prefix.
>>
>> Signed-off-by: Abel Vesa <abel.vesa@linaro.org>
>> ---
>> .../phy/qualcomm/phy-qcom-qmp-dp-qserdes-com-v8.h | 52 ++++++++++++++++++++++
>> 1 file changed, 52 insertions(+)
>>
>> diff --git a/drivers/phy/qualcomm/phy-qcom-qmp-dp-qserdes-com-v8.h b/drivers/phy/qualcomm/phy-qcom-qmp-dp-qserdes-com-v8.h
>> new file mode 100644
>> index 0000000000000000000000000000000000000000..2bef1eecdc56a75e954ebdbcd168ab7306be1302
>> --- /dev/null
>> +++ b/drivers/phy/qualcomm/phy-qcom-qmp-dp-qserdes-com-v8.h
>> @@ -0,0 +1,52 @@
>> +/* SPDX-License-Identifier: GPL-2.0 */
>> +/*
>> + * Copyright (C) 2025 Linaro Ltd.
>> + */
>> +
>> +#ifndef QCOM_PHY_QMP_DP_QSERDES_COM_V8_H_
>> +#define QCOM_PHY_QMP_DP_QSERDES_COM_V8_H_
>> +
>> +/* Only for DP QMP V8 PHY - QSERDES COM registers */
>> +#define DP_QSERDES_V8_COM_HSCLK_SEL_1 0x03c
>> +#define DP_QSERDES_V8_COM_BIN_VCOCAL_CMP_CODE1_MODE0 0x058
>> +#define DP_QSERDES_V8_COM_BIN_VCOCAL_CMP_CODE2_MODE0 0x05c
>> +#define DP_QSERDES_V8_COM_SSC_STEP_SIZE1_MODE0 0x060
>> +#define DP_QSERDES_V8_COM_SSC_STEP_SIZE2_MODE0 0x064
>> +#define DP_QSERDES_V8_COM_CP_CTRL_MODE0 0x070
>> +#define DP_QSERDES_V8_COM_PLL_RCTRL_MODE0 0x074
>> +#define DP_QSERDES_V8_COM_PLL_CCTRL_MODE0 0x078
>> +#define DP_QSERDES_V8_COM_CORECLK_DIV_MODE0 0x07c
>> +#define DP_QSERDES_V8_COM_LOCK_CMP1_MODE0 0x080
>> +#define DP_QSERDES_V8_COM_LOCK_CMP2_MODE0 0x084
>> +#define DP_QSERDES_V8_COM_DEC_START_MODE0 0x088
>> +#define DP_QSERDES_V8_COM_DIV_FRAC_START1_MODE0 0x090
>> +#define DP_QSERDES_V8_COM_DIV_FRAC_START2_MODE0 0x094
>> +#define DP_QSERDES_V8_COM_DIV_FRAC_START3_MODE0 0x098
>> +#define DP_QSERDES_V8_COM_INTEGLOOP_GAIN0_MODE0 0x0a0
>> +#define DP_QSERDES_V8_COM_VCO_TUNE1_MODE0 0x0a8
>> +#define DP_QSERDES_V8_COM_INTEGLOOP_GAIN1_MODE0 0x0a4
>> +#define DP_QSERDES_V8_COM_VCO_TUNE2_MODE0 0x0ac
>> +#define DP_QSERDES_V8_COM_BG_TIMER 0x0bc
>> +#define DP_QSERDES_V8_COM_SSC_EN_CENTER 0x0c0
>> +#define DP_QSERDES_V8_COM_SSC_ADJ_PER1 0x0c4
>> +#define DP_QSERDES_V8_COM_SSC_PER1 0x0cc
>> +#define DP_QSERDES_V8_COM_SSC_PER2 0x0d0
>> +#define DP_QSERDES_V8_COM_BIAS_EN_CLKBUFLR_EN 0x0dc
>> +#define DP_QSERDES_V8_COM_CLK_ENABLE1 0x0e0
>> +#define DP_QSERDES_V8_COM_SYS_CLK_CTRL 0x0e4
>> +#define DP_QSERDES_V8_COM_SYSCLK_BUF_ENABLE 0x0e8
>> +#define DP_QSERDES_V8_COM_PLL_IVCO 0x0f4
>> +#define DP_QSERDES_V8_COM_SYSCLK_EN_SEL 0x110
>> +#define DP_QSERDES_V8_COM_RESETSM_CNTRL 0x118
>> +#define DP_QSERDES_V8_COM_LOCK_CMP_EN 0x120
>> +#define DP_QSERDES_V8_COM_VCO_TUNE_CTRL 0x13c
>> +#define DP_QSERDES_V8_COM_VCO_TUNE_MAP 0x140
>> +#define DP_QSERDES_V8_COM_CLK_SELECT 0x164
>> +#define DP_QSERDES_V8_COM_CORE_CLK_EN 0x170
>> +#define DP_QSERDES_V8_COM_CMN_CONFIG_1 0x174
>
> The registers are the same at least up to this point. Would it make
> sense to keep common part in the same header and define only those bits
> that actually differ between DP and PCIe parts? (Is it really about PCIe
> or is it eDP vs everything else?)
No, there's a wild amount of variation between various "v8" PHYs and this
is impossible to catch by eye
Konrad
--
linux-phy mailing list
linux-phy@lists.infradead.org
https://lists.infradead.org/mailman/listinfo/linux-phy
next prev parent reply other threads:[~2025-09-09 17:14 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-09 10:07 [PATCH v2 0/3] phy: qcom: edp: Add support for Glymur platform Abel Vesa
2025-09-09 10:07 ` [PATCH v2 1/3] dt-bindings: phy: Add DP PHY compatible for Glymur Abel Vesa
2025-09-10 11:32 ` Krzysztof Kozlowski
2025-09-11 9:02 ` Abel Vesa
2025-09-09 10:07 ` [PATCH v2 2/3] phy: qcom-qmp: qserdes-com: Add v8 DP-specific qserdes register offsets Abel Vesa
2025-09-09 11:19 ` Dmitry Baryshkov
2025-09-09 11:24 ` Konrad Dybcio [this message]
2025-09-09 11:40 ` Dmitry Baryshkov
2025-09-09 10:07 ` [PATCH v2 3/3] phy: qcom: edp: Add Glymur platform support Abel Vesa
2025-09-09 11:12 ` Dmitry Baryshkov
2025-09-11 8:52 ` Abel Vesa
2025-09-11 9:18 ` Konrad Dybcio
2025-09-11 12:33 ` Abel Vesa
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=12ae186b-9816-4269-ab3a-7aacdc7cb954@oss.qualcomm.com \
--to=konrad.dybcio@oss.qualcomm.com \
--cc=abel.vesa@linaro.org \
--cc=andersson@kernel.org \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=dmitry.baryshkov@oss.qualcomm.com \
--cc=johan@kernel.org \
--cc=kishon@kernel.org \
--cc=konradybcio@kernel.org \
--cc=krzk+dt@kernel.org \
--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=robh@kernel.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