From: "Lisovskiy, Stanislav" <stanislav.lisovskiy@intel.com>
To: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: intel-gfx@lists.freedesktop.org
Subject: Re: [PATCH 8/8] drm/i915: Handle joined pipes inside hsw_crtc_disable()
Date: Fri, 1 Mar 2024 18:22:19 +0200 [thread overview]
Message-ID: <ZeIAuyrebrSiF2Sw@intel.com> (raw)
In-Reply-To: <ZeH98WJ1ONKtEgEI@intel.com>
On Fri, Mar 01, 2024 at 06:10:25PM +0200, Ville Syrjälä wrote:
> On Fri, Mar 01, 2024 at 06:04:27PM +0200, Lisovskiy, Stanislav wrote:
> > On Fri, Mar 01, 2024 at 04:36:00PM +0200, Ville Syrjala wrote:
> > > From: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > >
> > > Reorganize the crtc disable path to only deal with the
> > > master pipes/transcoders in intel_old_crtc_state_disables()
> > > and offload the handling of joined pipes to hsw_crtc_disable().
> > > This makes the whole thing much more sensible since we can
> > > actually control the order in which we do the per-pipe vs.
> > > per-transcoder modeset steps.
> > >
> > > Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > ---
> > > drivers/gpu/drm/i915/display/intel_display.c | 64 ++++++++++++--------
> > > 1 file changed, 38 insertions(+), 26 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> > > index 1df3923cc30d..07239c1ce9df 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > > @@ -1793,29 +1793,27 @@ static void hsw_crtc_disable(struct intel_atomic_state *state,
> > > const struct intel_crtc_state *old_master_crtc_state =
> > > intel_atomic_get_old_crtc_state(state, master_crtc);
> > > struct drm_i915_private *i915 = to_i915(master_crtc->base.dev);
> > > + u8 pipe_mask = intel_crtc_joined_pipe_mask(old_master_crtc_state);
> > > + struct intel_crtc *crtc;
> > >
> > > /*
> > > * FIXME collapse everything to one hook.
> > > * Need care with mst->ddi interactions.
> > > */
> > > - if (!intel_crtc_is_bigjoiner_slave(old_master_crtc_state)) {
> > > - intel_encoders_disable(state, master_crtc);
> > > - intel_encoders_post_disable(state, master_crtc);
> > > - }
> > > -
> > > - intel_disable_shared_dpll(old_master_crtc_state);
> > > + intel_encoders_disable(state, master_crtc);
> > > + intel_encoders_post_disable(state, master_crtc);
> > >
> > > - if (!intel_crtc_is_bigjoiner_slave(old_master_crtc_state)) {
> > > - struct intel_crtc *slave_crtc;
> > > + for_each_intel_crtc_in_pipe_mask(&i915->drm, crtc, pipe_mask) {
> > > + const struct intel_crtc_state *old_crtc_state =
> > > + intel_atomic_get_old_crtc_state(state, crtc);
> > >
> > > - intel_encoders_post_pll_disable(state, master_crtc);
> > > + intel_disable_shared_dpll(old_crtc_state);
> > > + }
> > >
> > > - intel_dmc_disable_pipe(i915, master_crtc->pipe);
> > > + intel_encoders_post_pll_disable(state, master_crtc);
> > >
> > > - for_each_intel_crtc_in_pipe_mask(&i915->drm, slave_crtc,
> > > - intel_crtc_bigjoiner_slave_pipes(old_master_crtc_state))
> > > - intel_dmc_disable_pipe(i915, slave_crtc->pipe);
> > > - }
> > > + for_each_intel_crtc_in_pipe_mask(&i915->drm, crtc, pipe_mask)
> > > + intel_dmc_disable_pipe(i915, crtc->pipe);
> > > }
> >
> > Okay the only difference from hsw_crtc_disable part from my patch is that
> > I don't have intel_crtc_joined_pipe_mask and encoder calls are outside the pipe
> > loop. Ok. You could of course just communicate this to me, it is quite a small
> > thing to change.
> >
> > And still there is a question about how to handle the crtc enable side, since
> > extracting transcoder programming from the pipe loop, will break the sequence,
> > as I described. Either it is ok that we will partly program slave/master pipe, then
> > program transcoder then again program slave/master pipes or it has to be
> > in a pipe loop.
>
> Transcoder stuff shouldn't be in pipe loops. That's what
> I've been saying all along.
Yep, I realize you kept saying this and I described you the problem what happens if
we extract it from there.
Either it is ok to have 2 loops and have transcoder programming in between or you
first program pipes then program the transcoder - in both cases that would change
the sequence of how it is done now.
My question was if this is ok or not.
Stan
>
> --
> Ville Syrjälä
> Intel
next prev parent reply other threads:[~2024-03-01 16:22 UTC|newest]
Thread overview: 32+ messages / expand[flat|nested] mbox.gz Atom feed top
2024-03-01 14:35 [PATCH 0/8] drm/i915: Bigjoiner stuff Ville Syrjala
2024-03-01 14:35 ` [PATCH 1/8] drm/i915: Rename the crtc/crtc_states in the top level DDI hooks/etc Ville Syrjala
2024-03-05 8:41 ` Lisovskiy, Stanislav
2024-03-05 8:50 ` Ville Syrjälä
2024-03-05 9:08 ` Lisovskiy, Stanislav
2024-03-05 9:19 ` Ville Syrjälä
2024-03-05 14:07 ` Jani Nikula
2024-03-05 14:34 ` Ville Syrjälä
2024-03-05 14:57 ` Jani Nikula
2024-03-01 14:35 ` [PATCH 2/8] drm/i915: Introduce intel_crtc_joined_pipe_mask() Ville Syrjala
2024-03-01 14:35 ` [PATCH 3/8] drm/i915: Extract intel_ddi_post_disable_hdmi_or_sst() Ville Syrjala
2024-03-05 8:47 ` Lisovskiy, Stanislav
2024-03-01 14:35 ` [PATCH 4/8] drm/i915: Utilize intel_crtc_joined_pipe_mask() more Ville Syrjala
2024-03-01 14:35 ` [PATCH 5/8] drm/i915: Precompute disable_pipes bitmask in intel_commit_modeset_disables() Ville Syrjala
2024-03-05 8:49 ` Lisovskiy, Stanislav
2024-03-01 14:35 ` [PATCH 6/8] drm/i915: Disable planes more atomically during modesets Ville Syrjala
2024-03-05 8:58 ` Lisovskiy, Stanislav
2024-03-01 14:35 ` [PATCH 7/8] drm/i915: Simplify intel_old_crtc_state_disables() calling convention Ville Syrjala
2024-03-05 8:59 ` Lisovskiy, Stanislav
2024-03-01 14:36 ` [PATCH 8/8] drm/i915: Handle joined pipes inside hsw_crtc_disable() Ville Syrjala
2024-03-01 16:04 ` Lisovskiy, Stanislav
2024-03-01 16:10 ` Ville Syrjälä
2024-03-01 16:22 ` Lisovskiy, Stanislav [this message]
2024-03-01 16:47 ` Ville Syrjälä
2024-03-04 8:55 ` Lisovskiy, Stanislav
2024-03-01 16:08 ` Lisovskiy, Stanislav
2024-03-01 16:15 ` Ville Syrjälä
2024-03-01 17:23 ` [PATCH v2 " Ville Syrjala
2024-03-04 6:44 ` Srinivas, Vidya
2024-03-04 10:20 ` Lisovskiy, Stanislav
2024-03-01 19:54 ` ✗ Fi.CI.CHECKPATCH: warning for drm/i915: Bigjoiner stuff (rev2) Patchwork
2024-03-01 20:12 ` ✗ Fi.CI.BAT: failure " 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=ZeIAuyrebrSiF2Sw@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;
as well as URLs for NNTP newsgroup(s).