mirror of https://lore.kernel.org/lkml/
 help / color / mirror / Atom feed
From: Heiko Stuebner <heiko@sntech.de>
To: heiko@sntech.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-kernel@vger.kernel.org, quentin.schulz@cherry.de,
	andyshrk@163.com, macromorgan@hotmail.com
Subject: [PATCH v2 0/2] Bring dclk_vop2 in line with other VPs on RK3588
Date: Wed,  4 Mar 2026 13:14:24 +0100	[thread overview]
Message-ID: <20260304121426.1184680-1-heiko@sntech.de> (raw)

The dclk for VP2 behaves differently and its use can currently break
other peripherals, so fix that and additionally allow it to drive
the same outputs.

I've kept Quentin's Tested-by from v1, as the overall change is the same
but did not transfer his Reviewed-by, as the series-structure changed.


changes in v2:
- split the actual fix for breakage and change of reparent handling
  into two separate patches

Heiko Stuebner (2):
  clk: rockchip: rk3588: Don't change PLL rates when setting
    dclk_vop2_src
  clk: rockchip: rk3588: Allow VP2 the same sourcing options as other
    VPs

 drivers/clk/rockchip/clk-rk3588.c | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

-- 
2.47.3


             reply	other threads:[~2026-03-04 12:14 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2026-03-04 12:14 Heiko Stuebner [this message]
2026-03-04 12:14 ` [PATCH v2 1/2] clk: rockchip: rk3588: Don't change PLL rates when setting dclk_vop2_src Heiko Stuebner
2026-03-10  9:30   ` Quentin Schulz
2026-03-10 10:25   ` Quentin Schulz
2026-03-04 12:14 ` [PATCH v2 2/2] clk: rockchip: rk3588: Allow VP2 the same sourcing options as other VPs Heiko Stuebner
2026-03-10  9:43   ` Quentin Schulz
2026-03-10 10:26   ` Quentin Schulz
2026-03-09 22:13 ` [PATCH v2 0/2] Bring dclk_vop2 in line with other VPs on RK3588 Chris Morgan
2026-07-07  9:41 ` 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=20260304121426.1184680-1-heiko@sntech.de \
    --to=heiko@sntech.de \
    --cc=andyshrk@163.com \
    --cc=linux-arm-kernel@lists.infradead.org \
    --cc=linux-clk@vger.kernel.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=macromorgan@hotmail.com \
    --cc=mturquette@baylibre.com \
    --cc=quentin.schulz@cherry.de \
    --cc=sboyd@kernel.org \
    --cc=sebastian.reichel@collabora.com \
    --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®