From: "Ville Syrjälä" <ville.syrjala@linux.intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-gfx@lists.freedesktop.org,
Lucas De Marchi <lucas.demarchi@intel.com>
Subject: Re: [Intel-gfx] [PATCH v3 10/11] drm/i915/display: Check if pipe fastset is allowed by external dependencies
Date: Wed, 18 Dec 2019 19:10:20 +0200 [thread overview]
Message-ID: <20191218171020.GP1208@intel.com> (raw)
In-Reply-To: <20191218170019.GO1208@intel.com>
On Wed, Dec 18, 2019 at 07:00:19PM +0200, Ville Syrjälä wrote:
> On Mon, Dec 16, 2019 at 02:07:41PM -0800, José Roberto de Souza wrote:
> > Check if fastset is allowed by external dependencies like other pipes
> > and transcoders.
> >
> > Right now this patch only forces a fullmodeset in MST slaves of MST
> > masters that needs a fullmodeset but it will be needed for port sync
> > as well.
> >
> > v3:
> > - moved handling to intel_atomic_check() this way is guarantee that
> > all pipes will have its state computed
> >
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Cc: Lucas De Marchi <lucas.demarchi@intel.com>
> > Cc: Maarten Lankhorst <maarten.lankhorst@linux.intel.com>
> > Cc: Manasi Navare <manasi.d.navare@intel.com>
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> > drivers/gpu/drm/i915/display/intel_display.c | 63 ++++++++++++++++----
> > 1 file changed, 50 insertions(+), 13 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/display/intel_display.c b/drivers/gpu/drm/i915/display/intel_display.c
> > index f1c0687bf69b..2627a7bcb45c 100644
> > --- a/drivers/gpu/drm/i915/display/intel_display.c
> > +++ b/drivers/gpu/drm/i915/display/intel_display.c
> > @@ -13941,19 +13941,6 @@ static void intel_crtc_check_fastset(const struct intel_crtc_state *old_crtc_sta
> >
> > new_crtc_state->uapi.mode_changed = false;
> > new_crtc_state->update_pipe = true;
> > -
> > - /*
> > - * If we're not doing the full modeset we want to
> > - * keep the current M/N values as they may be
> > - * sufficiently different to the computed values
> > - * to cause problems.
> > - *
> > - * FIXME: should really copy more fuzzy state here
> > - */
> > - new_crtc_state->fdi_m_n = old_crtc_state->fdi_m_n;
> > - new_crtc_state->dp_m_n = old_crtc_state->dp_m_n;
> > - new_crtc_state->dp_m2_n2 = old_crtc_state->dp_m2_n2;
> > - new_crtc_state->has_drrs = old_crtc_state->has_drrs;
> > }
> >
> > static int intel_crtc_add_planes_to_state(struct intel_atomic_state *state,
> > @@ -14121,6 +14108,56 @@ static int intel_atomic_check(struct drm_device *dev,
> > any_ms = true;
> > }
> >
> > + /**
> > + * Check if fastset is allowed by external dependencies like other
> > + * pipes and transcoders.
> > + *
> > + * Right now it only forces a fullmodeset when the MST master
> > + * transcoder did not changed but the pipe of the master transcoder
> > + * needs a fullmodeset so all slaves also needs to do a fullmodeset.
> > + */
> > + for_each_new_intel_crtc_in_state(state, crtc, new_crtc_state, i) {
> > + struct intel_crtc_state *new_crtc_state_iter;
> > + struct intel_crtc *crtc_iter;
> > + int j;
> > +
> > + if (!intel_dp_mst_is_slave_trans(new_crtc_state) ||
> > + needs_modeset(new_crtc_state))
>
> shouldn't this be
> if (!mst_master || !needs_modeset)
> continue;
> ?
>
> > + continue;
> > +
> > + for_each_new_intel_crtc_in_state(state, crtc_iter,
> > + new_crtc_state_iter, j) {
> > + if (new_crtc_state->mst_master_transcoder !=
> > + new_crtc_state_iter->cpu_transcoder)
> > + continue;
> > +
> > + if (needs_modeset(new_crtc_state_iter)) {
> > + new_crtc_state->uapi.mode_changed = true;
> > + new_crtc_state->update_pipe = false;
> > + }
> > + break;
>
> Hmm. So I guess the break here is because we're going to keep iterating
> the outer loop anyway? Don't think that works with the s/slave/master/
> fix above.
>
> I suggest moving this inner loop into a separate function entirely.
> Could simply pass in the master_transcoder to that function and then
> we wouldn't even have this clash with variable names for the two
> crtcs/crtc_states.
>
> Somethig like (with better funciton names ofc :)
>
> mst_modeset_slaves(state, master_transcoder)
> {
> for_each() {
> if (master_transcoder == crtc_state->master_transcoder)
> modeset=1;
> }
> }
>
> atomic_check()
> {
> for_each()
> compute();
>
> for_each() {
> if (master && needs_modeset()
> mst_modeset_slaves(state, crtc_state->cpu_transcoder);
> }
>
> for_each() {
> if (fastset)
> copy();
> }
> }
>
> Or do we also need to force a modeset for the master if a slave needs a
> modeset? I'm trying to think if there's a way that we could end up with
> a slave changing its master (thus needing modeset) without the master
> being flagged for modeset...
How about this:
1. Enable pipe B (master) + pipe C (slave)
2. Enable pipe A (should become master)
Hmm. Scratch that. Pipe B will have it's master_transcoder change from
INVALID to A so it'll get flagged for a modeset. Seems I need a more
heavy duty thinking cap for this one...
--
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:[~2019-12-18 17:10 UTC|newest]
Thread overview: 26+ messages / expand[flat|nested] mbox.gz Atom feed top
2019-12-16 22:07 [Intel-gfx] [PATCH v3 01/11] drm: Add __drm_atomic_helper_crtc_state_reset() & co José Roberto de Souza
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 02/11] drm/i915: s/intel_crtc/crtc/ in intel_crtc_init() José Roberto de Souza
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 03/11] drm/i915: Introduce intel_crtc_{alloc, free}() José Roberto de Souza
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 04/11] drm/i915: Introduce intel_crtc_state_reset() José Roberto de Souza
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 05/11] drm/i915: Introduce intel_plane_state_reset() José Roberto de Souza
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 06/11] drm/i915/display: Share intel_connector_needs_modeset() José Roberto de Souza
2019-12-16 23:52 ` Lucas De Marchi
2019-12-17 16:39 ` Souza, Jose
2019-12-17 17:37 ` Lucas De Marchi
2019-12-18 10:48 ` Ville Syrjälä
2019-12-18 16:38 ` Ville Syrjälä
2019-12-18 17:13 ` Souza, Jose
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 07/11] drm/i915/tgl: Select master transcoder for MST stream José Roberto de Souza
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 08/11] drm/i915/display: Always enables MST master pipe first José Roberto de Souza
2019-12-18 16:43 ` Ville Syrjälä
2019-12-18 17:27 ` Souza, Jose
2019-12-18 18:24 ` Ville Syrjälä
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 09/11] drm/i915/dp: Fix MST disable sequences José Roberto de Souza
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 10/11] drm/i915/display: Check if pipe fastset is allowed by external dependencies José Roberto de Souza
2019-12-18 17:00 ` Ville Syrjälä
2019-12-18 17:10 ` Ville Syrjälä [this message]
2019-12-18 17:38 ` Souza, Jose
2019-12-16 22:07 ` [Intel-gfx] [PATCH v3 11/11] drm/i915/display: Add comment to a function that probably can be removed José Roberto de Souza
2019-12-16 23:35 ` [Intel-gfx] [PATCH v3 01/11] drm: Add __drm_atomic_helper_crtc_state_reset() & co Lucas De Marchi
2019-12-17 5:13 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v3,01/11] " Patchwork
2019-12-17 14:44 ` [Intel-gfx] ✗ Fi.CI.BAT: failure for series starting with [v3,01/11] drm: Add __drm_atomic_helper_crtc_state_reset() & co. (rev2) 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=20191218171020.GP1208@intel.com \
--to=ville.syrjala@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.souza@intel.com \
--cc=lucas.demarchi@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