From: Peng Fan <peng.fan@oss.nxp.com>
To: Brian Masney <bmasney@redhat.com>
Cc: Michael Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>,
linux-clk@vger.kernel.org, linux-kernel@vger.kernel.org,
Abel Vesa <abelvesa@kernel.org>, Frank Li <Frank.Li@nxp.com>,
Sascha Hauer <s.hauer@pengutronix.de>,
Peng Fan <peng.fan@nxp.com>,
Pengutronix Kernel Team <kernel@pengutronix.de>,
Fabio Estevam <festevam@gmail.com>,
imx@lists.linux.dev, linux-arm-kernel@lists.infradead.org
Subject: Re: [PATCH 07/13] clk: imx: scu: drop determine_rate op and use CLK_ROUNDING_FW_MANAGED flag
Date: Fri, 27 Feb 2026 10:04:22 +0800 [thread overview]
Message-ID: <aaD7pts7UrWqj3Jr@shlinux89> (raw)
In-Reply-To: <20260226-clk-det-rate-fw-managed-v1-7-4421dd2f6dc6@redhat.com>
On Thu, Feb 26, 2026 at 01:16:51PM -0500, Brian Masney wrote:
>This clk driver has a noop determine_rate clk op. Drop this empty
>function, and enable the CLK_ROUNDING_FW_MANAGED flag.
>
>Signed-off-by: Brian Masney <bmasney@redhat.com>
>
Reviewed-by: Peng Fan <peng.fan@nxp.com>
next prev parent reply other threads:[~2026-02-27 2:02 UTC|newest]
Thread overview: 38+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-02-26 18:16 [PATCH 00/13] clk: add new flag CLK_ROUNDING_FW_MANAGED Brian Masney
2026-02-26 18:16 ` [PATCH 01/13] " Brian Masney
2026-02-27 8:16 ` Geert Uytterhoeven
2026-02-27 8:57 ` Biju Das
2026-02-27 12:00 ` Biju Das
2026-02-27 14:44 ` Brian Masney
2026-02-27 16:38 ` Brian Masney
2026-03-02 11:27 ` Sudeep Holla
2026-02-26 18:16 ` [PATCH 02/13] clk: test: add test suite for CLK_ROUNDING_FW_MANAGED flag Brian Masney
2026-02-26 18:16 ` [PATCH 03/13] clk: rp1: drop determine_rate op and use " Brian Masney
2026-03-07 0:06 ` Andrea della Porta
2026-02-26 18:16 ` [PATCH 04/13] clk: scpi: " Brian Masney
2026-03-02 11:26 ` Sudeep Holla
2026-02-26 18:16 ` [PATCH 05/13] clk: hisilicon: hi3660-stub: " Brian Masney
2026-02-26 18:16 ` [PATCH 06/13] clk: imx: scu: drop redundant init.ops variable assignment Brian Masney
2026-02-27 2:02 ` Peng Fan
2026-02-26 18:16 ` [PATCH 07/13] clk: imx: scu: drop determine_rate op and use CLK_ROUNDING_FW_MANAGED flag Brian Masney
2026-02-27 2:04 ` Peng Fan [this message]
2026-02-26 18:16 ` [PATCH 08/13] clk: qcom: rpm: " Brian Masney
2026-02-27 0:07 ` Dmitry Baryshkov
2026-02-26 18:16 ` [PATCH 09/13] clk: qcom: rpmh: " Brian Masney
2026-02-27 0:12 ` Dmitry Baryshkov
2026-02-26 18:16 ` [PATCH 10/13] clk: qcom: smd-rpm: " Brian Masney
2026-02-27 0:13 ` Dmitry Baryshkov
2026-02-26 18:16 ` [PATCH 11/13] clk: renesas: rzg2l-cpg: " Brian Masney
2026-02-27 8:20 ` Geert Uytterhoeven
2026-02-27 14:46 ` Brian Masney
2026-02-27 15:01 ` Brian Masney
2026-02-27 15:09 ` Geert Uytterhoeven
2026-02-27 15:23 ` Biju Das
2026-02-27 15:48 ` Brian Masney
2026-02-27 15:57 ` Biju Das
2026-02-27 16:01 ` Brian Masney
2026-02-27 16:01 ` Geert Uytterhoeven
2026-02-27 16:04 ` Biju Das
2026-02-26 18:16 ` [PATCH 12/13] clk: samsung: acpm: " Brian Masney
2026-02-28 13:31 ` Krzysztof Kozlowski
2026-02-26 18:16 ` [PATCH 13/13] clk: sprd: " 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=aaD7pts7UrWqj3Jr@shlinux89 \
--to=peng.fan@oss.nxp.com \
--cc=Frank.Li@nxp.com \
--cc=abelvesa@kernel.org \
--cc=bmasney@redhat.com \
--cc=festevam@gmail.com \
--cc=imx@lists.linux.dev \
--cc=kernel@pengutronix.de \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-clk@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=peng.fan@nxp.com \
--cc=s.hauer@pengutronix.de \
--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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.