From: "Konduru, Chandra" <chandra.konduru@intel.com>
To: Daniel Vetter <daniel@ffwll.ch>,
Tvrtko Ursulin <tvrtko.ursulin@linux.intel.com>
Cc: "Nikula, Jani" <jani.nikula@intel.com>,
"Intel-gfx@lists.freedesktop.org"
<Intel-gfx@lists.freedesktop.org>,
"Lankhorst, Maarten" <maarten.lankhorst@intel.com>
Subject: Re: [PATCH] drm/i915/skl: Assume no scaling is available when things are not as expected
Date: Mon, 15 Jun 2015 21:03:09 +0000 [thread overview]
Message-ID: <76A9B330A4D78C4D99CB292C4CC06C0E3700789E@fmsmsx101.amr.corp.intel.com> (raw)
In-Reply-To: <20150615104617.GA8341@phenom.ffwll.local>
> >
> > Cdclk < crtc_clock is not allowed and suggests a different problem elsewhere.
> >
> > It is more robust and safe to assume no scaling is possible in this case.
> >
> > Signed-off-by: Tvrtko Ursulin <tvrtko.ursulin@intel.com>
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_display.c | 2 +-
> > 1 file changed, 1 insertion(+), 1 deletion(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_display.c
> b/drivers/gpu/drm/i915/intel_display.c
> > index 93a5e51..4c99373 100644
> > --- a/drivers/gpu/drm/i915/intel_display.c
> > +++ b/drivers/gpu/drm/i915/intel_display.c
> > @@ -13234,7 +13234,7 @@ skl_max_scale(struct intel_crtc *intel_crtc, struct
> intel_crtc_state *crtc_state
> > crtc_clock = crtc_state->base.adjusted_mode.crtc_clock;
> > cdclk = dev_priv->display.get_display_clock_speed(dev);
>
> Probably fallout from the in-flight dynamic cdclk stuff - this code checks
> the wrong bits I guess. Chandra?
Looks like something elsewhere has fallen out and issue manifested here.
Damien reported another issue where get_display_clock_speed causing
an assert because it is called when dev_priv->pm.suspend is true during
runtime resume. But later was resolved after one of atomic patch is
reverted.
While Maarten is addressing recently reported atomic issues, for
time being some atomic crtc patches were reverted.
I am not 100% sure whether issue here is due to same root cause or
due to something different.
>
> Thanks, Daniel
>
> >
> > - if (!crtc_clock || !cdclk)
> > + if (!crtc_clock || !cdclk || (cdclk < crtc_clock))
> > return DRM_PLANE_HELPER_NO_SCALING;
> >
> > /*
> > --
> > 2.4.0
> >
> > _______________________________________________
> > Intel-gfx mailing list
> > Intel-gfx@lists.freedesktop.org
> > http://lists.freedesktop.org/mailman/listinfo/intel-gfx
>
> --
> Daniel Vetter
> Software Engineer, Intel Corporation
> http://blog.ffwll.ch
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2015-06-15 21:03 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2015-06-01 12:04 [PATCH] drm/i915/skl: Assume no scaling is available when things are not as expected Tvrtko Ursulin
2015-06-01 21:45 ` shuang.he
2015-06-15 10:46 ` Daniel Vetter
2015-06-15 21:03 ` Konduru, Chandra [this message]
2015-06-16 13:40 ` Daniel Vetter
2015-06-16 13:46 ` Ville Syrjälä
2015-06-17 11:41 ` Daniel Vetter
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=76A9B330A4D78C4D99CB292C4CC06C0E3700789E@fmsmsx101.amr.corp.intel.com \
--to=chandra.konduru@intel.com \
--cc=Intel-gfx@lists.freedesktop.org \
--cc=daniel@ffwll.ch \
--cc=jani.nikula@intel.com \
--cc=maarten.lankhorst@intel.com \
--cc=tvrtko.ursulin@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 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.