[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <93690c52-7da7-4fee-9b58-6087b3fb1d71@kernel.org>
Date: Mon, 13 May 2024 08:38:38 +0200
From: Krzysztof Kozlowski <krzk@...nel.org>
To: Liankun Yang <liankun.yang@...iatek.com>, chunkuang.hu@...nel.org,
p.zabel@...gutronix.de, airlied@...il.com, daniel@...ll.ch,
maarten.lankhorst@...ux.intel.com, mripard@...nel.org, tzimmermann@...e.de,
robh+dt@...nel.org, krzysztof.kozlowski+dt@...aro.org, conor+dt@...nel.org,
chunfeng.yun@...iatek.com, vkoul@...nel.org, kishon@...nel.org,
matthias.bgg@...il.com, angelogioacchino.delregno@...labora.com,
jitao.shi@...iatek.com, mac.shen@...iatek.com,
Project_Global_Chrome_Upstream_Group@...iatek.com
Cc: dri-devel@...ts.freedesktop.org, linux-mediatek@...ts.infradead.org,
devicetree@...r.kernel.org, linux-arm-kernel@...ts.infradead.org,
linux-kernel@...r.kernel.org, linux-phy@...ts.infradead.org
Subject: Re: [PATCH v2 1/2] Add write DP phyd register from parse dts
On 10/05/2024 13:04, Liankun Yang wrote:
> During the testing phase, screen flickering is observed when
> using displayport for screen casting. Relevant SSC register parameters
> are set in dts to address the screen flickering issue effectively and
> improve compatibility with different devices by adjusting the SSC gear.
>
> Obtaining the DPTX node, parsing the dts to obtain PHY register address
> and value can adapt to settings of different manufacturers projects.
>
> Changeds in v2:
> - Optimized method of writing to DP PHY register
> https://patchwork.kernel.org/project/linux-mediatek/patch/
> 20240403040517.3279-1-liankun.yang@...iatek.com/
>
> Signed-off-by: Liankun Yang <liankun.yang@...iatek.com>
> ---
> drivers/phy/mediatek/phy-mtk-dp.c | 37 +++++++++++++++++++++++++++++++
> 1 file changed, 37 insertions(+)
>
> diff --git a/drivers/phy/mediatek/phy-mtk-dp.c b/drivers/phy/mediatek/phy-mtk-dp.c
> index d7024a144335..ce78112d5938 100644
> --- a/drivers/phy/mediatek/phy-mtk-dp.c
> +++ b/drivers/phy/mediatek/phy-mtk-dp.c
> @@ -28,6 +28,10 @@
> #define MTK_DP_PHY_DIG_SW_RST (PHY_OFFSET + 0x38)
> #define DP_GLB_SW_RST_PHYD BIT(0)
>
> +#define MTK_DP_PHY_DIG_GLB_DA_REG_14 (PHY_OFFSET + 0xD8)
> +#define XTP_GLB_TXPLL_SSC_DELTA_RBR_DEFAULT GENMASK(15, 0)
> +#define XTP_GLB_TXPLL_SSC_DELTA_HBR_DEFAULT GENMASK(31, 16)
> +
> #define MTK_DP_LANE0_DRIVING_PARAM_3 (PHY_OFFSET + 0x138)
> #define MTK_DP_LANE1_DRIVING_PARAM_3 (PHY_OFFSET + 0x238)
> #define MTK_DP_LANE2_DRIVING_PARAM_3 (PHY_OFFSET + 0x338)
> @@ -78,10 +82,39 @@
> #define DRIVING_PARAM_8_DEFAULT (XTP_LN_TX_LCTXCP1_SW2_PRE1_DEFAULT | \
> XTP_LN_TX_LCTXCP1_SW3_PRE0_DEFAULT)
>
> +#define SSC_SETTING "dp-ssc-setting"
> +#define RG_XTP_GLB_TXPLL_SSC_DELTA_HBR "ssc-delta-hbr"
> +
> struct mtk_dp_phy {
> struct regmap *regs;
> + struct device *dev;
> };
>
> +static int mtk_dp_set_ssc_config(struct phy *phy, struct mtk_dp_phy *dp_phy)
> +{
> + int ret;
> + u32 read_value = 0, reg_mask = 0;
> + struct device_node *ssc_node = NULL;
> +
> + ssc_node = of_find_node_by_name(dp_phy->dev->of_node, SSC_SETTING);
No, really. Node name can change.
Best regards,
Krzysztof
Powered by blists - more mailing lists