From: Jonas Karlman <jonas@kwiboo.se>
To: Elaine Zhang <zhangqing@rock-chips.com>
Cc: mturquette@baylibre.com, sboyd@kernel.org,
kever.yang@rock-chips.com, heiko@sntech.de, robh@kernel.org,
krzk+dt@kernel.org, conor+dt@kernel.org,
linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-kernel@vger.kernel.org, huangtao@rock-chips.com,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH v2 2/3] Revert "arm64: dts: rockchip: Increase VOP clk rate on RK3328"
Date: Sat, 25 Jan 2025 22:39:27 +0100 [thread overview]
Message-ID: <d1ddec89-08d5-4eed-8ecc-7df47294230a@kwiboo.se> (raw)
In-Reply-To: <20250125011545.15547-3-zhangqing@rock-chips.com>
Hi Elaine,
On 2025-01-25 02:15, Elaine Zhang wrote:
> This reverts commit 0f2ddb128fa20f8441d903285632f2c69e90fae1.
>
> Before changing the PLL frequency, in order to avoid overclocking the
> child clock, set the child clock to a large div first, and then set the
> CLK as required after the PLL is set.
This commit message does not match what this patch does. In this patch
you revert a change and in next patch you re-introduce same thing
slightly different.
As mentioned in v1, see [1], you should merge both patches as a single
fix, if a fix really is needed.
Testing on a rk3328-rock64 I see no difference before or after these
changes. Please describe what this fixes because clk_summary show same
clock tree and rates before and after this fix.
Also for next revert patch you send, please include the patch author in
the recipient list :-)
[1] https://lore.kernel.org/all/cae9cb0a-1500-4fbc-bbf4-a6266549bcb9@kwiboo.se/
Regards,
Jonas
>
> Fixes: 0f2ddb128fa2 ("arm64: dts: rockchip: Increase VOP clk rate on RK3328")
>
> Signed-off-by: Elaine Zhang <zhangqing@rock-chips.com>
> ---
> arch/arm64/boot/dts/rockchip/rk3328.dtsi | 4 ++--
> 1 file changed, 2 insertions(+), 2 deletions(-)
>
> diff --git a/arch/arm64/boot/dts/rockchip/rk3328.dtsi b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> index 7d992c3c01ce..f3ef8cbfbdae 100644
> --- a/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> +++ b/arch/arm64/boot/dts/rockchip/rk3328.dtsi
> @@ -852,8 +852,8 @@
> <0>, <24000000>,
> <24000000>, <24000000>,
> <15000000>, <15000000>,
> - <300000000>, <100000000>,
> - <400000000>, <100000000>,
> + <100000000>, <100000000>,
> + <100000000>, <100000000>,
> <50000000>, <100000000>,
> <100000000>, <100000000>,
> <50000000>, <50000000>,
next prev parent reply other threads:[~2025-01-25 21:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-25 1:15 [PATCH v2 0/3] clk: rockchip: Fixed some incorrect commits Elaine Zhang
2025-01-25 1:15 ` [PATCH v2 1/3] Revert "clk: rockchip: Set parent rate for DCLK_VOP clock on RK3228" Elaine Zhang
2025-01-25 5:38 ` Alex Bee
2025-01-25 21:28 ` Jonas Karlman
2025-01-25 1:15 ` [PATCH v2 2/3] Revert "arm64: dts: rockchip: Increase VOP clk rate on RK3328" Elaine Zhang
2025-01-25 21:39 ` Jonas Karlman [this message]
2025-02-05 2:18 ` zhangqing
2025-01-25 1:15 ` [PATCH v2 3/3] arm64: dts: rockchip: Increase VOP clk rate on RK3328 Elaine Zhang
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=d1ddec89-08d5-4eed-8ecc-7df47294230a@kwiboo.se \
--to=jonas@kwiboo.se \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--cc=huangtao@rock-chips.com \
--cc=kever.yang@rock-chips.com \
--cc=krzk+dt@kernel.org \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=mturquette@baylibre.com \
--cc=robh@kernel.org \
--cc=sboyd@kernel.org \
--cc=zhangqing@rock-chips.com \
/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®