From: Anshuman Gupta <anshuman.gupta@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: jani.nikula@intel.com, intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [RFC 2/6] drm/i915: Remove (pipe == crtc->index) asummption
Date: Thu, 30 Jan 2020 17:32:01 +0530 [thread overview]
Message-ID: <20200130120201.GG24118@intel.com> (raw)
In-Reply-To: <20200123134057.GL13686@intel.com>
On 2020-01-23 at 15:40:57 +0200, Ville Syrjälä wrote:
> On Thu, Jan 23, 2020 at 06:56:55PM +0530, Anshuman Gupta wrote:
> > we can't have (pipe == crtc->index) assumption in
> > driver in order to support 3 non-contiguous
> > display pipe system.
> >
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: Anshuman Gupta <anshuman.gupta@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_display.c | 10 ++++------
> > 1 file changed, 4 insertions(+), 6 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> > index 878d331b9e8c..afd8d43160c6 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > @@ -14070,11 +14070,11 @@ verify_single_dpll_state(struct drm_i915_private *dev_priv,
> > if (new_crtc_state->hw.active)
> > I915_STATE_WARN(!(pll->active_mask & crtc_mask),
> > "pll active mismatch (expected pipe %c in active mask 0x%02x)\n",
> > - pipe_name(drm_crtc_index(&crtc->base)), pll->active_mask);
> > + pipe_name(crtc->pipe), pll->active_mask);
> > else
> > I915_STATE_WARN(pll->active_mask & crtc_mask,
> > "pll active mismatch (didn't expect pipe %c in active mask 0x%02x)\n",
> > - pipe_name(drm_crtc_index(&crtc->base)), pll->active_mask);
> > + pipe_name(crtc->pipe), pll->active_mask);
> >
> > I915_STATE_WARN(!(pll->state.crtc_mask & crtc_mask),
> > "pll enabled crtcs mismatch (expected 0x%x in 0x%02x)\n",
> > @@ -14103,10 +14103,10 @@ verify_shared_dpll_state(struct intel_crtc *crtc,
> >
> > I915_STATE_WARN(pll->active_mask & crtc_mask,
> > "pll active mismatch (didn't expect pipe %c in active mask)\n",
> > - pipe_name(drm_crtc_index(&crtc->base)));
> > + pipe_name(crtc->pipe));
> > I915_STATE_WARN(pll->state.crtc_mask & crtc_mask,
> > "pll enabled crtcs mismatch (found %x in enabled mask)\n",
> > - pipe_name(drm_crtc_index(&crtc->base)));
> > + pipe_name(crtc->pipe));
> > }
> > }
> >
> > @@ -16485,8 +16485,6 @@ static int intel_crtc_init(struct drm_i915_private *dev_priv, enum pipe pipe)
> >
> > intel_color_init(crtc);
> >
> > - WARN_ON(drm_crtc_index(&crtc->base) != crtc->pipe);
> > -
>
> The first and second hunks don't really have anything to do with
> each other. Also the WARN_ON() should not be removed until all the
> assumptions are fixed.
True there can be other assumptions as well, there are few, i have come to know
drm_handle_vblank(&dev_priv->drm, pipe) in gen8_de_irq_handler()
drm_wait_one_vblank(&dev_priv->drm, pipe) in intel_wait_for_vblank(),
i will fix these assumptions is next update, are there any other similar kind of
assumption on which u can throw some light to look for?
I am not sure how does above WARN_ON helps to know all such kind of
assumptions, but it make sense to have it with FIXME.
Thanks,
Anshuman Gupta.
>
> > return 0;
> >
> > fail:
> > --
> > 2.24.0
>
> --
> Ville Syrjälä
> Intel
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2020-01-30 12:11 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-01-23 13:26 [Intel-gfx] [RFC 0/6] 3 display pipes combination system support Anshuman Gupta
2020-01-23 13:26 ` [Intel-gfx] [RFC 1/6] drm/i915: Iterate over pipe and skip the disabled one Anshuman Gupta
2020-01-23 13:48 ` Jani Nikula
2020-01-24 11:59 ` Anshuman Gupta
2020-01-24 12:15 ` Jani Nikula
2020-01-24 12:19 ` Anshuman Gupta
2020-01-24 13:34 ` Jani Nikula
2020-01-23 13:26 ` [Intel-gfx] [RFC 2/6] drm/i915: Remove (pipe == crtc->index) asummption Anshuman Gupta
2020-01-23 13:40 ` Ville Syrjälä
2020-01-30 12:02 ` Anshuman Gupta [this message]
2020-01-30 13:35 ` Ville Syrjälä
2020-01-30 15:27 ` Ville Syrjälä
2020-01-23 13:49 ` Jani Nikula
2020-01-23 13:26 ` [Intel-gfx] [RFC 3/6] drm/i915: Fix wrongly populated plane possible_crtcs bit mask Anshuman Gupta
2020-01-23 13:47 ` Ville Syrjälä
2020-01-23 13:26 ` [Intel-gfx] [RFC 4/6] drm/i915: Get right max plane stride Anshuman Gupta
2020-01-23 13:50 ` Ville Syrjälä
2020-01-23 13:26 ` [Intel-gfx] [RFC 5/6] drm/i915: Add WARN_ON in intel_get_crtc_for_pipe() Anshuman Gupta
2020-01-23 13:52 ` Ville Syrjälä
2020-01-23 13:26 ` [Intel-gfx] [RFC 6/6] drm/i915: Enable 3 display pipes support Anshuman Gupta
2020-01-23 13:53 ` Ville Syrjälä
2020-01-23 21:38 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for 3 display pipes combination system support Patchwork
2020-01-23 22:19 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2020-01-25 13:08 ` [Intel-gfx] ✓ Fi.CI.IGT: " 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=20200130120201.GG24118@intel.com \
--to=anshuman.gupta@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jani.nikula@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 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.