From: Heiko Stuebner <heiko@sntech.de>
To: heiko@sntech.de
Cc: quentin.schulz@cherry.de, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/3] Move to gated-fixed-clock for Theobroma/Cherry boards
Date: Thu, 5 Feb 2026 11:21:01 +0100 [thread overview]
Message-ID: <20260205102104.394991-1-heiko@sntech.de> (raw)
Both Tiger and Jaguar currently use a fixed-clock and gpio-gate-clock
to model the PCIe clock generator they have.
Ever since I wrote the gated-fixed-clock binding + driver, I carry
around conversion patches for those boards to use the new binding
and describe actual hardware.
I submitted different versions in the initial submission of the
then still named "clock-generator" binding, but have reworked
them now to use the gated-fixed-clock binding that actually landed.
Heiko Stuebner (3):
arm64: dts: rockchip: use gated-fixed-clock for pcie-refclk on
rk3588-jaguar
arm64: dts: rockchip: use gated-fixed-clock for pcie-refclk on
rk3588-tiger
arm64: dts: rockchip: add pinctrl for clk-generator GPIO on
rk3588-tiger
.../arm64/boot/dts/rockchip/rk3588-jaguar.dts | 13 ++++--------
.../arm64/boot/dts/rockchip/rk3588-tiger.dtsi | 21 +++++++++++--------
2 files changed, 16 insertions(+), 18 deletions(-)
--
2.47.2
next reply other threads:[~2026-02-05 10:21 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-05 10:21 Heiko Stuebner [this message]
2026-02-05 10:21 ` [PATCH 1/3] arm64: dts: rockchip: use gated-fixed-clock for pcie-refclk on rk3588-jaguar Heiko Stuebner
2026-02-05 15:58 ` Quentin Schulz
2026-02-05 10:21 ` [PATCH 2/3] arm64: dts: rockchip: use gated-fixed-clock for pcie-refclk on rk3588-tiger Heiko Stuebner
2026-02-05 10:21 ` [PATCH 3/3] arm64: dts: rockchip: add pinctrl for clk-generator GPIO " Heiko Stuebner
2026-02-05 16:49 ` Quentin Schulz
2026-02-09 16:27 ` Heiko Stübner
2026-02-09 17:12 ` Quentin Schulz
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=20260205102104.394991-1-heiko@sntech.de \
--to=heiko@sntech.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-rockchip@lists.infradead.org \
--cc=quentin.schulz@cherry.de \
/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