From: "Heiko Stübner" <heiko@sntech.de>
To: linux-rockchip@lists.infradead.org,
Alexander Shiyan <eagle.alexander923@gmail.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
Alexander Shiyan <eagle.alexander923@gmail.com>,
Kever Yang <kever.yang@rock-chips.com>
Subject: Re: [PATCH 1/2] clk: rockchip: clk-pll: Fix CRU_xx_CON2 register usage
Date: Tue, 08 Apr 2025 09:31:36 +0200 [thread overview]
Message-ID: <3871892.kQq0lBPeGt@diego> (raw)
In-Reply-To: <20250408063126.38904-1-eagle.alexander923@gmail.com>
Hi Alexander,
Am Dienstag, 8. April 2025, 08:31:25 Mitteleuropäische Sommerzeit schrieb Alexander Shiyan:
> According to RK3588 TRM, CRU_(CPLL/GPLL/etc)_CON2 register
> (rate-k value) does not use highword write enable mask.
> Lets fix this.
>
> Signed-off-by: Alexander Shiyan <eagle.alexander923@gmail.com>
The commit message doesn't say, but did you check this on actual
hardware too?
Sometimes there is a disconnect between the TRM and actual hardware,
so the actual real-life situation should be checked.
As for a test-case, any write without write-mask to a register that
would require a write-mask would not come through.
So with your patch applied, does the register value change after
the write below when reading it back again?
Thanks
Heiko
> ---
> drivers/clk/rockchip/clk-pll.c | 2 +-
> 1 file changed, 1 insertion(+), 1 deletion(-)
>
> diff --git a/drivers/clk/rockchip/clk-pll.c b/drivers/clk/rockchip/clk-pll.c
> index 2c2abb3b4210..77ba4d6e7b5f 100644
> --- a/drivers/clk/rockchip/clk-pll.c
> +++ b/drivers/clk/rockchip/clk-pll.c
> @@ -959,7 +959,7 @@ static int rockchip_rk3588_pll_set_params(struct rockchip_clk_pll *pll,
> HIWORD_UPDATE(rate->s, RK3588_PLLCON1_S_MASK, RK3588_PLLCON1_S_SHIFT),
> pll->reg_base + RK3399_PLLCON(1));
>
> - writel_relaxed(HIWORD_UPDATE(rate->k, RK3588_PLLCON2_K_MASK, RK3588_PLLCON2_K_SHIFT),
> + writel_relaxed((rate->k & RK3588_PLLCON2_K_MASK) << RK3588_PLLCON2_K_SHIFT,
> pll->reg_base + RK3399_PLLCON(2));
>
> /* set pll power up */
>
next prev parent reply other threads:[~2025-04-08 7:39 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-08 6:31 [PATCH 1/2] clk: rockchip: clk-pll: Fix CRU_xx_CON2 register usage Alexander Shiyan
2025-04-08 6:31 ` [PATCH 2/2] clk: rockchip: clk-pll: Typo fix Alexander Shiyan
2025-04-08 7:31 ` Heiko Stübner [this message]
2025-04-08 10:50 ` [PATCH 1/2] clk: rockchip: clk-pll: Fix CRU_xx_CON2 register usage Alexander Shiyan
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=3871892.kQq0lBPeGt@diego \
--to=heiko@sntech.de \
--cc=eagle.alexander923@gmail.com \
--cc=kever.yang@rock-chips.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=sboyd@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;
as well as URLs for NNTP newsgroup(s).