From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Jani Nikula" <jani.nikula@linux.intel.com>,
"Ville Syrjälä" <ville.syrjala@intel.com>
Cc: "Chaitanya Kumar Borah" <chaitanya.kumar.borah@intel.com>,
intel-xe@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>,
"Nemesa Garg" <nemesa.garg@intel.com>
Subject: Re: [PATCH] drm/i915/dp_mst: Remove duplicate intel_pfit_compute_config() call
Date: Fri, 7 Aug 2026 07:55:35 -0400 [thread overview]
Message-ID: <anXHt7b02V4s-tQ1@intel.com> (raw)
In-Reply-To: <anTmAUupVyP6fiA4@intel.com>
On Thu, Aug 06, 2026 at 03:52:33PM -0400, Rodrigo Vivi wrote:
> On Thu, Aug 06, 2026 at 12:30:16PM +0300, Jani Nikula wrote:
> > On Thu, 06 Aug 2026, Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com> wrote:
> > > mst_stream_compute_config() called intel_pfit_compute_config() twice
> > > in a row. Probably because of a bad merge. Drop the redundant duplicate
> > > call.
> > >
> > > Cc: Rodrigo Vivi <rodrigo.vivi@intel.com>
> > > Cc: Ville Syrjälä <ville.syrjala@linux.intel.com>
> > > Cc: Nemesa Garg <nemesa.garg@intel.com>
> > > Cc: Jani Nikula <jani.nikula@linux.intel.com>
> > > Fixes: 5ce9ac1531b8 ("drm/i915/mst: Call intel_pfit_compute_config() for sharpness filter")
> >
> > Rodrigo, by the looks of it, this was an unnecessary cherry-pick for
> > fixes. The context for 5ce9ac1531b8 shows the existing call, so I don't
> > think this is a merge failure. But why it happened, no idea!
>
> Indeed weird, I should had caught that on the fixes, I'm sorry.
>
> but it is weird anyway, looking to
> d4686f34bbeb ("drm/i915/pfit: Call intel_pfit_compute_config() unconditionally on (e)DP/HDMI")
>
> which is the mentioned fixed patch, it actually introduces this chunck.
> Then the fix patch introduces this again.
>
> So, it looks like this also occurred on the drm-intel-next first anyway?
I'm sorry, I got confused by intel_dp.c vs intel_dp_mst.c.
The thing is that
5ce9ac1531b8 ("drm/i915/mst: Call intel_pfit_compute_config() for sharpness filter")
should never had been cherry-picked because
ca97f5546f19 ("drm/i915/mst: Call intel_pfit_compute_config() for sharpness filter")
was already in the same tree.
git didn't notice it and move forward with the cherry-pick
dim couldn't have possibly noticed it and proceeded
I failed to review and notice the duplication. I'm sorry about that.
and the duplication then propagated to all the branches...
Reviewed-by: Rodrigo Vivi <rodrigo.vivi@intel.com>
for this patch here....
I pushing it right away to drm-intel-next.
>
> Ville, thoughts?
>
> >
> > BR,
> > Jani.
> >
> >
> > > Signed-off-by: Chaitanya Kumar Borah <chaitanya.kumar.borah@intel.com>
> > > ---
> > > drivers/gpu/drm/i915/display/intel_dp_mst.c | 4 ----
> > > 1 file changed, 4 deletions(-)
> > >
> > > diff --git a/drivers/gpu/drm/i915/display/intel_dp_mst.c b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > > index 3be1643f8d03..57daed0b0b36 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > > +++ b/drivers/gpu/drm/i915/display/intel_dp_mst.c
> > > @@ -761,10 +761,6 @@ static int mst_stream_compute_config(struct intel_atomic_state *state,
> > > pipe_config->sink_format = INTEL_OUTPUT_FORMAT_RGB;
> > > pipe_config->output_format = INTEL_OUTPUT_FORMAT_RGB;
> > >
> > > - ret = intel_pfit_compute_config(pipe_config, conn_state);
> > > - if (ret)
> > > - return ret;
> > > -
> > > ret = intel_pfit_compute_config(pipe_config, conn_state);
> > > if (ret)
> > > return ret;
> >
> > --
> > Jani Nikula, Intel
next prev parent reply other threads:[~2026-08-07 11:55 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-06 7:48 [PATCH] drm/i915/dp_mst: Remove duplicate intel_pfit_compute_config() call Chaitanya Kumar Borah
2026-08-06 8:28 ` Garg, Nemesa
2026-08-06 9:30 ` Jani Nikula
2026-08-06 19:52 ` Rodrigo Vivi
2026-08-07 11:55 ` Rodrigo Vivi [this message]
2026-08-07 12:00 ` Rodrigo Vivi
2026-08-06 21:49 ` ✓ i915.CI.BAT: 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=anXHt7b02V4s-tQ1@intel.com \
--to=rodrigo.vivi@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=jani.nikula@linux.intel.com \
--cc=nemesa.garg@intel.com \
--cc=ville.syrjala@intel.com \
--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