From: Rodrigo Vivi <rodrigo.vivi@intel.com>
To: "José Roberto de Souza" <jose.souza@intel.com>
Cc: intel-gfx@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: Thu, 6 Apr 2023 16:38:20 -0400 [thread overview]
Message-ID: <ZC8tvEoKW425Sbeh@intel.com> (raw)
In-Reply-To: <20230406143133.29474-1-jose.souza@intel.com>
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...
>
> 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
>
next prev parent reply other threads:[~2023-04-06 20:38 UTC|newest]
Thread overview: 13+ 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-gfx] [PATCH v2 rebased 2/6] drm/i915: Initialize dkl_phy spin lock from display code path José Roberto de Souza
2023-04-10 15:33 ` Rodrigo Vivi
2023-04-10 17:07 ` Souza, Jose
2023-04-10 17:20 ` [Intel-gfx] [Intel-xe] " 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-10 15:37 ` [Intel-gfx] [Intel-xe] " Rodrigo Vivi
2023-04-10 17:10 ` Souza, Jose
2023-04-10 17:19 ` Rodrigo Vivi
2023-04-06 20:38 ` Rodrigo Vivi [this message]
2023-04-10 14:43 ` [Intel-gfx] [Intel-xe] [PATCH v2 rebased 1/6] drm/i915: Nuke unused dsparb_lock Souza, Jose
2023-04-10 15:26 ` Rodrigo Vivi
2023-04-10 15:45 ` Rodrigo Vivi
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=ZC8tvEoKW425Sbeh@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 a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox