From: Brian Masney <bmasney@redhat.com>
To: sboyd@kernel.org
Cc: mturquette@baylibre.com, mripard@kernel.org,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org
Subject: [PATCH 0/2] clk: preserve original rate when a sibling clk changes it's rate
Date: Tue, 20 May 2025 15:28:44 -0400 [thread overview]
Message-ID: <20250520192846.9614-1-bmasney@redhat.com> (raw)
Here's a patch that helps to preserve the original clk rate on sibling
clks when the parent has it's rate changed. More details are on the
patch.
This series needs to be applied on top of my clk kunit tests that
document some issues that need to be fixed in the clk core:
https://lore.kernel.org/lkml/20250407131258.70638-1-bmasney@redhat.com/
This series fixes an issue in the clk core so that two of my kunit
tests can be enabled.
I will be at Embedded Linux Conference / OSS Summit in Denver, CO from
June 23-25th 2025 in case anyone would like to discuss some of these
issues and changes to the clk core in person.
Brian Masney (2):
clk: preserve original rate when a sibling clk changes it's rate
clk: test: remove kunit_skip() for divider tests that have been fixed
drivers/clk/clk.c | 28 ++++++++++++++++++++++++++--
drivers/clk/clk_test.c | 4 ----
2 files changed, 26 insertions(+), 6 deletions(-)
--
2.49.0
next reply other threads:[~2025-05-20 19:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-20 19:28 Brian Masney [this message]
2025-05-20 19:28 ` [PATCH 1/2] clk: preserve original rate when a sibling clk changes it's rate Brian Masney
2025-05-27 12:36 ` Maxime Ripard
2025-05-27 19:07 ` Brian Masney
2025-05-20 19:28 ` [PATCH 2/2] clk: test: remove kunit_skip() for divider tests that have been fixed Brian Masney
2025-05-28 23:23 ` [PATCH 0/2] clk: preserve original rate when a sibling clk changes it's rate Brian Masney
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=20250520192846.9614-1-bmasney@redhat.com \
--to=bmasney@redhat.com \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mripard@kernel.org \
--cc=mturquette@baylibre.com \
--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