From: Xiangyu Zhu <1194781887@qq.com>
To: Heiko Stuebner <heiko@sntech.de>, Stephen Boyd <sboyd@kernel.org>
Cc: Xiangyu Zhu <1194781887@qq.com>,
Michael Turquette <mturquette@baylibre.com>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
linux-clk@vger.kernel.org, linux-rockchip@lists.infradead.org,
linux-arm-kernel@lists.infradead.org, devicetree@vger.kernel.org,
linux-kernel@vger.kernel.org
Subject: [PATCH v2 0/2] clk: rockchip: rk3506: Add the SAI MCLK output gate clocks
Date: Mon, 23 Nov 2026 00:24:44 +0800 [thread overview]
Message-ID: <tencent_DFDA05189A0FAFA816FFAB91CC2F95247C09@qq.com> (raw)
The RK3506 has four SAI MCLK output gates: SAI0 and SAI1 are controlled
by bits in the PMU GRF, SAI2 and SAI3 by bits in the system GRF. Model
them as GRF gate clocks so the SAI MCLK pin direction can be controlled
through the clock framework.
This is a v2 of the earlier "[PATCH] dt-bindings: clock: add
rockchip,clk-out" submission. That one introduced a generic
"rockchip,clk-out" compatible plus a standalone driver, which is not
acceptable: upstream already has generic GRF gate support
(branch_grf_gate together with rockchip_clk_add_grf()), and RK3576 and
RK3588 register their SAI/I2S MCLK output gates with it. The new
binding and the driver are therefore dropped entirely, and this series
only adds the four gates to clk-rk3506.c plus their clock IDs. No
device tree changes are included.
Tested on a RK3506B board: the SAI0 MCLK output runs at 12.288 MHz and
drives the ES8388 codec, audio playback works, and the GRF gate bits
were read back from the registers to confirm that they get set.
Changes since v1:
- drop the rockchip,clk-out binding and driver
- use the existing GATE_GRF support like RK3576 and RK3588 do
- limit the series to the clock driver and the dt-bindings IDs
Xiangyu Zhu (2):
dt-bindings: clock: rockchip,rk3506-cru: Add SAI MCLK output gate IDs
clk: rockchip: rk3506: Register the SAI MCLK output gates
drivers/clk/rockchip/clk-rk3506.c | 23 +++++++++++++++++++
.../dt-bindings/clock/rockchip,rk3506-cru.h | 4 ++++
2 files changed, 27 insertions(+)
--
2.47.3
reply other threads:[~2026-11-22 16:25 UTC|newest]
Thread overview: [no followups] expand[flat|nested] mbox.gz Atom feed
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=tencent_DFDA05189A0FAFA816FFAB91CC2F95247C09@qq.com \
--to=1194781887@qq.com \
--cc=conor+dt@kernel.org \
--cc=devicetree@vger.kernel.org \
--cc=heiko@sntech.de \
--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=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
all inboxes | Powered by JetHome®