From: Jani Nikula <jani.nikula@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: ville.syrjala@linux.intel.com, jani.nikula@intel.com
Subject: [PATCH 2/6] drm/intel: group individual funcs in parent interface
Date: Fri, 12 Dec 2025 16:14:05 +0200 [thread overview]
Message-ID: <4305b09a93ce2c8ca83bf1fbb3cc7ef5a29d1567.1765548786.git.jani.nikula@intel.com> (raw)
In-Reply-To: <cover.1765548786.git.jani.nikula@intel.com>
There are a handful of function pointers that don't really warrant a
dedicated sub-struct for the functionality. Group all of them together
in a single anonymous sub-struct.
Signed-off-by: Jani Nikula <jani.nikula@intel.com>
---
'git show -w' is easy to review
---
include/drm/intel/display_parent_interface.h | 19 +++++++++++--------
1 file changed, 11 insertions(+), 8 deletions(-)
diff --git a/include/drm/intel/display_parent_interface.h b/include/drm/intel/display_parent_interface.h
index 87e26ee0ecbf..5d4b9dc837d9 100644
--- a/include/drm/intel/display_parent_interface.h
+++ b/include/drm/intel/display_parent_interface.h
@@ -103,17 +103,20 @@ struct intel_display_parent_interface {
/** @stolen: Stolen memory. */
const struct intel_display_stolen_interface *stolen;
- /** @vgpu_active: Is vGPU active? Optional. */
- bool (*vgpu_active)(struct drm_device *drm);
+ /* Generic independent functions */
+ struct {
+ /** @vgpu_active: Is vGPU active? Optional. */
+ bool (*vgpu_active)(struct drm_device *drm);
- /** @has_fenced_regions: Support legacy fencing? Optional. */
- bool (*has_fenced_regions)(struct drm_device *drm);
+ /** @has_fenced_regions: Support legacy fencing? Optional. */
+ bool (*has_fenced_regions)(struct drm_device *drm);
- /** @fence_priority_display: Set display priority. Optional. */
- void (*fence_priority_display)(struct dma_fence *fence);
+ /** @fence_priority_display: Set display priority. Optional. */
+ void (*fence_priority_display)(struct dma_fence *fence);
- /** @has_auxccs: Are AuxCCS formats supported by the parent. Optional. */
- bool (*has_auxccs)(struct drm_device *drm);
+ /** @has_auxccs: Are AuxCCS formats supported by the parent. Optional. */
+ bool (*has_auxccs)(struct drm_device *drm);
+ };
};
#endif
--
2.47.3
next prev parent reply other threads:[~2025-12-12 14:14 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-12-12 14:14 [PATCH 0/6] drm/{i915,xe}: clean up parent interface definitions Jani Nikula
2025-12-12 14:14 ` [PATCH 1/6] drm/intel: fix parent interface kernel-doc Jani Nikula
2025-12-12 14:14 ` Jani Nikula [this message]
2025-12-12 14:14 ` [PATCH 3/6] drm/intel: sort parent interface struct definitions and members Jani Nikula
2025-12-12 14:14 ` [PATCH 4/6] drm/i915: sort parent interface initialization Jani Nikula
2025-12-12 14:14 ` [PATCH 5/6] drm/xe: " Jani Nikula
2025-12-12 14:14 ` [PATCH 6/6] drm/i915/display: group and sort the parent interface wrappers better Jani Nikula
2025-12-12 14:23 ` ✗ CI.checkpatch: warning for drm/{i915,xe}: clean up parent interface definitions Patchwork
2025-12-12 14:24 ` ✓ CI.KUnit: success " Patchwork
2025-12-12 14:46 ` [PATCH 0/6] " Ville Syrjälä
2025-12-15 12:30 ` Jani Nikula
2025-12-12 14:47 ` ✗ CI.checksparse: warning for " Patchwork
2025-12-12 15:35 ` ✓ Xe.CI.BAT: success " Patchwork
2025-12-13 6:11 ` ✓ Xe.CI.Full: " 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=4305b09a93ce2c8ca83bf1fbb3cc7ef5a29d1567.1765548786.git.jani.nikula@intel.com \
--to=jani.nikula@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--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