From: Maxime Ripard <maxime@cerno.tech>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org
Cc: Jerome Brunet <jbrunet@baylibre.com>,
Alexander Stein <alexander.stein@ew.tq-group.com>,
Naresh Kamboju <naresh.kamboju@linaro.org>,
Yassine Oudjana <y.oudjana@protonmail.com>,
Marek Szyprowski <m.szyprowski@samsung.com>,
Neil Armstrong <narmstrong@baylibre.com>,
Dmitry Baryshkov <dmitry.baryshkov@linaro.org>,
Tony Lindgren <tony@atomide.com>
Subject: Re: [PATCH v3 00/28] clk: More clock rate fixes and tests
Date: Fri, 3 Jun 2022 16:30:40 +0200 [thread overview]
Message-ID: <20220603143040.pjcelo6a5packoaj@penduick> (raw)
In-Reply-To: <20220511144830.wgs6zt27gzckbzng@houat>
Hi Stephen, Mike,
On Wed, May 11, 2022 at 04:48:30PM +0200, Maxime Ripard wrote:
> On Wed, May 11, 2022 at 04:42:21PM +0200, Maxime Ripard wrote:
> > Thanks to the feedback I got on the previous series, I found and fixed a
> > number of bugs in the clock framework and how it deals with rates,
> > especially when it comes to orphan clocks.
> >
> > In order to make sure this doesn't pop up again as a regression, I've
> > extended the number of tests.
> >
> > The first patch reintroduces the clk_set_rate_range call on clk_put, but
> > this time will only do so if there was a range set on that clock to
> > begin with. It should be less intrusive, and reduce the number of
> > potential side effects considerably.
> >
> > We then have a fix for the qcom rcg2 issue that has been reported
> > recently, and two patches to address a regression with the RaspberryPi4.
>
> Those four patches are fixing regressions in 5.18. Even though the later
> patches are also fixing some issues, the first four should have your
> priority over the rest.
Could we please move forward on this?
Maxime
prev parent reply other threads:[~2022-06-03 14:30 UTC|newest]
Thread overview: 35+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-05-11 14:42 [PATCH v3 00/28] clk: More clock rate fixes and tests Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 01/28] clk: Drop the rate range on clk_put() Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 02/28] clk: Skip clamping when rounding if there's no boundaries Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 03/28] clk: Introduce clk_get_rate_range() Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 04/28] drm/vc4: hdmi: Rework hdmi_enable_4kp60 detection Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 05/28] clk: Mention that .recalc_rate can return 0 on error Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 06/28] clk: Clarify clk_get_rate() expectations Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 07/28] clk: tests: Add test suites description Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 08/28] clk: tests: Add reference to the orphan mux bug report Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 09/28] clk: tests: Add tests for uncached clock Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 10/28] clk: tests: Add tests for single parent mux Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 11/28] clk: tests: Add tests for mux with multiple parents Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 12/28] clk: tests: Add some tests for orphan " Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 13/28] clk: Take into account uncached clocks in clk_set_rate_range() Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 14/28] clk: Fix clk_get_parent() documentation Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 15/28] clk: Set req_rate on reparenting Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 16/28] clk: Change clk_core_init_rate_req prototype Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 17/28] clk: Move clk_core_init_rate_req() from clk_core_round_rate_nolock() to its caller Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 18/28] clk: Introduce clk_hw_init_rate_request() Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 19/28] clk: Add our request boundaries in clk_core_init_rate_req Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 20/28] clk: Switch from __clk_determine_rate to clk_core_round_rate_nolock Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 21/28] clk: Introduce clk_core_has_parent() Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 22/28] clk: Stop forwarding clk_rate_requests to the parent Maxime Ripard
2022-05-11 19:21 ` kernel test robot
2022-05-11 19:21 ` kernel test robot
2022-05-11 20:23 ` kernel test robot
2022-05-11 21:25 ` kernel test robot
2022-05-11 14:42 ` [PATCH v3 23/28] clk: Zero the clk_rate_request structure Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 24/28] clk: Test the clock pointer in clk_hw_get_name() Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 25/28] clk: Introduce the clk_hw_get_rate_range function Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 26/28] clk: qcom: clk-rcg2: Take clock boundaries into consideration for gfx3d Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 27/28] clk: tests: Add some tests for clk_get_rate_range() Maxime Ripard
2022-05-11 14:42 ` [PATCH v3 28/28] clk: tests: Add missing test case for ranges Maxime Ripard
2022-05-11 14:48 ` [PATCH v3 00/28] clk: More clock rate fixes and tests Maxime Ripard
2022-06-03 14:30 ` Maxime Ripard [this message]
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=20220603143040.pjcelo6a5packoaj@penduick \
--to=maxime@cerno.tech \
--cc=alexander.stein@ew.tq-group.com \
--cc=dmitry.baryshkov@linaro.org \
--cc=jbrunet@baylibre.com \
--cc=linux-clk@vger.kernel.org \
--cc=m.szyprowski@samsung.com \
--cc=mturquette@baylibre.com \
--cc=naresh.kamboju@linaro.org \
--cc=narmstrong@baylibre.com \
--cc=sboyd@kernel.org \
--cc=tony@atomide.com \
--cc=y.oudjana@protonmail.com \
/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