Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [Intel-gfx] [PATCH] drm/i915/mtl: Copy c10 phy pll sw state from master to slave for bigjoiner
Date: Fri, 21 Apr 2023 15:19:42 +0300	[thread overview]
Message-ID: <ZEJ/XgsHWBrwWeEa@intel.com> (raw)
In-Reply-To: <ZEJ1Z2gnKPswMks7@intel.com>

On Fri, Apr 21, 2023 at 02:37:11PM +0300, Lisovskiy, Stanislav wrote:
> On Fri, Apr 21, 2023 at 12:26:08PM +0300, Ville Syrjälä wrote:
> > On Fri, Apr 21, 2023 at 11:35:20AM +0300, Stanislav Lisovskiy wrote:
> > > We try to verify pll registers in sw state for slave crtc with the hw state.
> > > However in case of bigjoiner we don't calculate those at all, so this verification
> > > will then always fail.
> > > So we should either skip the verification for Bigjoiner slave crtc or copy sw state
> > > from master crtc.
> > > 
> > > Signed-off-by: Stanislav Lisovskiy <stanislav.lisovskiy@intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/display/intel_display.c | 1 +
> > >  1 file changed, 1 insertion(+)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> > > index bf391a6cd8d6..83c98791fea3 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > > @@ -4556,6 +4556,7 @@ copy_bigjoiner_crtc_state_modeset(struct intel_atomic_state *state,
> > >  	drm_mode_copy(&slave_crtc_state->hw.adjusted_mode,
> > >  		      &master_crtc_state->hw.adjusted_mode);
> > >  	slave_crtc_state->hw.scaling_filter = master_crtc_state->hw.scaling_filter;
> > > +	slave_crtc_state->cx0pll_state = master_crtc_state->cx0pll_state;
> > 
> > Wrong place. Also we're already copying dpll_hw_state which is in the
> > same union, and on first blush looks bigger than this thing. So why is
> > that not working?
> 
> No we aren't copying it, we are "saving" it earlier, however it doesn't help at all:
> 
> /* preserve some things from the slave's original crtc state */
> saved_state->uapi = slave_crtc_state->uapi;
> saved_state->scaler_state = slave_crtc_state->scaler_state;
> saved_state->shared_dpll = slave_crtc_state->shared_dpll;
> saved_state->dpll_hw_state = slave_crtc_state->dpll_hw_state;

Hmm. How is anything at all working if we keep this around
from the old state?

Looks like I probably broke this in
commit 0ff0e219d9b8 ("drm/i915: Compute clocks earlier")
and somehow no one has noticed.

The correct fix would seem to be to just nuke that
dpll_hw_state preservation above.


> saved_state->crc_enabled = slave_crtc_state->crc_enabled;
> 
> intel_crtc_free_hw_state(slave_crtc_state);
> memcpy(slave_crtc_state, saved_state, sizeof(*slave_crtc_state));
> kfree(saved_state);
> 
> /* Re-init hw state */
> memset(&slave_crtc_state->hw, 0, sizeof(slave_crtc_state->hw));
> slave_crtc_state->hw.enable = master_crtc_state->hw.enable;
> slave_crtc_state->hw.active = master_crtc_state->hw.active;
> 
> because I guess it just didn't have that stuff initially.
> 
> It starts to work without those verify WARN's only if I copy it from master_crtc_state.
> 
> Stan
> 
> > 
> > >  
> > >  	copy_bigjoiner_crtc_state_nomodeset(state, slave_crtc);
> > >  
> > > -- 
> > > 2.37.3
> > 
> > -- 
> > Ville Syrjälä
> > Intel

-- 
Ville Syrjälä
Intel

  reply	other threads:[~2023-04-21 12:19 UTC|newest]

Thread overview: 9+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-21  8:35 [Intel-gfx] [PATCH] drm/i915/mtl: Copy c10 phy pll sw state from master to slave for bigjoiner Stanislav Lisovskiy
2023-04-21  9:26 ` Ville Syrjälä
2023-04-21 11:37   ` Lisovskiy, Stanislav
2023-04-21 12:19     ` Ville Syrjälä [this message]
2023-04-21 12:43       ` Lisovskiy, Stanislav
2023-04-21 12:52         ` Ville Syrjälä
2023-04-21 11:17 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2023-04-21 11:25 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2023-04-21 18:29 ` [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=ZEJ/XgsHWBrwWeEa@intel.com \
    --to=ville.syrjala@linux.intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=stanislav.lisovskiy@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