From: Ahmad Fatoum <a.fatoum@pengutronix.de>
To: barebox@lists.infradead.org
Subject: [PATCH 1/7] clk: add compatibility for prepare/unprepare/is_prepared
Date: Tue, 22 Apr 2025 09:56:31 +0200 [thread overview]
Message-ID: <20250422075637.220688-1-a.fatoum@pengutronix.de> (raw)
From: Ahmad Fatoum <a.fatoum@barebox.org>
Instead of having to mechanically rename prepare/unprepare operations to
enable/disable, let's just alias them in a union.
This risks code porters missing to merge both operations when they
exist, but this can be fixed via enforcing -Woverride-init as default
warning, which will be added separately.
Signed-off-by: Ahmad Fatoum <a.fatoum@barebox.org>
---
include/linux/clk.h | 21 ++++++++++++++++++---
1 file changed, 18 insertions(+), 3 deletions(-)
diff --git a/include/linux/clk.h b/include/linux/clk.h
index b10af93af429..6bedc5204cca 100644
--- a/include/linux/clk.h
+++ b/include/linux/clk.h
@@ -269,12 +269,18 @@ static inline void clk_put(struct clk *clk)
* @enable: Prepare and enable the clock atomically. This must not return
* until the clock is generating a valid clock signal, usable by
* consumer devices.
+ * @prepare: Alias for @enable. If the Linux driver defines both, they
+ * must be merged when ported to barebox.
*
* @disable: Unprepare and disable the clock atomically.
+ * @unprepare: Alias for @disable. If the Linux driver defines both, they
+ * must be merged when ported to barebox.
*
* @is_enabled: Queries the hardware to determine if the clock is enabled.
* Optional, if this op is not set then the enable count will be
* used.
+ * @is_prepared Alias for @is_enabled. If the Linux driver defines both, they
+ * must be merged when ported to barebox.
*
* @recalc_rate Recalculate the rate of this clock, by querying hardware. The
* parent rate is an input parameter. If the driver cannot figure
@@ -319,9 +325,18 @@ static inline void clk_put(struct clk *clk)
*/
struct clk_ops {
int (*init)(struct clk_hw *hw);
- int (*enable)(struct clk_hw *hw);
- void (*disable)(struct clk_hw *hw);
- int (*is_enabled)(struct clk_hw *hw);
+ union {
+ int (*enable)(struct clk_hw *hw);
+ int (*prepare)(struct clk_hw *hw);
+ };
+ union {
+ void (*disable)(struct clk_hw *hw);
+ void (*unprepare)(struct clk_hw *hw);
+ };
+ union {
+ int (*is_enabled)(struct clk_hw *hw);
+ int (*is_prepared)(struct clk_hw *hw);
+ };
unsigned long (*recalc_rate)(struct clk_hw *hw,
unsigned long parent_rate);
long (*round_rate)(struct clk_hw *hw, unsigned long,
--
2.39.5
next reply other threads:[~2025-04-22 8:39 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-22 7:56 Ahmad Fatoum [this message]
2025-04-22 7:56 ` [PATCH 2/7] clk: mux: replace width member with mask as in Linux Ahmad Fatoum
2025-04-22 7:56 ` [PATCH 3/7] clk: mux: fix mask/width confusion in clk_hw_register_mux Ahmad Fatoum
2025-04-22 7:56 ` [PATCH 4/7] clk: gate: underscore-prefix barebox-specific parent member Ahmad Fatoum
2025-04-22 7:56 ` [PATCH 5/7] clk: gate: add bit_idx member as in Linux Ahmad Fatoum
2025-04-22 7:56 ` [PATCH 6/7] clk: composite: change mux/rate/gate members to clk_hw Ahmad Fatoum
2025-04-22 7:56 ` [PATCH 7/7] clk: move struct clk_composite definition to header Ahmad Fatoum
2025-04-22 9:18 ` [PATCH 1/7] clk: add compatibility for prepare/unprepare/is_prepared Sascha Hauer
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=20250422075637.220688-1-a.fatoum@pengutronix.de \
--to=a.fatoum@pengutronix.de \
--cc=barebox@lists.infradead.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