All of lore.kernel.org
 help / color / mirror / Atom feed
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-gfx] [Intel-xe] [PATCH v2 rebased 1/6] drm/i915: Nuke unused dsparb_lock
Date: Mon, 10 Apr 2023 11:26:57 -0400	[thread overview]
Message-ID: <ZDQqwfP+ZcONL2wO@intel.com> (raw)
In-Reply-To: <9cdff10d82ca47241257edf8c8443e5368464692.camel@intel.com>

On Mon, Apr 10, 2023 at 10:43:12AM -0400, Souza, Jose wrote:
> On Thu, 2023-04-06 at 16:38 -0400, Rodrigo Vivi wrote:
> > On Thu, Apr 06, 2023 at 07:31:28AM -0700, José Roberto de Souza wrote:
> > > dsparb_lock it not used anymore, nuke it.
> > 
> > Well, this doesn't exist in our drm-tip baseline, so it would be good
> > if this patch is a fixup! to whatever patch is adding this back here.
> > 
> > Take a look to the Jani series I just pushed:
> > 
> > https://lists.freedesktop.org/archives/intel-xe/2023-April/002000.html
> > 
> > I believe you should make this series on something more like that.
> > so on a next step I run a rebase --autosquash and we get cleaner patches.
> > 
> > Also, I believe this series here might conflict with that, so I'm
> > afraid you will have to rebase it anyway. Sorry about that...
> 
> Will skip this patch then, it will probably be gone in next rebase.

no. we do need to remove it. But the right way is with a
fixup! drm/i915/display: Remaining changes to make xe compile

A patch that removes this dsparb_lock from the patch that is now incorrectly
addding it in our xe tree.

> 
> Can you please take a look at the other 5 patches before I send a new version?

I will take a look one by one...

> 
> > 
> > > 
> > > Cc: intel-gfx@lists.freedesktop.org
> > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/display/intel_display_core.h | 3 ---
> > >  drivers/gpu/drm/i915/i915_driver.c                | 1 -
> > >  2 files changed, 4 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/display/intel_display_core.h b/drivers/gpu/drm/i915/display/intel_display_core.h
> > > index cc058eb303ee8..d2346d43d1162 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_display_core.h
> > > +++ b/drivers/gpu/drm/i915/display/intel_display_core.h
> > > @@ -266,9 +266,6 @@ struct intel_wm {
> > >  	 */
> > >  	struct mutex wm_mutex;
> > >  
> > > -	/* protects DSPARB registers on pre-g4x/vlv/chv */
> > > -	spinlock_t dsparb_lock;
> > > -
> > >  	bool ipc_enabled;
> > >  };
> > >  
> > > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > > index 066d79c2069c4..ea2cc56d18a6e 100644
> > > --- a/drivers/gpu/drm/i915/i915_driver.c
> > > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > > @@ -214,7 +214,6 @@ static int i915_driver_early_probe(struct drm_i915_private *dev_priv)
> > >  	spin_lock_init(&dev_priv->irq_lock);
> > >  	spin_lock_init(&dev_priv->gpu_error.lock);
> > >  	spin_lock_init(&dev_priv->display.fb_tracking.lock);
> > > -	spin_lock_init(&dev_priv->display.wm.dsparb_lock);
> > >  	mutex_init(&dev_priv->display.backlight.lock);
> > >  
> > >  	mutex_init(&dev_priv->sb_lock);
> > > -- 
> > > 2.40.0
> > > 
> 

WARNING: multiple messages have this Message-ID (diff)
From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "Souza, Jose" <jose.souza@intel.com>
Cc: "intel-gfx@lists.freedesktop.org"
	<intel-gfx@lists.freedesktop.org>,
	"intel-xe@lists.freedesktop.org" <intel-xe@lists.freedesktop.org>
Subject: Re: [Intel-xe] [PATCH v2 rebased 1/6] drm/i915: Nuke unused dsparb_lock
Date: Mon, 10 Apr 2023 11:26:57 -0400	[thread overview]
Message-ID: <ZDQqwfP+ZcONL2wO@intel.com> (raw)
In-Reply-To: <9cdff10d82ca47241257edf8c8443e5368464692.camel@intel.com>

On Mon, Apr 10, 2023 at 10:43:12AM -0400, Souza, Jose wrote:
> On Thu, 2023-04-06 at 16:38 -0400, Rodrigo Vivi wrote:
> > On Thu, Apr 06, 2023 at 07:31:28AM -0700, José Roberto de Souza wrote:
> > > dsparb_lock it not used anymore, nuke it.
> > 
> > Well, this doesn't exist in our drm-tip baseline, so it would be good
> > if this patch is a fixup! to whatever patch is adding this back here.
> > 
> > Take a look to the Jani series I just pushed:
> > 
> > https://lists.freedesktop.org/archives/intel-xe/2023-April/002000.html
> > 
> > I believe you should make this series on something more like that.
> > so on a next step I run a rebase --autosquash and we get cleaner patches.
> > 
> > Also, I believe this series here might conflict with that, so I'm
> > afraid you will have to rebase it anyway. Sorry about that...
> 
> Will skip this patch then, it will probably be gone in next rebase.

no. we do need to remove it. But the right way is with a
fixup! drm/i915/display: Remaining changes to make xe compile

A patch that removes this dsparb_lock from the patch that is now incorrectly
addding it in our xe tree.

> 
> Can you please take a look at the other 5 patches before I send a new version?

I will take a look one by one...

> 
> > 
> > > 
> > > Cc: intel-gfx@lists.freedesktop.org
> > > Signed-off-by: José Roberto de Souza <jose.souza@intel.com>
> > > ---
> > >  drivers/gpu/drm/i915/display/intel_display_core.h | 3 ---
> > >  drivers/gpu/drm/i915/i915_driver.c                | 1 -
> > >  2 files changed, 4 deletions(-)
> > > 
> > > diff --git a/drivers/gpu/drm/i915/display/intel_display_core.h b/drivers/gpu/drm/i915/display/intel_display_core.h
> > > index cc058eb303ee8..d2346d43d1162 100644
> > > --- a/drivers/gpu/drm/i915/display/intel_display_core.h
> > > +++ b/drivers/gpu/drm/i915/display/intel_display_core.h
> > > @@ -266,9 +266,6 @@ struct intel_wm {
> > >  	 */
> > >  	struct mutex wm_mutex;
> > >  
> > > -	/* protects DSPARB registers on pre-g4x/vlv/chv */
> > > -	spinlock_t dsparb_lock;
> > > -
> > >  	bool ipc_enabled;
> > >  };
> > >  
> > > diff --git a/drivers/gpu/drm/i915/i915_driver.c b/drivers/gpu/drm/i915/i915_driver.c
> > > index 066d79c2069c4..ea2cc56d18a6e 100644
> > > --- a/drivers/gpu/drm/i915/i915_driver.c
> > > +++ b/drivers/gpu/drm/i915/i915_driver.c
> > > @@ -214,7 +214,6 @@ static int i915_driver_early_probe(struct drm_i915_private *dev_priv)
> > >  	spin_lock_init(&dev_priv->irq_lock);
> > >  	spin_lock_init(&dev_priv->gpu_error.lock);
> > >  	spin_lock_init(&dev_priv->display.fb_tracking.lock);
> > > -	spin_lock_init(&dev_priv->display.wm.dsparb_lock);
> > >  	mutex_init(&dev_priv->display.backlight.lock);
> > >  
> > >  	mutex_init(&dev_priv->sb_lock);
> > > -- 
> > > 2.40.0
> > > 
> 

  reply	other threads:[~2023-04-10 15:27 UTC|newest]

Thread overview: 42+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-04-06 14:31 [Intel-gfx] [PATCH v2 rebased 1/6] drm/i915: Nuke unused dsparb_lock José Roberto de Souza
2023-04-06 14:31 ` [Intel-xe] " José Roberto de Souza
2023-04-06 14:31 ` [Intel-gfx] [PATCH v2 rebased 2/6] drm/i915: Initialize dkl_phy spin lock from display code path José Roberto de Souza
2023-04-06 14:31   ` [Intel-xe] " José Roberto de Souza
2023-04-10 15:33   ` [Intel-gfx] " Rodrigo Vivi
2023-04-10 15:33     ` [Intel-xe] " Rodrigo Vivi
2023-04-10 17:07     ` Souza, Jose
2023-04-10 17:07       ` [Intel-xe] " Souza, Jose
2023-04-10 17:20       ` [Intel-gfx] [Intel-xe] " Rodrigo Vivi
2023-04-10 17:20         ` [Intel-xe] [Intel-gfx] " Rodrigo Vivi
2023-04-06 14:31 ` [Intel-gfx] [PATCH v2 rebased 3/6] drm/i915: Only initialize dlk phy lock in display 12 and newer José Roberto de Souza
2023-04-06 14:31   ` [Intel-xe] " José Roberto de Souza
2023-04-10 15:37   ` [Intel-gfx] " Rodrigo Vivi
2023-04-10 15:37     ` Rodrigo Vivi
2023-04-10 17:10     ` [Intel-gfx] " Souza, Jose
2023-04-10 17:10       ` Souza, Jose
2023-04-10 17:19       ` [Intel-gfx] " Rodrigo Vivi
2023-04-10 17:19         ` Rodrigo Vivi
2023-04-06 14:31 ` [Intel-xe] [PATCH v2 rebased 4/6] drm/xe/display: Enable modular fia in TGL José Roberto de Souza
2023-04-10 15:38   ` Rodrigo Vivi
2023-04-10 16:24     ` Souza, Jose
2023-04-10 16:50       ` Rodrigo Vivi
2023-04-10 17:15         ` Souza, Jose
2023-04-10 17:20           ` Rodrigo Vivi
2023-04-10 17:29             ` Souza, Jose
2023-04-10 17:30               ` Vivi, Rodrigo
2023-04-06 14:31 ` [Intel-xe] [PATCH v2 rebased 5/6] drm/xe/display: Disable PSR HW tracking for DG2 and MTL José Roberto de Souza
2023-04-10 15:43   ` Rodrigo Vivi
2023-04-06 14:31 ` [Intel-xe] [PATCH v2 rebased 6/6] drm/xe: Enable Raptorlake-P José Roberto de Souza
2023-04-10 15:44   ` Rodrigo Vivi
2023-04-06 14:36 ` [Intel-xe] ✓ CI.Patch_applied: success for series starting with [v2,rebased,1/6] drm/i915: Nuke unused dsparb_lock Patchwork
2023-04-06 14:37 ` [Intel-xe] ✓ CI.KUnit: " Patchwork
2023-04-06 14:41 ` [Intel-xe] ✓ CI.Build: " Patchwork
2023-04-06 20:38 ` [Intel-gfx] [Intel-xe] [PATCH v2 rebased 1/6] " Rodrigo Vivi
2023-04-06 20:38   ` Rodrigo Vivi
2023-04-10 14:43   ` [Intel-gfx] " Souza, Jose
2023-04-10 14:43     ` Souza, Jose
2023-04-10 15:26     ` Rodrigo Vivi [this message]
2023-04-10 15:26       ` Rodrigo Vivi
2023-04-10 15:45       ` [Intel-gfx] " Rodrigo Vivi
2023-04-10 15:45         ` Rodrigo Vivi
2023-04-10 15:46 ` [Intel-xe] ✗ CI.Patch_applied: failure for series starting with [v2,rebased,1/6] drm/i915: Nuke unused dsparb_lock (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=ZDQqwfP+ZcONL2wO@intel.com \
    --to=rodrigo.vivi@intel.com \
    --cc=intel-gfx@lists.freedesktop.org \
    --cc=intel-xe@lists.freedesktop.org \
    --cc=jose.souza@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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.