From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Zhao, Xinda" <xinda.zhao@intel.com>
Cc: Zhao@freedesktop.org, intel-gfx@lists.freedesktop.org,
intel-gvt-dev@lists.freedesktop.org
Subject: Re: [PATCH] drm/i915: Fix DPLL warning when starting guest VM
Date: Mon, 30 Oct 2017 17:14:14 +0200 [thread overview]
Message-ID: <20171030151414.GP10981@intel.com> (raw)
In-Reply-To: <20171030134928.GO10981@intel.com>
On Mon, Oct 30, 2017 at 03:49:28PM +0200, Ville Syrjälä wrote:
> On Mon, Oct 30, 2017 at 04:17:06PM +0800, Zhao, Xinda wrote:
> > The warning is occurred in guest VM when trying to get clock in encoder
> > initialization.
What does guest VM mean here? gvt? If so, why do you claim to have
an enabled port without an enabled pipe?
> >
> > intel_modeset_init()
> > ->intel_modeset_setup_hw_state()
> > ->intel_ddi_get_config()
> > ->intel_ddi_clock_get()
> > ->skl_ddi_clock_get()
> > ->intel_get_shared_dpll_id()
> > ->WARN_ON(pll < dev_priv->shared_dplls||
> > pll > &dev_priv->shared_dplls[dev_priv->num_shared_dpll])
> >
> > In encoder initialization, shared DPLL is used for calculating clock for
> > DDI ports, but it is not set when crtc is not active.
> > In some cases, encoder is enabled while crtc is disabled, during encoder
> > initialization, the warning occurred.
> >
> > Signed-off-by: Zhao, Xinda <xinda.zhao@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_ddi.c | 10 ++++++++++
> > 1 file changed, 10 insertions(+)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_ddi.c b/drivers/gpu/drm/i915/intel_ddi.c
> > index 28c25cb..ef35c12 100644
> > --- a/drivers/gpu/drm/i915/intel_ddi.c
> > +++ b/drivers/gpu/drm/i915/intel_ddi.c
> > @@ -1489,6 +1489,16 @@ void intel_ddi_clock_get(struct intel_encoder *encoder,
> > struct intel_crtc_state *pipe_config)
> > {
> > struct drm_i915_private *dev_priv = to_i915(encoder->base.dev);
> > + struct intel_crtc *crtc = to_intel_crtc(pipe_config->base.crtc);
> > +
> > + /*
> > + * For DDI ports we always use a shared PLL.
> > + * But the shared PLL will not be set when crtc is not active.
> > + */
> > + if (crtc->active == false) {
>
> Seem to me that the correct fix would be to do the DPLL readout
> regardless of the state of the pipe.
>
> > + DRM_DEBUG_KMS("Trying to get clock, but pipe is not active.\n");
> > + return;
> > + }
> >
> > if (INTEL_GEN(dev_priv) <= 8)
> > hsw_ddi_clock_get(encoder, pipe_config);
> > --
> > 2.7.4
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > https://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Ville Syrjälä
> Intel OTC
--
Ville Syrjälä
Intel OTC
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-10-30 15:14 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-10-30 8:17 [PATCH] drm/i915: Fix DPLL warning when starting guest VM Zhao, Xinda
2017-10-30 8:37 ` ✗ Fi.CI.BAT: failure for " Patchwork
2017-10-30 13:49 ` [PATCH] " Ville Syrjälä
2017-10-30 15:14 ` Ville Syrjälä [this message]
2017-10-31 3:09 ` Zhao, Xinda
2017-10-31 6:51 ` Zhenyu Wang
2017-10-31 8:51 ` Zhao, Xinda
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=20171030151414.GP10981@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=Zhao@freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-gvt-dev@lists.freedesktop.org \
--cc=xinda.zhao@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.