From: Ville Syrjala <ville.syrjala@linux.intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [Intel-gfx] [PATCH 3/3] drm/i915: Remove dead members from dev_priv
Date: Mon, 21 Mar 2022 21:50:06 +0200 [thread overview]
Message-ID: <20220321195006.775-4-ville.syrjala@linux.intel.com> (raw)
In-Reply-To: <20220321195006.775-1-ville.syrjala@linux.intel.com>
From: Ville Syrjälä <ville.syrjala@linux.intel.com>
Remove some zombies from our device structure.
Signed-off-by: Ville Syrjälä <ville.syrjala@linux.intel.com>
---
drivers/gpu/drm/i915/i915_drv.h | 9 ---------
1 file changed, 9 deletions(-)
diff --git a/drivers/gpu/drm/i915/i915_drv.h b/drivers/gpu/drm/i915/i915_drv.h
index 217c09422711..98f04e0ebdbe 100644
--- a/drivers/gpu/drm/i915/i915_drv.h
+++ b/drivers/gpu/drm/i915/i915_drv.h
@@ -635,12 +635,6 @@ struct drm_i915_private {
struct list_head global_obj_list;
- /*
- * For reading active_pipes holding any crtc lock is
- * sufficient, for writing must hold all of them.
- */
- u8 active_pipes;
-
struct i915_frontbuffer_tracking fb_tracking;
struct intel_atomic_helper {
@@ -670,8 +664,6 @@ struct drm_i915_private {
struct i915_gpu_error gpu_error;
- struct drm_i915_gem_object *vlv_pctx;
-
/* list of fbdev register on this device */
struct intel_fbdev *fbdev;
struct work_struct fbdev_suspend_work;
@@ -692,7 +684,6 @@ struct drm_i915_private {
u32 bxt_phy_grc;
u32 suspend_count;
- bool power_domains_suspended;
struct i915_suspend_saved_registers regfile;
struct vlv_s0ix_state *vlv_s0ix_state;
--
2.34.1
next prev parent reply other threads:[~2022-03-21 19:50 UTC|newest]
Thread overview: 9+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-03-21 19:50 [Intel-gfx] [PATCH 0/3] drm/i915: Random cleanups Ville Syrjala
2022-03-21 19:50 ` [Intel-gfx] [PATCH 1/3] drm/i915: Program i830 DPLL FP register later Ville Syrjala
2022-03-21 19:50 ` [Intel-gfx] [PATCH 2/3] drm/i915: Use drm_connector_attach_hdr_output_metadata_property() Ville Syrjala
2022-03-21 19:50 ` Ville Syrjala [this message]
2022-03-22 0:38 ` [Intel-gfx] ✗ Fi.CI.SPARSE: warning for drm/i915: Random cleanups Patchwork
2022-03-22 0:42 ` [Intel-gfx] ✗ Fi.CI.DOCS: " Patchwork
2022-03-22 1:14 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2022-03-22 13:14 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2022-04-01 12:57 ` [Intel-gfx] [PATCH 0/3] " Jani Nikula
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=20220321195006.775-4-ville.syrjala@linux.intel.com \
--to=ville.syrjala@linux.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