From: Maxime Ripard <maxime@cerno.tech>
To: Mike Turquette <mturquette@baylibre.com>,
Stephen Boyd <sboyd@kernel.org>
Cc: dri-devel@lists.freedesktop.org, linux-clk@vger.kernel.org,
Dave Stevenson <dave.stevenson@raspberrypi.com>,
Phil Elwell <phil@raspberrypi.com>,
Tim Gover <tim.gover@raspberrypi.com>,
Dom Cobley <dom@raspberrypi.com>,
Maxime Ripard <maxime@cerno.tech>
Subject: [PATCH v5 10/11] drm/vc4: Add logging and comments
Date: Tue, 22 Feb 2022 14:18:52 +0100 [thread overview]
Message-ID: <20220222131853.198625-11-maxime@cerno.tech> (raw)
In-Reply-To: <20220222131853.198625-1-maxime@cerno.tech>
The HVS core clock isn't really obvious, so let's add a bunch more
comments and some logging for easier debugging.
Signed-off-by: Maxime Ripard <maxime@cerno.tech>
---
drivers/gpu/drm/vc4/vc4_kms.c | 11 +++++++++++
1 file changed, 11 insertions(+)
diff --git a/drivers/gpu/drm/vc4/vc4_kms.c b/drivers/gpu/drm/vc4/vc4_kms.c
index 24de29bc1cda..6fe03fc17d73 100644
--- a/drivers/gpu/drm/vc4/vc4_kms.c
+++ b/drivers/gpu/drm/vc4/vc4_kms.c
@@ -389,8 +389,15 @@ static void vc4_atomic_commit_tail(struct drm_atomic_state *state)
500000000,
new_hvs_state->core_clock_rate);
+ drm_dbg(dev, "Raising the core clock at %lu Hz\n", core_rate);
+
+ /*
+ * Do a temporary request on the core clock during the
+ * modeset.
+ */
clk_set_min_rate(hvs->core_clk, core_rate);
}
+
drm_atomic_helper_commit_modeset_disables(dev, state);
vc4_ctm_commit(vc4, state);
@@ -416,6 +423,10 @@ static void vc4_atomic_commit_tail(struct drm_atomic_state *state)
drm_dbg(dev, "Running the core clock at %lu Hz\n",
new_hvs_state->core_clock_rate);
+ /*
+ * Request a clock rate based on the current HVS
+ * requirements.
+ */
clk_set_min_rate(hvs->core_clk, new_hvs_state->core_clock_rate);
}
}
--
2.35.1
next prev parent reply other threads:[~2022-02-22 13:19 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-02-22 13:18 [PATCH v5 00/11] clk: Improve clock range handling Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 01/11] clk: Introduce Kunit Tests for the framework Maxime Ripard
2022-02-23 2:25 ` kernel test robot
2022-02-22 13:18 ` [PATCH v5 02/11] clk: Enforce that disjoints limits are invalid Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 03/11] clk: Always clamp the rounded rate Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 04/11] clk: Use clamp instead of open-coding our own Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 05/11] clk: Always set the rate on clk_set_range_rate Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 06/11] clk: Add clk_drop_range Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 07/11] clk: bcm: rpi: Add variant structure Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 08/11] clk: bcm: rpi: Set a default minimum rate Maxime Ripard
2022-02-22 13:18 ` [PATCH v5 09/11] clk: bcm: rpi: Run some clocks at the minimum rate allowed Maxime Ripard
2022-02-22 13:18 ` Maxime Ripard [this message]
2022-02-22 13:18 ` [PATCH v5 11/11] drm/vc4: hdmi: Remove clock rate initialization 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=20220222131853.198625-11-maxime@cerno.tech \
--to=maxime@cerno.tech \
--cc=dave.stevenson@raspberrypi.com \
--cc=dom@raspberrypi.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=linux-clk@vger.kernel.org \
--cc=mturquette@baylibre.com \
--cc=phil@raspberrypi.com \
--cc=sboyd@kernel.org \
--cc=tim.gover@raspberrypi.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