From: Stephen Boyd <sboyd@kernel.org>
To: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: linux-kernel@vger.kernel.org, linux-clk@vger.kernel.org,
patches@lists.linux.dev, Guenter Roeck <linux@roeck-us.net>,
Maxime Ripard <mripard@kernel.org>
Subject: [PATCH 0/2] clk: Fix lockdep warnings in clk_test
Date: Tue, 12 Sep 2023 10:55:29 -0700 [thread overview]
Message-ID: <20230912175534.2427862-1-sboyd@kernel.org> (raw)
This is a replacement for the series from Maxime[1]. I didn't want to
introduce more wrappers, so this series takes the approach of driving
the test from a clk_op instead. The second patch extends the test to
look at more determine_rate variants. We can probably extend the test
further to set or not set the CLK_SET_RATE_PARENT flag as well but I
didn't do that.
Stephen Boyd (2):
clk: Drive clk_leaf_mux_set_rate_parent test from clk_ops
clk: Parameterize clk_leaf_mux_set_rate_parent
drivers/clk/clk_test.c | 130 +++++++++++++++++++++++++++++++++++------
1 file changed, 113 insertions(+), 17 deletions(-)
Cc: Guenter Roeck <linux@roeck-us.net>
Cc: Maxime Ripard <mripard@kernel.org>
[1] https://lore.kernel.org/r/20230721-clk-fix-kunit-lockdep-v1-0-32cdba4c8fc1@kernel.org
base-commit: 0bb80ecc33a8fb5a682236443c1e740d5c917d1d
--
https://git.kernel.org/pub/scm/linux/kernel/git/clk/linux.git/
https://git.kernel.org/pub/scm/linux/kernel/git/sboyd/spmi.git
next reply other threads:[~2023-09-12 17:55 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2023-09-12 17:55 Stephen Boyd [this message]
2023-09-12 17:55 ` [PATCH 1/2] clk: Drive clk_leaf_mux_set_rate_parent test from clk_ops Stephen Boyd
2023-10-10 3:23 ` Stephen Boyd
2023-09-12 17:55 ` [PATCH 2/2] clk: Parameterize clk_leaf_mux_set_rate_parent Stephen Boyd
2023-10-10 3:23 ` Stephen Boyd
2023-09-19 11:01 ` [PATCH 0/2] clk: Fix lockdep warnings in clk_test Maxime Ripard
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=20230912175534.2427862-1-sboyd@kernel.org \
--to=sboyd@kernel.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux@roeck-us.net \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--cc=patches@lists.linux.dev \
/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).