From: "Heiko Stübner" <heiko@sntech.de>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: mturquette@baylibre.com, sboyd@kernel.org,
zhangqing@rock-chips.com, sebastian.reichel@collabora.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] clk: rockchip: rk3588: Don't change PLL rates when setting dclk_vop2_src
Date: Wed, 15 Oct 2025 15:27:12 +0200 [thread overview]
Message-ID: <2749454.BddDVKsqQX@diego> (raw)
In-Reply-To: <6677ebf9-50bd-4df0-806c-9698f2256a8d@cherry.de>
Am Mittwoch, 15. Oktober 2025, 14:58:46 Mitteleuropäische Sommerzeit schrieb Quentin Schulz:
> Hi Heiko,
>
> On 10/8/25 3:31 PM, Heiko Stuebner wrote:
> > dclk_vop2_src currently has CLK_SET_RATE_PARENT | CLK_SET_RATE_NO_REPARENT
> > flags set, which is vastly different than dclk_vop0_src or dclk_vop1_src,
> > which have none of those.
> >
> > With these flags in dclk_vop2_src, actually setting the clock then results
> > in a lot of other peripherals breaking, because setting the rate results
> > in the PLL source getting changed:
> >
> > [ 14.898718] clk_core_set_rate_nolock: setting rate for dclk_vop2 to 152840000
> > [ 15.155017] clk_change_rate: setting rate for pll_gpll to 1680000000
> > [ clk adjusting every gpll user ]
> >
> > This includes possibly the other vops, i2s, spdif and even the uarts.
> > Among other possible things, this breaks the uart console on a board
> > I use. Sometimes it recovers later on, but there will be a big block
>
> I can reproduce on the same board as yours and this fixes the issue
> indeed (note I can only reproduce for now when display the modetest
> pattern, otherwise after boot the console seems fine to me).
I boot into a Debian rootfs with fbcon on my system, and the serial
console produces garbled output when the vop adjusts the clock
Sometimes it recovers after a bit, but other times it doesn't
> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
> Tested-by: Quentin Schulz <quentin.schulz@cherry.de> # RK3588 Tiger w/
> DP carrierboard
Thanks for testing
Heiko
WARNING: multiple messages have this Message-ID (diff)
From: "Heiko Stübner" <heiko@sntech.de>
To: Quentin Schulz <quentin.schulz@cherry.de>
Cc: mturquette@baylibre.com, sboyd@kernel.org,
zhangqing@rock-chips.com, sebastian.reichel@collabora.com,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
stable@vger.kernel.org
Subject: Re: [PATCH] clk: rockchip: rk3588: Don't change PLL rates when setting dclk_vop2_src
Date: Wed, 15 Oct 2025 15:27:12 +0200 [thread overview]
Message-ID: <2749454.BddDVKsqQX@diego> (raw)
In-Reply-To: <6677ebf9-50bd-4df0-806c-9698f2256a8d@cherry.de>
Am Mittwoch, 15. Oktober 2025, 14:58:46 Mitteleuropäische Sommerzeit schrieb Quentin Schulz:
> Hi Heiko,
>
> On 10/8/25 3:31 PM, Heiko Stuebner wrote:
> > dclk_vop2_src currently has CLK_SET_RATE_PARENT | CLK_SET_RATE_NO_REPARENT
> > flags set, which is vastly different than dclk_vop0_src or dclk_vop1_src,
> > which have none of those.
> >
> > With these flags in dclk_vop2_src, actually setting the clock then results
> > in a lot of other peripherals breaking, because setting the rate results
> > in the PLL source getting changed:
> >
> > [ 14.898718] clk_core_set_rate_nolock: setting rate for dclk_vop2 to 152840000
> > [ 15.155017] clk_change_rate: setting rate for pll_gpll to 1680000000
> > [ clk adjusting every gpll user ]
> >
> > This includes possibly the other vops, i2s, spdif and even the uarts.
> > Among other possible things, this breaks the uart console on a board
> > I use. Sometimes it recovers later on, but there will be a big block
>
> I can reproduce on the same board as yours and this fixes the issue
> indeed (note I can only reproduce for now when display the modetest
> pattern, otherwise after boot the console seems fine to me).
I boot into a Debian rootfs with fbcon on my system, and the serial
console produces garbled output when the vop adjusts the clock
Sometimes it recovers after a bit, but other times it doesn't
> Reviewed-by: Quentin Schulz <quentin.schulz@cherry.de>
> Tested-by: Quentin Schulz <quentin.schulz@cherry.de> # RK3588 Tiger w/
> DP carrierboard
Thanks for testing
Heiko
_______________________________________________
Linux-rockchip mailing list
Linux-rockchip@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/linux-rockchip
next prev parent reply other threads:[~2025-10-15 13:27 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-10-08 13:31 [PATCH] clk: rockchip: rk3588: Don't change PLL rates when setting dclk_vop2_src Heiko Stuebner
2025-10-08 13:31 ` Heiko Stuebner
2025-10-15 12:58 ` Quentin Schulz
2025-10-15 12:58 ` Quentin Schulz
2025-10-15 13:27 ` Heiko Stübner [this message]
2025-10-15 13:27 ` Heiko Stübner
2025-10-15 22:57 ` Sebastian Reichel
2025-10-15 22:57 ` Sebastian Reichel
2025-10-20 12:49 ` Heiko Stuebner
2025-10-20 12:49 ` Heiko Stuebner
2025-10-20 15:59 ` Sebastian Reichel
2025-10-20 15:59 ` Sebastian Reichel
2025-10-27 2:03 ` Andy Yan
2025-10-27 2:03 ` Andy Yan
2025-10-27 13:20 ` Sebastian Reichel
2025-10-27 13:20 ` Sebastian Reichel
2025-10-28 1:25 ` Andy Yan
2025-10-28 1:25 ` Andy Yan
2026-03-04 12:09 ` Heiko Stuebner
2026-03-04 12:09 ` Heiko Stuebner
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=2749454.BddDVKsqQX@diego \
--to=heiko@sntech.de \
--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=quentin.schulz@cherry.de \
--cc=sboyd@kernel.org \
--cc=sebastian.reichel@collabora.com \
--cc=stable@vger.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.