From: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
To: Algea Cao <algea.cao@rock-chips.com>,
vkoul@kernel.org, kishon@kernel.org, heiko@sntech.de,
andy.yan@rock-chips.com
Cc: linux-phy@lists.infradead.org,
linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: Re: [PATCH] phy: phy-rockchip-samsung-hdptx: Fix PHY PLL output 50.25MHz error
Date: Fri, 25 Apr 2025 09:12:22 +0300 [thread overview]
Message-ID: <eb1f0bf7-3827-488e-925f-18c8fee9b1a2@collabora.com> (raw)
In-Reply-To: <20250425023720.3296069-1-algea.cao@rock-chips.com>
Hi Algea,
On 4/25/25 5:37 AM, Algea Cao wrote:
> When using HDMI PLL frequency division coefficient at 50.25MHz
> that calculated by rk_hdptx_phy_clk_pll_calc(), it is failed to
s/that/that is/
s/is failed/it fails/
> get PHY LANE lock. Although the calculated values are within the
> allowable range of PHY PLL configuration.
>
> So we manually calculated PHY PLL frequency division coefficient
> at 50.25Mhz and added it to ropll_tmds_cfg. Manually calculated
> value can make PHY LANE lock normally and output 50.25MHz normally.
I'd reword this paragraph using imperative sentences, e.g.:
In order to fix the PHY LANE lock error and provide the expected
50.25MHz output, manually compute the required PHY PLL frequency
division coefficient and add it to ropll_tmds_cfg configuration table.
> Signed-off-by: Algea Cao <algea.cao@rock-chips.com>
> ---
> drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c | 2 ++
> 1 file changed, 2 insertions(+)
>
> diff --git a/drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c b/drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c
> index fe7c05748356..77236f012a1f 100644
> --- a/drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c
> +++ b/drivers/phy/rockchip/phy-rockchip-samsung-hdptx.c
> @@ -476,6 +476,8 @@ static const struct ropll_config ropll_tmds_cfg[] = {
> 1, 1, 0, 0x20, 0x0c, 1, 0x0e, 0, 0, },
> { 650000, 162, 162, 1, 1, 11, 1, 1, 1, 1, 1, 1, 1, 54, 0, 16, 4, 1,
> 1, 1, 0, 0x20, 0x0c, 1, 0x0e, 0, 0, },
> + { 502500, 84, 84, 1, 1, 7, 1, 1, 1, 1, 1, 1, 1, 11, 1, 4, 5,
> + 4, 11, 1, 0, 0x20, 0x0c, 1, 0x0e, 0, 0, },
> { 337500, 0x70, 0x70, 1, 1, 0xf, 1, 1, 1, 1, 1, 1, 1, 0x2, 0, 0x01, 5,
> 1, 1, 1, 0, 0x20, 0x0c, 1, 0x0e, 0, 0, },
> { 400000, 100, 100, 1, 1, 11, 1, 1, 0, 1, 0, 1, 1, 0x9, 0, 0x05, 0,
With the above fixed,
Reviewed-by: Cristian Ciocaltea <cristian.ciocaltea@collabora.com>
Thanks,
Cristian
prev parent reply other threads:[~2025-04-25 6:12 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-25 2:37 Algea Cao
2025-04-25 6:12 ` Cristian Ciocaltea [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=eb1f0bf7-3827-488e-925f-18c8fee9b1a2@collabora.com \
--to=cristian.ciocaltea@collabora.com \
--cc=algea.cao@rock-chips.com \
--cc=andy.yan@rock-chips.com \
--cc=heiko@sntech.de \
--cc=kishon@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-phy@lists.infradead.org \
--cc=linux-rockchip@lists.infradead.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®