From: "Michał Grzelak" <michal.grzelak@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
ville.syrjala@linux.intel.com, michal.grzelak@intel.com
Subject: Re: [PATCH v2 00/15] drm/i915: vlv clock cleanups
Date: Thu, 18 Sep 2025 14:01:09 +0200 (CEST) [thread overview]
Message-ID: <dc4baf0c-420b-3486-98bd-24c4c53b5b0b@intel.com> (raw)
In-Reply-To: <cover.1757688216.git.jani.nikula@intel.com>
[-- Attachment #1: Type: text/plain, Size: 1861 bytes --]
Hi Jani,
On Fri, 12 Sep 2025, Jani Nikula wrote:
> This is v2 of [1]. There were issues with sideband get/put, discovered
> in CI, so I ended up doing what Ville suggested in [2], and handling
> sideband get/put inside the functions. This is done in new patches 1-2,
> which obviously caused some rebase churn in the rest. I also removed
> vlv_get_cck_clock_hpll() completely, this is new patch 11.
>
> I added r-b/ack from the previous version in some patches, dropped them
> from others, depending on how much changes there were. Sorry about the
> trouble, please look into this again.
>
> BR,
> Jani.
>
> [1] https://lore.kernel.org/r/cover.1755607980.git.jani.nikula@intel.com
> [2] https://lore.kernel.org/r/aMAqlVAw2NqlwQ5_@intel.com
>
> Jani Nikula (15):
> drm/i915: do cck get/put inside vlv_get_hpll_vco()
> drm/i915: do cck get/put inside vlv_get_cck_clock()
> drm/i915: add vlv_clock_get_gpll()
> drm/i915: add vlv_clock_get_czclk()
> drm/i915: add vlv_clock_get_hrawclk()
> drm/i915: make vlv_get_cck_clock_hpll() static
> drm/i915: add vlv_clock_get_cdclk()
> drm/i915: make vlv_get_cck_clock() static
> drm/i915: rename vlv_get_hpll_vco() to vlv_clock_get_hpll_vco()
> drm/i915: cache the results in vlv_clock_get_hpll_vco() and use it
> more
> drm/i915: remove vlv_get_cck_clock_hpll()
> drm/i915: remove intel_update_czclk() as unnecessary
> drm/i915: log HPLL frequency similar to CZCLK
> drm/i915: move hpll and czclk caching under display
> drm/i915: split out vlv_clock.[ch]
Although I have just issued my r-b on the rest of the series, I would
have one question. Can't we add on top of the series a separate commit
with rename of vlv_get_cck_clock() into vlv_clock_get_cck()? It would
be more consistent with the rest of the function names in vlv_clock.c.
Patch with what I am meaning is in the attachment.
BR,
Michał
[-- Warning: decoded text below may be mangled, UTF-8 assumed --]
[-- Attachment #2: rfc.patch --]
[-- Type: text/x-diff; name=0001-drm-i915-rename-vlv_get_cck_clock-to-vlv_clock_get_c.patch, Size: 2657 bytes --]
From 084926eea9cc5347fef6ea3d1f9f0c42e510f5fe Mon Sep 17 00:00:00 2001
From: =?UTF-8?q?Micha=C5=82=20Grzelak?= <michal.grzelak@intel.com>
Date: Thu, 18 Sep 2025 13:43:16 +0200
Subject: [PATCH] drm/i915: rename vlv_get_cck_clock() to vlv_clock_get_cck()
MIME-Version: 1.0
Content-Type: text/plain; charset=UTF-8
Content-Transfer-Encoding: 8bit
Organization: Intel Technology Poland sp. z o.o. - ul. Slowackiego 173, 80-298 Gdansk - KRS 101882 - NIP 957-07-52-316
Keep the convention of naming vlv_clock* instead of vlv_*_clock.
Signed-off-by: Michał Grzelak <michal.grzelak@intel.com>
---
drivers/gpu/drm/i915/display/vlv_clock.c | 10 +++++-----
1 file changed, 5 insertions(+), 5 deletions(-)
diff --git a/drivers/gpu/drm/i915/display/vlv_clock.c b/drivers/gpu/drm/i915/display/vlv_clock.c
index 2c55083d8fdb..e4499cbf4420 100644
--- a/drivers/gpu/drm/i915/display/vlv_clock.c
+++ b/drivers/gpu/drm/i915/display/vlv_clock.c
@@ -29,7 +29,7 @@ int vlv_clock_get_hpll_vco(struct drm_device *drm)
return display->vlv_clock.hpll_freq;
}
-static int vlv_get_cck_clock(struct drm_device *drm,
+static int vlv_clock_get_cck(struct drm_device *drm,
const char *name, u32 reg, int ref_freq)
{
u32 val;
@@ -51,7 +51,7 @@ static int vlv_get_cck_clock(struct drm_device *drm,
int vlv_clock_get_hrawclk(struct drm_device *drm)
{
/* RAWCLK_FREQ_VLV register updated from power well code */
- return vlv_get_cck_clock(drm, "hrawclk", CCK_DISPLAY_REF_CLOCK_CONTROL,
+ return vlv_clock_get_cck(drm, "hrawclk", CCK_DISPLAY_REF_CLOCK_CONTROL,
vlv_clock_get_hpll_vco(drm));
}
@@ -60,7 +60,7 @@ int vlv_clock_get_czclk(struct drm_device *drm)
struct intel_display *display = to_intel_display(drm);
if (!display->vlv_clock.czclk_freq) {
- display->vlv_clock.czclk_freq = vlv_get_cck_clock(drm, "czclk", CCK_CZ_CLOCK_CONTROL,
+ display->vlv_clock.czclk_freq = vlv_clock_get_cck(drm, "czclk", CCK_CZ_CLOCK_CONTROL,
vlv_clock_get_hpll_vco(drm));
drm_dbg_kms(drm, "CZ clock rate: %d kHz\n", display->vlv_clock.czclk_freq);
}
@@ -70,12 +70,12 @@ int vlv_clock_get_czclk(struct drm_device *drm)
int vlv_clock_get_cdclk(struct drm_device *drm)
{
- return vlv_get_cck_clock(drm, "cdclk", CCK_DISPLAY_CLOCK_CONTROL,
+ return vlv_clock_get_cck(drm, "cdclk", CCK_DISPLAY_CLOCK_CONTROL,
vlv_clock_get_hpll_vco(drm));
}
int vlv_clock_get_gpll(struct drm_device *drm)
{
- return vlv_get_cck_clock(drm, "GPLL ref", CCK_GPLL_CLOCK_CONTROL,
+ return vlv_clock_get_cck(drm, "GPLL ref", CCK_GPLL_CLOCK_CONTROL,
vlv_clock_get_czclk(drm));
}
--
2.45.2
next prev parent reply other threads:[~2025-09-18 12:01 UTC|newest]
Thread overview: 33+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-09-12 14:48 [PATCH v2 00/15] drm/i915: vlv clock cleanups Jani Nikula
2025-09-12 14:48 ` [PATCH v2 01/15] drm/i915: do cck get/put inside vlv_get_hpll_vco() Jani Nikula
2025-09-18 10:54 ` Michał Grzelak
2025-09-12 14:48 ` [PATCH v2 02/15] drm/i915: do cck get/put inside vlv_get_cck_clock() Jani Nikula
2025-09-18 10:59 ` Michał Grzelak
2025-09-12 14:48 ` [PATCH v2 03/15] drm/i915: add vlv_clock_get_gpll() Jani Nikula
2025-09-12 14:48 ` [PATCH v2 04/15] drm/i915: add vlv_clock_get_czclk() Jani Nikula
2025-09-12 14:48 ` [PATCH v2 05/15] drm/i915: add vlv_clock_get_hrawclk() Jani Nikula
2025-09-12 14:48 ` [PATCH v2 06/15] drm/i915: make vlv_get_cck_clock_hpll() static Jani Nikula
2025-09-12 14:48 ` [PATCH v2 07/15] drm/i915: add vlv_clock_get_cdclk() Jani Nikula
2025-09-12 14:48 ` [PATCH v2 08/15] drm/i915: make vlv_get_cck_clock() static Jani Nikula
2025-09-12 14:48 ` [PATCH v2 09/15] drm/i915: rename vlv_get_hpll_vco() to vlv_clock_get_hpll_vco() Jani Nikula
2025-09-12 14:48 ` [PATCH v2 10/15] drm/i915: cache the results in vlv_clock_get_hpll_vco() and use it more Jani Nikula
2025-09-16 19:51 ` Ville Syrjälä
2025-09-17 13:57 ` Jani Nikula
2025-09-18 11:17 ` Michał Grzelak
2025-09-12 14:48 ` [PATCH v2 11/15] drm/i915: remove vlv_get_cck_clock_hpll() Jani Nikula
2025-09-18 11:24 ` Michał Grzelak
2025-09-12 14:48 ` [PATCH v2 12/15] drm/i915: remove intel_update_czclk() as unnecessary Jani Nikula
2025-09-18 11:26 ` Michał Grzelak
2025-09-12 14:48 ` [PATCH v2 13/15] drm/i915: log HPLL frequency similar to CZCLK Jani Nikula
2025-09-12 14:48 ` [PATCH v2 14/15] drm/i915: move hpll and czclk caching under display Jani Nikula
2025-09-18 11:28 ` Michał Grzelak
2025-09-12 14:48 ` [PATCH v2 15/15] drm/i915: split out vlv_clock.[ch] Jani Nikula
2025-09-18 11:32 ` Michał Grzelak
2025-09-12 14:56 ` ✗ CI.checkpatch: warning for drm/i915: vlv clock cleanups (rev3) Patchwork
2025-09-12 14:57 ` ✓ CI.KUnit: success " Patchwork
2025-09-12 15:12 ` ✗ CI.checksparse: warning " Patchwork
2025-09-12 15:35 ` ✓ Xe.CI.BAT: success " Patchwork
2025-09-12 17:25 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-18 12:01 ` Michał Grzelak [this message]
2025-09-18 12:28 ` [PATCH v2 00/15] drm/i915: vlv clock cleanups Jani Nikula
2025-09-19 22:00 ` Michał Grzelak
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=dc4baf0c-420b-3486-98bd-24c4c53b5b0b@intel.com \
--to=michal.grzelak@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@intel.com \
--cc=ville.syrjala@linux.intel.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