From: Alex Bee <knaerzche@gmail.com>
To: Rob Herring <robh@kernel.org>,
Krzysztof Kozlowski <krzk+dt@kernel.org>,
Conor Dooley <conor+dt@kernel.org>,
Heiko Stuebner <heiko@sntech.de>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
devicetree@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
linux-clk@vger.kernel.org, Alex Bee <knaerzche@gmail.com>
Subject: [PATCH v2 0/5] Add SFC support for RK3128
Date: Wed, 5 Jun 2024 22:52:04 +0200 [thread overview]
Message-ID: <20240605205209.232005-6-knaerzche@gmail.com> (raw)
In-Reply-To: <20240605205209.232005-1-knaerzche@gmail.com>
This series adds support for the Serial Flash Controller (SFC) found in
RK3128 SoCs.
As without using some "id holes" we would run out clock ids in the binding
and would have to touch the ABI, I added patches which removes the
CLK_NR_CLKS macro and uses the recently introduced
rockchip_clk_find_max_clk_id helper instead to find the highest clock id.
changes since v1:
- added patches to remove CLK_NR_CLKS (Connor)
Link to v1:
https://lore.kernel.org/all/20240605172154.193047-1-knaerzche@gmail.com/
Alex Bee (5):
clk: rockchip: rk3128: Drop CLK_NR_CLKS usage
dt-bindings: clock: rk3128: Drop CLK_NR_CLKS
dt-bindings: clock: rk3128: Add HCLK_SFC
clk: rockchip: Add HCLK_SFC for RK3128
ARM: dts: rockchip: Add SFC for RK3128
arch/arm/boot/dts/rockchip/rk3128.dtsi | 35 ++++++++++++++++++++++++++
drivers/clk/rockchip/clk-rk3128.c | 21 +++++++++++++---
include/dt-bindings/clock/rk3128-cru.h | 2 +-
3 files changed, 53 insertions(+), 5 deletions(-)
base-commit: 234cb065ad82915ff8d06ce01e01c3e640b674d2
--
2.45.2
next prev parent reply other threads:[~2024-06-05 20:52 UTC|newest]
Thread overview: 17+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-06-05 20:51 [PATCH 1/5] clk: rockchip: rk3128: Drop CLK_NR_CLKS usage Alex Bee
2024-06-05 20:52 ` [PATCH 2/5] dt-bindings: clock: rk3128: Drop CLK_NR_CLKS Alex Bee
2024-06-06 6:40 ` Krzysztof Kozlowski
2024-06-05 20:52 ` [PATCH 3/5] dt-bindings: clock: rk3128: Add HCLK_SFC Alex Bee
2024-06-06 6:40 ` Krzysztof Kozlowski
2024-06-05 20:52 ` [PATCH 4/5] clk: rockchip: Add HCLK_SFC for RK3128 Alex Bee
2024-06-05 20:52 ` [PATCH 5/5] ARM: dts: rockchip: Add SFC " Alex Bee
2024-06-05 20:52 ` Alex Bee [this message]
2024-06-06 6:41 ` [PATCH v2 0/5] Add SFC support " Krzysztof Kozlowski
2024-06-06 7:37 ` Heiko Stübner
2024-06-06 10:12 ` Alex Bee
2024-06-05 20:52 ` [PATCH v2 1/5] clk: rockchip: rk3128: Drop CLK_NR_CLKS usage Alex Bee
2024-06-05 20:52 ` [PATCH v2 2/5] dt-bindings: clock: rk3128: Drop CLK_NR_CLKS Alex Bee
2024-06-05 20:52 ` [PATCH v2 3/5] dt-bindings: clock: rk3128: Add HCLK_SFC Alex Bee
2024-06-05 20:52 ` [PATCH v2 4/5] clk: rockchip: Add HCLK_SFC for RK3128 Alex Bee
2024-06-05 20:52 ` [PATCH v2 5/5] ARM: dts: rockchip: Add SFC " Alex Bee
2024-06-05 21:03 ` [PATCH 1/5] clk: rockchip: rk3128: Drop CLK_NR_CLKS usage Alex Bee
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=20240605205209.232005-6-knaerzche@gmail.com \
--to=knaerzche@gmail.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=robh@kernel.org \
--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;
as well as URLs for NNTP newsgroup(s).