Intel-XE Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: "Michał Grzelak" <michal.grzelak@intel.com>,
	intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Michał Grzelak" <michal.grzelak@intel.com>
Subject: Re: [PATCH] drm/i915: rename vlv_get_cck_clock() to vlv_clock_get_cck()
Date: Mon, 22 Sep 2025 12:47:42 +0300	[thread overview]
Message-ID: <c30c4bac7fa5b3f9126a90d887c0563149673703@intel.com> (raw)
In-Reply-To: <20250919215413.1006296-1-michal.grzelak@intel.com>

On Fri, 19 Sep 2025, Michał Grzelak <michal.grzelak@intel.com> wrote:
> Keep the convention of naming vlv_clock* instead of vlv_*_clock.
>
> Signed-off-by: Michał Grzelak <michal.grzelak@intel.com>

Thanks for the patch, pushed to drm-intel-next.

BR,
Jani.

> ---
>  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 42c2837b32c1..1abdae453514 100644
> --- a/drivers/gpu/drm/i915/display/vlv_clock.c
> +++ b/drivers/gpu/drm/i915/display/vlv_clock.c
> @@ -36,7 +36,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;
> @@ -58,7 +58,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));
>  }
>  
> @@ -67,7 +67,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);
>  	}
> @@ -77,12 +77,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));
>  }

-- 
Jani Nikula, Intel

      parent reply	other threads:[~2025-09-22  9:47 UTC|newest]

Thread overview: 6+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2025-09-19 21:54 [PATCH] drm/i915: rename vlv_get_cck_clock() to vlv_clock_get_cck() Michał Grzelak
2025-09-19 21:59 ` ✗ CI.checkpatch: warning for " Patchwork
2025-09-19 22:01 ` ✓ CI.KUnit: success " Patchwork
2025-09-19 22:50 ` ✓ Xe.CI.BAT: " Patchwork
2025-09-20  6:13 ` ✗ Xe.CI.Full: failure " Patchwork
2025-09-22  9:47 ` Jani Nikula [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=c30c4bac7fa5b3f9126a90d887c0563149673703@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=michal.grzelak@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