Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Jani Nikula <jani.nikula@linux.intel.com>
To: Ville Syrjala <ville.syrjala@linux.intel.com>,
	intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH v3 6/6] drm/i915: Setup final panel drrs_type already during init
Date: Tue, 04 Oct 2022 12:00:03 +0300	[thread overview]
Message-ID: <8735c4ufos.fsf@intel.com> (raw)
In-Reply-To: <20221003113249.16213-7-ville.syrjala@linux.intel.com>

On Mon, 03 Oct 2022, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Now that we track the VBT drrs type per-panel we can move the
> has_drrs_modes() check to the panel init rather than doing it
> for every intel_panel_drrs_type() call.

And we also get the correct DRRS type logging hint early on.

Reviewed-by: Jani Nikula <jani.nikula@intel.com>

>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> ---
>  drivers/gpu/drm/i915/display/intel_panel.c | 6 +++---
>  1 file changed, 3 insertions(+), 3 deletions(-)
>
> diff --git a/drivers/gpu/drm/i915/display/intel_panel.c b/drivers/gpu/drm/i915/display/intel_panel.c
> index d18c56cf957d..2b4b359b8342 100644
> --- a/drivers/gpu/drm/i915/display/intel_panel.c
> +++ b/drivers/gpu/drm/i915/display/intel_panel.c
> @@ -165,9 +165,6 @@ static bool has_drrs_modes(struct intel_connector *connector)
>  
>  enum drrs_type intel_panel_drrs_type(struct intel_connector *connector)
>  {
> -	if (!has_drrs_modes(connector))
> -		return DRRS_TYPE_NONE;
> -
>  	return connector->panel.vbt.drrs_type;
>  }
>  
> @@ -668,6 +665,9 @@ int intel_panel_init(struct intel_connector *connector)
>  
>  	intel_backlight_init_funcs(panel);
>  
> +	if (!has_drrs_modes(connector))
> +		connector->panel.vbt.drrs_type = DRRS_TYPE_NONE;
> +
>  	drm_dbg_kms(connector->base.dev,
>  		    "[CONNECTOR:%d:%s] DRRS type: %s\n",
>  		    connector->base.base.id, connector->base.name,

-- 
Jani Nikula, Intel Open Source Graphics Center

  reply	other threads:[~2022-10-04  9:00 UTC|newest]

Thread overview: 12+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-03 11:32 [Intel-gfx] [PATCH v3 0/6] drm/i915: Per-crtc/connector DRRS debugfs Ville Syrjala
2022-10-03 11:32 ` [Intel-gfx] [PATCH v3 1/6] drm/i915: Move DRRS debugfs next to the implementation Ville Syrjala
2022-10-03 11:32 ` [Intel-gfx] [PATCH v3 2/6] drm/i915: Make the DRRS debugfs contents more consistent Ville Syrjala
2022-10-03 11:32 ` [Intel-gfx] [PATCH v3 3/6] drm/i915: Make DRRS debugfs per-crtc/connector Ville Syrjala
2022-10-03 11:32 ` [Intel-gfx] [PATCH v3 4/6] drm/i915: Fix locking in DRRS debugfs Ville Syrjala
2022-10-03 11:32 ` [Intel-gfx] [PATCH v3 5/6] drm/i915: Tighten DRRS capability reporting Ville Syrjala
2022-10-04  8:59   ` Jani Nikula
2022-10-03 11:32 ` [Intel-gfx] [PATCH v3 6/6] drm/i915: Setup final panel drrs_type already during init Ville Syrjala
2022-10-04  9:00   ` Jani Nikula [this message]
2022-10-03 12:58 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Per-crtc/connector DRRS debugfs (rev3) Patchwork
2022-10-03 13:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-03 15:02 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " 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=8735c4ufos.fsf@intel.com \
    --to=jani.nikula@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --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