Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH 1/3] drm/i915: Drop redundant !modeset check
Date: Thu, 12 Oct 2023 01:10:06 +0300	[thread overview]
Message-ID: <ZScdPmLom5xnapGD@intel.com> (raw)
In-Reply-To: <ZSbELYuH25Rb5iHb@intel.com>

On Wed, Oct 11, 2023 at 06:50:05PM +0300, Ville Syrjälä wrote:
> On Wed, Oct 11, 2023 at 04:47:00PM +0300, Lisovskiy, Stanislav wrote:
> > On Thu, Sep 07, 2023 at 03:25:39PM +0300, Ville Syrjala wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > 
> > > Since commit 7de5b6b54630 ("drm/i915: Don't flag both full
> > > modeset and fastset at the same time")
> > > intel_crtc_needs_fastset() and intel_crtc_needs_modeset() have
> > > been mutually exclusive. Drop the redundant check.
> > > 
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > 
> > Let's see if the crash returns, however if it does then anyway
> > its time to change/refactor bigjoiner logic(as we suspected it
> > to be bigjoiner issue)
> 
> You must be thinking of some other patch.

Yeah right, it was about another one.
Anyways that change is ok for me.

Stan

> 
> > 
> > Reviewed-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > 
> > > ---
> > >  drivers/gpu/drm/i915/display/intel_display.c | 2 +-
> > >  1 file changed, 1 insertion(+), 1 deletion(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> > > index 83e1bc858b9f..526f38b502be 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > > @@ -6606,7 +6606,7 @@ static void intel_update_crtc(struct intel_atomic_state *state,
> > >  	 * valid pipe configuration from the BIOS we need to take care
> > >  	 * of enabling them on the CRTC's first fastset.
> > >  	 */
> > > -	if (intel_crtc_needs_fastset(new_crtc_state) && !modeset &&
> > > +	if (intel_crtc_needs_fastset(new_crtc_state) &&
> > >  	    old_crtc_state->inherited)
> > >  		intel_crtc_arm_fifo_underrun(crtc, new_crtc_state);
> > >  }
> > > -- 
> > > 2.41.0
> > > 
> 
> -- 
> Ville Syrjälä
> Intel

  reply	other threads:[~2023-10-11 22:10 UTC|newest]

Thread overview: 11+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-09-07 12:25 [Intel-gfx] [PATCH 0/3] drm/i915: Slightly more atomic multi-pipe commits Ville Syrjala
2023-09-07 12:25 ` [Intel-gfx] [PATCH 1/3] drm/i915: Drop redundant !modeset check Ville Syrjala
2023-10-11 13:47   ` Lisovskiy, Stanislav
2023-10-11 15:50     ` Ville Syrjälä
2023-10-11 22:10       ` Lisovskiy, Stanislav [this message]
2023-09-07 12:25 ` [Intel-gfx] [PATCH 2/3] drm/i915: Split intel_update_crtc() into two parts Ville Syrjala
2023-11-08 14:49   ` Lisovskiy, Stanislav
2023-09-07 12:25 ` [Intel-gfx] [PATCH 3/3] drm/i915: Do plane/etc. updates more atomically across pipes Ville Syrjala
2023-10-11 13:48   ` Lisovskiy, Stanislav
2023-09-07 14:51 ` [Intel-gfx] ✓ Fi.CI.BAT: success for drm/i915: Slightly more atomic multi-pipe commits Patchwork
2023-09-07 16:50 ` [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=ZScdPmLom5xnapGD@intel.com \
    --to=stanislav.lisovskiy@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