Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Imre Deak <imre.deak@intel.com>
To: "Murthy, Arun R" <arun.r.murthy@intel.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH] drm/i915: Fix simulated GPU reset wrt. encoder HW readout
Date: Tue, 11 Oct 2022 13:12:46 +0300	[thread overview]
Message-ID: <Y0VBnlm2vei/Vj5k@ideak-desk.fi.intel.com> (raw)
In-Reply-To: <DM6PR11MB3177E0CAC9D1794A550BB201BA239@DM6PR11MB3177.namprd11.prod.outlook.com>

On Tue, Oct 11, 2022 at 10:07:11AM +0300, Murthy, Arun R wrote:
> > [...]
> > diff --git a/drivers/gpu/drm/i915/display/intel_display.c
> > b/drivers/gpu/drm/i915/display/intel_display.c
> > index 8c3bd9ba0d748..b147ea79c566a 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > @@ -830,6 +830,20 @@ intel_plane_fence_y_offset(const struct
> > intel_plane_state *plane_state)
> >       return y;
> >  }
> >
> > +static int
> > +intel_display_commit_duplicated_state(struct intel_atomic_state *state,
> > +                                   struct drm_modeset_acquire_ctx *ctx) {
> > +     struct drm_i915_private *i915 = to_i915(state->base.dev);
> > +     int ret;
> > +
> > +     ret = drm_atomic_helper_commit_duplicated_state(&state->base,
> > ctx);
> > +
> > +     drm_WARN_ON(&i915->drm, ret == -EDEADLK);
> > +
> > +     return ret;
> > +}
>
> Do we need a wrapper function for this, cant the drm function be
> called directly? since the wrapper function does nothing than calling
> drm atomic helper function.

It also WARNs when failing with -EDEADLK, which is not expected when
committing a duplicated state.

> 
> Thanks and Regards,
> Arun R Murthy
> --------------------
> > +
> >  static int
> >  __intel_display_resume(struct drm_i915_private *i915,
> >                      struct drm_atomic_state *state, @@ -837,7 +851,7 @@
> > __intel_display_resume(struct drm_i915_private *i915,  {
> >       struct drm_crtc_state *crtc_state;
> >       struct drm_crtc *crtc;
> > -     int i, ret;
> > +     int i;
> >
> >       intel_modeset_setup_hw_state(i915, ctx);
> >       intel_vga_redisable(i915);
> > @@ -863,11 +877,7 @@ __intel_display_resume(struct drm_i915_private
> > *i915,
> >       if (!HAS_GMCH(i915))
> >               to_intel_atomic_state(state)->skip_intermediate_wm = true;
> >
> > -     ret = drm_atomic_helper_commit_duplicated_state(state, ctx);
> > -
> > -     drm_WARN_ON(&i915->drm, ret == -EDEADLK);
> > -
> > -     return ret;
> > +     return
> > +intel_display_commit_duplicated_state(to_intel_atomic_state(state),
> > +ctx);
> >  }
> >
> >  static bool gpu_reset_clobbers_display(struct drm_i915_private *dev_priv)
> > @@ -959,7 +969,7 @@ void intel_display_finish_reset(struct
> > drm_i915_private *i915)
> >       /* reset doesn't touch the display */
> >       if (!gpu_reset_clobbers_display(i915)) {
> >               /* for testing only restore the display */
> > -             ret = __intel_display_resume(i915, state, ctx);
> > +             ret =
> > +intel_display_commit_duplicated_state(to_intel_atomic_state(state),
> > +ctx);
> >               if (ret)
> >                       drm_err(&i915->drm,
> >                               "Restoring old state failed with %i\n", ret);
> > --
> > 2.37.1
> 

  reply	other threads:[~2022-10-11 10:12 UTC|newest]

Thread overview: 13+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-10-07 13:33 [Intel-gfx] [PATCH] drm/i915: Fix simulated GPU reset wrt. encoder HW readout Imre Deak
2022-10-07 13:42 ` Ville Syrjälä
2022-10-07 14:45 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2022-10-07 15:09 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2022-10-08  8:10   ` Imre Deak
2022-10-10  6:02     ` Vudum, Lakshminarayana
2022-10-09 16:41 ` Patchwork
2022-10-10  5:26 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-10-10  8:02 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-10-14 10:41   ` Imre Deak
2022-10-11  7:07 ` [Intel-gfx] [PATCH] " Murthy, Arun R
2022-10-11 10:12   ` Imre Deak [this message]
2022-10-14 15:56 ` [Intel-gfx] ✓ Fi.CI.IGT: success for " 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=Y0VBnlm2vei/Vj5k@ideak-desk.fi.intel.com \
    --to=imre.deak@intel.com \
    --cc=arun.r.murthy@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    /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