public inbox for intel-gfx@lists.freedesktop.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: [PATCH 5/5] drm/i915: Update TRANS_MSA_MISC for fastsets
Date: Tue, 26 Mar 2019 12:43:48 +0200	[thread overview]
Message-ID: <87ef6t5317.fsf@intel.com> (raw)
In-Reply-To: <20190308192409.5804-5-ville.syrjala@linux.intel.com>

On Fri, 08 Mar 2019, Ville Syrjala <ville.syrjala@linux.intel.com> wrote:
> From: Ville Syrjälä <ville.syrjala@linux.intel.com>
>
> Update the DP MSA MISC bits for fastsets. This is needed
> when we change between limited and full range RGB output.
>
> On HSW+ changing limited_range does not currently result in a
> full modeset since we have don't have the readout code for it
> (for DP we could, and probably should, readout from TRANS_MSA_MISC
> itself, for HDMI we would have to rely on the infoframe). So
> the PIPE_CONF_CHECK() is only performed for pre-HSW platforms.
> That means any change in the value will result in a fastset
> instead. Fortunately there is no prohibition to changing
> TRANS_MSA_MISC dynamically, so it looks like we can legally do
> fastsets for this.
>
> Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>

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

> ---
>  drivers/gpu/drm/i915/intel_ddi.c | 2 ++
>  1 file changed, 2 insertions(+)
>
> diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> index 7e3b4e8fdf3a..3d9ad4526cf9 100644
> --- a/drivers/gpu/drm/i915/intel_ddi.c
> +++ b/drivers/gpu/drm/i915/intel_ddi.c
> @@ -3556,6 +3556,8 @@ static void intel_ddi_update_pipe_dp(struct intel_encoder *encoder,
>  {
>  	struct intel_dp *intel_dp = enc_to_intel_dp(&encoder->base);
>  
> +	intel_ddi_set_pipe_settings(crtc_state);
> +
>  	intel_psr_update(intel_dp, crtc_state);
>  	intel_edp_drrs_enable(intel_dp, crtc_state);

-- 
Jani Nikula, Intel Open Source Graphics Center
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

  reply	other threads:[~2019-03-26 10:41 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2019-03-08 19:24 [PATCH 1/5] drm/i915: Add broadcast RGB property for DP MST Ville Syrjala
2019-03-08 19:24 ` [PATCH 2/5] drm/i915: Expose the force_audio property with " Ville Syrjala
2019-03-26 10:41   ` Jani Nikula
2019-03-08 19:24 ` [PATCH 3/5] drm/i915: Remove the 8bpc shackles from " Ville Syrjala
2019-03-26 10:43   ` Jani Nikula
2019-03-26 13:16     ` Ville Syrjälä
2019-03-08 19:24 ` [PATCH 4/5] drm/i915: Add max_bpc property for " Ville Syrjala
2019-03-26 10:43   ` Jani Nikula
2019-03-08 19:24 ` [PATCH 5/5] drm/i915: Update TRANS_MSA_MISC for fastsets Ville Syrjala
2019-03-26 10:43   ` Jani Nikula [this message]
2019-03-08 20:16 ` ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/5] drm/i915: Add broadcast RGB property for DP MST Patchwork
2019-03-08 20:45 ` ✓ Fi.CI.BAT: success " Patchwork
2019-03-09  3:49 ` ✓ Fi.CI.IGT: " Patchwork
2019-03-14 13:07 ` [PATCH 1/5] " Ville Syrjälä
2019-03-26 10:41 ` Jani Nikula
2019-03-26 13:12   ` Ville Syrjälä

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=87ef6t5317.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