[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-Id: <20250528-clk-wip-v2-v2-3-0d2c2f220442@redhat.com>
Date: Wed, 28 May 2025 19:16:49 -0400
From: Brian Masney <bmasney@...hat.com>
To: Stephen Boyd <sboyd@...nel.org>, Maxime Ripard <mripard@...nel.org>
Cc: linux-clk@...r.kernel.org, linux-kernel@...r.kernel.org,
Arnd Bergmann <arnd@...db.de>, Thomas Gleixner <tglx@...utronix.de>,
Michael Turquette <mturquette@...libre.com>,
Alberto Ruiz <aruiz@...hat.com>, Brian Masney <bmasney@...hat.com>
Subject: [PATCH v2 03/10] clk: test: introduce a few specific rate
constants for mock testing
Some of the mock tests care about the relationship between two
different rates, and the specific numbers are important, such as for
mocking a divider.
Signed-off-by: Brian Masney <bmasney@...hat.com>
---
drivers/clk/clk_test.c | 4 ++++
1 file changed, 4 insertions(+)
diff --git a/drivers/clk/clk_test.c b/drivers/clk/clk_test.c
index f08feeaa3750bc86859294650de298762dea690a..1b34d54ec9c610ffa3e91b06f5a5180e0395e26f 100644
--- a/drivers/clk/clk_test.c
+++ b/drivers/clk/clk_test.c
@@ -24,6 +24,10 @@ static const struct clk_ops empty_clk_ops = { };
#define DUMMY_CLOCK_INIT_RATE (42 * 1000 * 1000)
#define DUMMY_CLOCK_RATE_1 (142 * 1000 * 1000)
#define DUMMY_CLOCK_RATE_2 (242 * 1000 * 1000)
+#define DUMMY_CLOCK_RATE_6_MHZ (6 * 1000 * 1000)
+#define DUMMY_CLOCK_RATE_16_MHZ (16 * 1000 * 1000)
+#define DUMMY_CLOCK_RATE_24_MHZ (24 * 1000 * 1000)
+#define DUMMY_CLOCK_RATE_48_MHZ (48 * 1000 * 1000)
struct clk_dummy_context {
struct clk_hw hw;
--
2.49.0
Powered by blists - more mailing lists