From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v2 2/2] drm/i915/cdclk: move struct intel_cdclk_funcs to intel_cdclk.c
Date: Mon, 13 Dec 2021 14:43:14 +0200 [thread overview]
Message-ID: <Ybc/4ktIaLxKl6lJ@intel.com> (raw)
In-Reply-To: <20211213114106.296017-2-jani.nikula@intel.com>
On Mon, Dec 13, 2021 at 01:41:06PM +0200, Jani Nikula wrote:
> The funcs struct can be opaque, make it internal to intel_cdclk.c.
>
> Suggested-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
> drivers/gpu/drm/i915/display/intel_cdclk.c | 11 +++++++++++
> drivers/gpu/drm/i915/i915_drv.h | 12 +-----------
> 2 files changed, 12 insertions(+), 11 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_cdclk.c b/drivers/gpu/drm/i915/display/intel_cdclk.c
> index c30cf8d2b835..249f81a80eb7 100644
> --- a/drivers/gpu/drm/i915/display/intel_cdclk.c
> +++ b/drivers/gpu/drm/i915/display/intel_cdclk.c
> @@ -63,6 +63,17 @@
> * dividers can be programmed correctly.
> */
>
> +struct intel_cdclk_funcs {
> + void (*get_cdclk)(struct drm_i915_private *i915,
> + struct intel_cdclk_config *cdclk_config);
> + void (*set_cdclk)(struct drm_i915_private *i915,
> + const struct intel_cdclk_config *cdclk_config,
> + enum pipe pipe);
> + int (*bw_calc_min_cdclk)(struct intel_atomic_state *state);
> + int (*modeset_calc_cdclk)(struct intel_cdclk_state *state);
> + u8 (*calc_voltage_level)(int cdclk);
> +};
> +
> void intel_cdclk_get_cdclk(struct drm_i915_private *dev_priv,
> struct intel_cdclk_config *cdclk_config)
> {
> diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
> index e2c0d69753b1..0112ae942664 100644
> --- a/drivers/gpu/drm/i915/i915_drv.h
> +++ b/drivers/gpu/drm/i915/i915_drv.h
> @@ -291,6 +291,7 @@ struct intel_connector;
> struct intel_encoder;
> struct intel_atomic_state;
> struct intel_cdclk_config;
> +struct intel_cdclk_funcs;
> struct intel_cdclk_state;
> struct intel_cdclk_vals;
> struct intel_initial_plane_config;
> @@ -339,17 +340,6 @@ struct intel_color_funcs {
> void (*read_luts)(struct intel_crtc_state *crtc_state);
> };
>
> -struct intel_cdclk_funcs {
> - void (*get_cdclk)(struct drm_i915_private *dev_priv,
> - struct intel_cdclk_config *cdclk_config);
> - void (*set_cdclk)(struct drm_i915_private *dev_priv,
> - const struct intel_cdclk_config *cdclk_config,
> - enum pipe pipe);
> - int (*bw_calc_min_cdclk)(struct intel_atomic_state *state);
> - int (*modeset_calc_cdclk)(struct intel_cdclk_state *state);
> - u8 (*calc_voltage_level)(int cdclk);
> -};
> -
> struct intel_hotplug_funcs {
> void (*hpd_irq_setup)(struct drm_i915_private *dev_priv);
> };
> --
> 2.30.2
--
Ville Syrjälä
Intel
next prev parent reply other threads:[~2021-12-13 12:43 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-12-13 11:41 [Intel-gfx] [PATCH v2 1/2] drm/i915/cdclk: turn around i915_drv.h and intel_cdclk.h dependency Jani Nikula
2021-12-13 11:41 ` [Intel-gfx] [PATCH v2 2/2] drm/i915/cdclk: move struct intel_cdclk_funcs to intel_cdclk.c Jani Nikula
2021-12-13 12:43 ` Ville Syrjälä [this message]
2021-12-14 19:55 ` Jani Nikula
2021-12-13 17:14 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/2] drm/i915/cdclk: turn around i915_drv.h and intel_cdclk.h dependency Patchwork
2021-12-13 17:49 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-12-14 0:21 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/2] drm/i915/cdclk: turn around i915_drv.h and intel_cdclk.h dependency (rev2) Patchwork
2021-12-14 0:56 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-12-14 12:25 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/2] drm/i915/cdclk: turn around i915_drv.h and intel_cdclk.h dependency (rev3) Patchwork
2021-12-14 12:53 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-12-14 16:32 ` [Intel-gfx] ✓ Fi.CI.IGT: " Patchwork
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=Ybc/4ktIaLxKl6lJ@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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