From: Johan Jonker <jbx6244@gmail.com>
To: heiko@sntech.de
Cc: robh@kernel.org, conor+dt@kernel.org, krzk+dt@kernel.org,
mturquette@baylibre.com, sboyd@kernel.org,
linux-clk@vger.kernel.org, linux-arm-kernel@lists.infradead.org,
linux-rockchip@lists.infradead.org, linux-kernel@vger.kernel.org,
devicetree@vger.kernel.org
Subject: [PATCH v1 0/9] clk: rockchip: Drop CLK_NR_CLKS CLKPMU_NR_CLKS usage
Date: Mon, 26 Aug 2024 18:36:40 +0200 [thread overview]
Message-ID: <416cdaf2-fef2-471d-a03a-837775d6e7dc@gmail.com> (raw)
In order to get rid of CLK_NR_CLKS and CLKPMU_NR_CLKS
and be able to drop it from the bindings, use
rockchip_clk_find_max_clk_id helper to find the
highest clock id.
Johan Jonker (9):
clk: rockchip: px30: Drop CLK_NR_CLKS CLKPMU_NR_CLKS usage
clk: rockchip: rk3036: Drop CLK_NR_CLKS usage
clk: rockchip: rk3228: Drop CLK_NR_CLKS usage
clk: rockchip: rk3288: Drop CLK_NR_CLKS usage
clk: rockchip: rk3308: Drop CLK_NR_CLKS usage
clk: rockchip: rk3328: Drop CLK_NR_CLKS usage
clk: rockchip: rk3368: Drop CLK_NR_CLKS usage
clk: rockchip: rk3399: Drop CLK_NR_CLKS CLKPMU_NR_CLKS usage
dt-bindings: clock: rockchip: remove CLK_NR_CLKS and CLKPMU_NR_CLKS
drivers/clk/rockchip/clk-px30.c | 10 ++++++++--
drivers/clk/rockchip/clk-rk3036.c | 5 ++++-
drivers/clk/rockchip/clk-rk3228.c | 5 ++++-
drivers/clk/rockchip/clk-rk3288.c | 5 ++++-
drivers/clk/rockchip/clk-rk3308.c | 5 ++++-
drivers/clk/rockchip/clk-rk3328.c | 5 ++++-
drivers/clk/rockchip/clk-rk3368.c | 5 ++++-
drivers/clk/rockchip/clk-rk3399.c | 10 ++++++++--
include/dt-bindings/clock/px30-cru.h | 4 ----
include/dt-bindings/clock/rk3036-cru.h | 2 --
include/dt-bindings/clock/rk3228-cru.h | 2 --
include/dt-bindings/clock/rk3288-cru.h | 2 --
include/dt-bindings/clock/rk3308-cru.h | 2 --
include/dt-bindings/clock/rk3328-cru.h | 2 --
include/dt-bindings/clock/rk3368-cru.h | 2 --
include/dt-bindings/clock/rk3399-cru.h | 4 ----
16 files changed, 40 insertions(+), 30 deletions(-)
--
2.39.2
next reply other threads:[~2024-08-26 16:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-26 16:36 Johan Jonker [this message]
2024-08-26 16:38 ` [PATCH v1 1/9] clk: rockchip: px30: " Johan Jonker
2024-08-26 16:38 ` [PATCH v1 2/9] clk: rockchip: rk3036: Drop CLK_NR_CLKS usage Johan Jonker
2024-08-26 16:38 ` [PATCH v1 3/9] clk: rockchip: rk3228: " Johan Jonker
2024-08-26 16:38 ` [PATCH v1 4/9] clk: rockchip: rk3288: " Johan Jonker
2024-08-26 16:39 ` [PATCH v1 5/9] clk: rockchip: rk3308: " Johan Jonker
2024-08-26 16:39 ` [PATCH v1 6/9] clk: rockchip: rk3328: " Johan Jonker
2024-08-26 16:39 ` [PATCH v1 7/9] clk: rockchip: rk3368: " Johan Jonker
2024-08-26 16:39 ` [PATCH v1 8/9] clk: rockchip: rk3399: Drop CLK_NR_CLKS CLKPMU_NR_CLKS usage Johan Jonker
2024-08-26 16:39 ` [PATCH v1 9/9] dt-bindings: clock: rockchip: remove CLK_NR_CLKS and CLKPMU_NR_CLKS Johan Jonker
2024-08-26 17:11 ` Conor Dooley
2024-08-28 20:53 ` [PATCH v1 0/9] clk: rockchip: Drop CLK_NR_CLKS CLKPMU_NR_CLKS usage 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=416cdaf2-fef2-471d-a03a-837775d6e7dc@gmail.com \
--to=jbx6244@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
all inboxes | Powered by JetHome®