From: Imre Deak <imre.deak@intel.com>
To: Jani Nikula <jani.nikula@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: make __intel_display_power_is_enabled() static
Date: Wed, 14 Aug 2024 15:34:31 +0300 [thread overview]
Message-ID: <ZrykV8TC5w4pmyMR@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <20240813151216.2573845-1-jani.nikula@intel.com>
On Tue, Aug 13, 2024 at 06:12:16PM +0300, Jani Nikula wrote:
> The function isn't used outside of intel_display_power.c. Make it
> static.
>
> Signed-off-by: Jani Nikula <jani.nikula@intel.com>
Reviewed-by: Imre Deak <imre.deak@intel.com>
Same applies to intel_display_power_domain_str().
> ---
> .../gpu/drm/i915/display/intel_display_power.c | 16 ++--------------
> .../gpu/drm/i915/display/intel_display_power.h | 2 --
> 2 files changed, 2 insertions(+), 16 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_display_power.c b/drivers/gpu/drm/i915/display/intel_display_power.c
> index 0af1e34ef2a7..cf8b38f2ebf5 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_power.c
> +++ b/drivers/gpu/drm/i915/display/intel_display_power.c
> @@ -198,20 +198,8 @@ intel_display_power_domain_str(enum intel_display_power_domain domain)
> }
> }
>
> -/**
> - * __intel_display_power_is_enabled - unlocked check for a power domain
> - * @dev_priv: i915 device instance
> - * @domain: power domain to check
> - *
> - * This is the unlocked version of intel_display_power_is_enabled() and should
> - * only be used from error capture and recovery code where deadlocks are
> - * possible.
> - *
> - * Returns:
> - * True when the power domain is enabled, false otherwise.
> - */
> -bool __intel_display_power_is_enabled(struct drm_i915_private *dev_priv,
> - enum intel_display_power_domain domain)
> +static bool __intel_display_power_is_enabled(struct drm_i915_private *dev_priv,
> + enum intel_display_power_domain domain)
> {
> struct i915_power_well *power_well;
> bool is_enabled;
> diff --git a/drivers/gpu/drm/i915/display/intel_display_power.h b/drivers/gpu/drm/i915/display/intel_display_power.h
> index d6c2a5846bdc..0962f6aaeee6 100644
> --- a/drivers/gpu/drm/i915/display/intel_display_power.h
> +++ b/drivers/gpu/drm/i915/display/intel_display_power.h
> @@ -188,8 +188,6 @@ intel_display_power_domain_str(enum intel_display_power_domain domain);
>
> bool intel_display_power_is_enabled(struct drm_i915_private *dev_priv,
> enum intel_display_power_domain domain);
> -bool __intel_display_power_is_enabled(struct drm_i915_private *dev_priv,
> - enum intel_display_power_domain domain);
> intel_wakeref_t intel_display_power_get(struct drm_i915_private *dev_priv,
> enum intel_display_power_domain domain);
> intel_wakeref_t
> --
> 2.39.2
>
next prev parent reply other threads:[~2024-08-14 12:34 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-08-13 15:12 [PATCH] drm/i915: make __intel_display_power_is_enabled() static Jani Nikula
2024-08-13 16:35 ` ✗ Fi.CI.SPARSE: warning for " Patchwork
2024-08-13 16:42 ` ✓ Fi.CI.BAT: success " Patchwork
2024-08-14 0:38 ` ✗ Fi.CI.IGT: failure " Patchwork
2024-08-14 12:34 ` Imre Deak [this message]
2024-08-15 12:01 ` [PATCH] " Jani Nikula
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=ZrykV8TC5w4pmyMR@ideak-desk.fi.intel.com \
--to=imre.deak@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