Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Hans de Goede <hdegoede@redhat.com>
To: "Hans de Goede" <j.w.r.degoede@gmail.com>,
	"Jani Nikula" <jani.nikula@linux.intel.com>,
	"Joonas Lahtinen" <joonas.lahtinen@linux.intel.com>,
	"Rodrigo Vivi" <rodrigo.vivi@intel.com>,
	"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
	"Daniel Vetter" <daniel@ffwll.ch>
Cc: intel-gfx <intel-gfx@lists.freedesktop.org>,
	dri-devel@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: intel_pipe_config_compare: Don't compare DSI PLL regs when adjusting
Date: Thu, 29 Nov 2018 12:28:31 +0100	[thread overview]
Message-ID: <e3d14bae-46d6-368b-857f-9a40e465fafe@redhat.com> (raw)
In-Reply-To: <20181102114447.29501-1-hdegoede@redhat.com>

Hi all,

On 02-11-18 12:44, Hans de Goede wrote:
> The GOP sometimes initializes the DSI pclk at a (slightly) different freq
> then the pclk which we pick. intel_pipe_config_compare() allows for this
> by doing a fuzzy compare on the port_clock.
> 
> But the pclk difference not only results in the port_clock and
> base.adjusted_mode.crtc_clock clocks being a bit different, but also in
> us picking different dsi_pll register values matching the different pclk.
> 
> This commit makes us only do the dsi_pll register compare when the adjust
> parameter is false, so only from verify_crtc_state(), so that we correctly
> do a fast modeset at boot avoiding the screen going black for about 1 sec.
> 
> Signed-off-by: Hans de Goede <hdegoede@redhat.com>

Self-nack to this patch. This avoids the modeset on boot when
booting with fastboot=1 but then on the first commit afterwards
we get errors like these:

[    6.330864] [drm:pipe_config_err [i915]] *ERROR* mismatch in dsi_pll.ctrl (expected 0x80040100, found 0x80080100)
[    6.330967] [drm:pipe_config_err [i915]] *ERROR* mismatch in dsi_pll.div (expected 0x000001aa, found 0x0000011a)

Followed by a backtrace caused by the I915_STATE_WARN at the
end of verify_crtc_state triggering.

So I will brush of my previous patch to fix this, which reads the
pclk picked by the GOP back and uses overrides the VBT one with
that if it is close.

I believe I've a solution for not doing hw readback in intel_dsi_vbt.c,
which was the largest objection last time I posted that series.

Regards,

Hans


> ---
>   drivers/gpu/drm/i915/intel_display.c | 6 ++++--
>   1 file changed, 4 insertions(+), 2 deletions(-)
> 
> diff --git a/drivers/gpu/drm/i915/intel_display.c b/drivers/gpu/drm/i915/intel_display.c
> index b219d5858160..82fa85df0fba 100644
> --- a/drivers/gpu/drm/i915/intel_display.c
> +++ b/drivers/gpu/drm/i915/intel_display.c
> @@ -11759,8 +11759,10 @@ intel_pipe_config_compare(struct drm_i915_private *dev_priv,
>   	PIPE_CONF_CHECK_X(dpll_hw_state.mg_pll_bias);
>   	PIPE_CONF_CHECK_X(dpll_hw_state.mg_pll_tdc_coldst_bias);
>   
> -	PIPE_CONF_CHECK_X(dsi_pll.ctrl);
> -	PIPE_CONF_CHECK_X(dsi_pll.div);
> +	if (!adjust) {
> +		PIPE_CONF_CHECK_X(dsi_pll.ctrl);
> +		PIPE_CONF_CHECK_X(dsi_pll.div);
> +	}
>   
>   	if (IS_G4X(dev_priv) || INTEL_GEN(dev_priv) >= 5)
>   		PIPE_CONF_CHECK_I(pipe_bpp);
> 
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx

      parent reply	other threads:[~2018-11-29 11:28 UTC|newest]

Thread overview: 5+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2018-11-02 11:44 [PATCH] drm/i915: intel_pipe_config_compare: Don't compare DSI PLL regs when adjusting Hans de Goede
2018-11-02 12:00 ` ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2018-11-02 12:23 ` ✓ Fi.CI.BAT: success " Patchwork
2018-11-02 14:16 ` ✓ Fi.CI.IGT: " Patchwork
2018-11-29 11:28 ` Hans de Goede [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=e3d14bae-46d6-368b-857f-9a40e465fafe@redhat.com \
    --to=hdegoede@redhat.com \
    --cc=daniel@ffwll.ch \
    --cc=dri-devel@lists.freedesktop.org \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=j.w.r.degoede@gmail.com \
    --cc=jani.nikula@linux.intel.com \
    --cc=joonas.lahtinen@linux.intel.com \
    --cc=rodrigo.vivi@intel.com \
    --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