From: "Souza, Jose" <jose.souza@intel.com>
To: "cazyokoyama@gmail.com" <cazyokoyama@gmail.com>
Cc: "intel-gfx@lists.freedesktop.org" <intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH v2 4/4] drm/i915/display: Remove MBUS joining invalid TODOs
Date: Tue, 22 Mar 2022 22:02:23 +0000 [thread overview]
Message-ID: <b91fe3cc8989d5651597cf9ac80954db5a960e49.camel@intel.com> (raw)
In-Reply-To: <CABhNg0hh47jNo_a4EpsrhsRYcB7Mn86+f6oykX0kvGv0XPtuSg@mail.gmail.com>
On Tue, 2022-03-22 at 14:58 -0700, Caz Yokoyama wrote:
>
>
> On Tue, Mar 22, 2022 at 2:45 PM José Roberto de Souza <jose.souza@intel.com> wrote:
> > skl_compute_ddb() will for a modeset in all pipes when MBUS joining
> > changes between states, so all pipes will be disabled, have all
> > MBUS related registers updated and then each pipe enabled.
> >
>
> I am not clear what you want to say here. Could you rephrase above 3 lines?
Ops it should be:
skl_compute_ddb() will do a modeset in all pipes when MBUS joining changes between atomic commits, so all pipes will be disabled, have all MBUS
related registers updated and then each pipe enabled.
>
> > So no vblank syncronization is necessary and here droping those TODOs.
> >
>
> dropping
> -caz
>
> >
> > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> > drivers/gpu/drm/i915/intel_pm.c | 5 -----
> > 1 file changed, 5 deletions(-)
> >
> > diff --git a/drivers/gpu/drm/i915/intel_pm.c b/drivers/gpu/drm/i915/intel_pm.c
> > index cf290bb704221..9ccf0f062862c 100644
> > --- a/drivers/gpu/drm/i915/intel_pm.c
> > +++ b/drivers/gpu/drm/i915/intel_pm.c
> > @@ -6066,7 +6066,6 @@ skl_compute_ddb(struct intel_atomic_state *state)
> > return ret;
> >
> > if (old_dbuf_state->joined_mbus != new_dbuf_state->joined_mbus) {
> > - /* TODO: Implement vblank synchronized MBUS joining changes */
> > ret = intel_modeset_all_pipes(state);
> > if (ret)
> > return ret;
> > @@ -8195,10 +8194,6 @@ static void update_mbus_pre_enable(struct intel_atomic_state *state)
> > if (!HAS_MBUS_JOINING(dev_priv))
> > return;
> >
> > - /*
> > - * TODO: Implement vblank synchronized MBUS joining changes.
> > - * Must be properly coordinated with dbuf reprogramming.
> > - */
> > if (dbuf_state->joined_mbus) {
> > mbus_ctl = MBUS_HASHING_MODE_1x4 | MBUS_JOIN |
> > MBUS_JOIN_PIPE_SELECT_NONE;
> > --
> > 2.35.1
> >
>
>
next prev parent reply other threads:[~2022-03-22 22:02 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-22 21:46 [Intel-gfx] [PATCH v2 1/4] drm/i915/display: Program PIPE_MBUS_DBOX_CTL with adl-p values José Roberto de Souza
2022-03-22 21:46 ` [Intel-gfx] [PATCH v2 2/4] drm/i915/display: Add HAS_MBUS_JOINING José Roberto de Souza
2022-03-22 21:46 ` [Intel-gfx] [PATCH v2 3/4] drm/i915/display/adlp: Fix programing of PIPE_MBUS_DBOX_CTL José Roberto de Souza
2022-03-24 11:30 ` Ville Syrjälä
2022-03-24 12:58 ` Souza, Jose
2022-03-25 18:06 ` Ville Syrjälä
2022-03-22 21:46 ` [Intel-gfx] [PATCH v2 4/4] drm/i915/display: Remove MBUS joining invalid TODOs José Roberto de Souza
2022-03-22 21:58 ` Caz Yokoyama
2022-03-22 22:02 ` Souza, Jose [this message]
2022-03-24 11:12 ` Ville Syrjälä
2022-03-22 22:43 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for series starting with [v2,1/4] drm/i915/display: Program PIPE_MBUS_DBOX_CTL with adl-p values Patchwork
2022-03-22 22:47 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-22 23:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-23 7:59 ` [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=b91fe3cc8989d5651597cf9ac80954db5a960e49.camel@intel.com \
--to=jose.souza@intel.com \
--cc=cazyokoyama@gmail.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