Intel-GFX Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: "Souza, Jose" <jose.souza@intel.com>
To: "Mun, Gwan-gyeong" <gwan-gyeong.mun@intel.com>,
	"intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [PATCH 3/4] drm/i915: Nuke ORIGIN_GTT
Date: Tue, 3 Aug 2021 17:19:19 +0000	[thread overview]
Message-ID: <42fd8ffa5aab181c4e82e30b8c9d67e61c03ee66.camel@intel.com> (raw)
In-Reply-To: <29fc7f2e-93e9-229b-0fd6-75e4b988edef@intel.com>

On Tue, 2021-08-03 at 14:20 +0300, Gwan-gyeong Mun wrote:
> 
> On 7/31/21 3:10 AM, José Roberto de Souza wrote:
> > There is no users of it, so no need to keep handling for it.
> > 
> > Cc: Gwan-gyeong Mun <gwan-gyeong.mun@intel.com>
> > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > ---
> >   drivers/gpu/drm/i915/display/intel_fbc.c         | 10 +---------
> >   drivers/gpu/drm/i915/display/intel_frontbuffer.h |  3 +--
> >   2 files changed, 2 insertions(+), 11 deletions(-)
> > 
> > diff --git a/drivers/gpu/drm/i915/display/intel_fbc.c b/drivers/gpu/drm/i915/display/intel_fbc.c
> > index ddfc17e21668a..e4d412d395c34 100644
> > --- a/drivers/gpu/drm/i915/display/intel_fbc.c
> > +++ b/drivers/gpu/drm/i915/display/intel_fbc.c
> > @@ -1129,7 +1129,7 @@ void intel_fbc_invalidate(struct drm_i915_private *dev_priv,
> >   	if (!HAS_FBC(dev_priv))
> >   		return;
> >   
> > -	if (origin == ORIGIN_GTT || origin == ORIGIN_FLIP)
> > +	if (origin == ORIGIN_FLIP)
> >   		return;
> >   
> >   	mutex_lock(&fbc->lock);
> > @@ -1150,14 +1150,6 @@ void intel_fbc_flush(struct drm_i915_private *dev_priv,
> >   	if (!HAS_FBC(dev_priv))
> >   		return;
> >   
> > -	/*
> > -	 * GTT tracking does not nuke the entire cfb
> > -	 * so don't clear busy_bits set for some other
> > -	 * reason.
> > -	 */
> > -	if (origin == ORIGIN_GTT)
> > -		return;
> > -
> >   	mutex_lock(&fbc->lock);
> >   
> >   	fbc->busy_bits &= ~frontbuffer_bits;
> > diff --git a/drivers/gpu/drm/i915/display/intel_frontbuffer.h b/drivers/gpu/drm/i915/display/intel_frontbuffer.h
> > index 6d41f53944250..4b977c1e4d52b 100644
> > --- a/drivers/gpu/drm/i915/display/intel_frontbuffer.h
> > +++ b/drivers/gpu/drm/i915/display/intel_frontbuffer.h
> > @@ -33,8 +33,7 @@
> >   struct drm_i915_private;
> >   
> >   enum fb_op_origin {
> > -	ORIGIN_GTT,
> > -	ORIGIN_CPU,
> > +	ORIGIN_CPU = 0,
> >   	ORIGIN_CS,
> >   	ORIGIN_FLIP,
> >   	ORIGIN_DIRTYFB,
> > 
> Is this patch absolutely necessary for this series?

Nope, just notice this unused ORIGIN_GTT while debugging.

  reply	other threads:[~2021-08-03 17:19 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2021-07-31  0:10 [Intel-gfx] [PATCH 1/4] drm/i915/display/tgl+: Dispatch atomic commits instead of front buffer modifications José Roberto de Souza
2021-07-31  0:10 ` [Intel-gfx] [PATCH 2/4] drm/i915/display: Fix sel fetch plane offset calculation José Roberto de Souza
2021-08-13  7:40   ` Gwan-gyeong Mun
2021-07-31  0:10 ` [Intel-gfx] [PATCH 3/4] drm/i915: Nuke ORIGIN_GTT José Roberto de Souza
2021-08-03 11:20   ` Gwan-gyeong Mun
2021-08-03 17:19     ` Souza, Jose [this message]
2021-08-13  7:41       ` Gwan-gyeong Mun
2021-07-31  0:10 ` [Intel-gfx] [PATCH 4/4] DO_NOT_MERGE: drm/i915/display: Enable PSR2 selective fetch by default José Roberto de Souza
2021-08-03 11:17   ` Gwan-gyeong Mun
2021-08-03 17:18     ` Souza, Jose
2021-08-05 18:26       ` Gwan-gyeong Mun
2021-08-05 21:47         ` Souza, Jose
2021-07-31  0:14 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for series starting with [1/4] drm/i915/display/tgl+: Dispatch atomic commits instead of front buffer modifications Patchwork
2021-07-31  0:45 ` [Intel-gfx] ✗ Fi.CI.BAT: failure " Patchwork
2021-08-12 17:24 ` [Intel-gfx] [PATCH 1/4] " Souza, Jose
2021-08-12 19:02   ` Daniel Vetter

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=42fd8ffa5aab181c4e82e30b8c9d67e61c03ee66.camel@intel.com \
    --to=jose.souza@intel.com \
    --cc=gwan-gyeong.mun@intel.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