From: "Michał Grzelak" <michal.grzelak@linux.intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org
Cc: "Michał Grzelak" <michal.grzelak@linux.intel.com>
Subject: [PATCH v4 5/5] drm/i915/display: log eDP TC support and DBuf overlap detection state
Date: Tue, 13 Oct 2026 22:47:04 +0200 [thread overview]
Message-ID: <20261013204705.1574475-6-michal.grzelak@linux.intel.com> (raw)
In-Reply-To: <20261013204705.1574475-1-michal.grzelak@linux.intel.com>
edp_tc_support and dbuf_overlap_detection are only fields of display's
runtime info which state is not logged. Show it along other fields.
While at it, move dbuf_overlap_detection to have display runtime info's
fields in alphabetical order.
Signed-off-by: Michał Grzelak <michal.grzelak@linux.intel.com>
---
drivers/gpu/drm/i915/display/intel_display_device.c | 3 +++
drivers/gpu/drm/i915/display/intel_display_device.h | 2 +-
2 files changed, 4 insertions(+), 1 deletion(-)
diff --git a/drivers/gpu/drm/i915/display/intel_display_device.c b/drivers/gpu/drm/i915/display/intel_display_device.c
index d4e52e627b34..c806e2135620 100644
--- a/drivers/gpu/drm/i915/display/intel_display_device.c
+++ b/drivers/gpu/drm/i915/display/intel_display_device.c
@@ -2005,6 +2005,9 @@ void intel_display_device_info_print(const struct intel_display_device_info *inf
DEV_INFO_DISPLAY_FOR_EACH_FLAG(PRINT_FLAG);
#undef PRINT_FLAG
+ drm_printf(p, "edp_typec_support: %s\n", str_yes_no(runtime->edp_typec_support));
+ drm_printf(p, "has_dbuf_overlap_detection: %s\n", str_yes_no(runtime->has_dbuf_overlap_detection));
+
drm_printf(p, "has_3dlut: %s\n", str_yes_no(runtime->has_3dlut));
drm_printf(p, "has_hdcp: %s\n", str_yes_no(runtime->has_hdcp));
drm_printf(p, "has_dmc: %s\n", str_yes_no(runtime->has_dmc));
diff --git a/drivers/gpu/drm/i915/display/intel_display_device.h b/drivers/gpu/drm/i915/display/intel_display_device.h
index 5300c6ab99e7..230eec31f654 100644
--- a/drivers/gpu/drm/i915/display/intel_display_device.h
+++ b/drivers/gpu/drm/i915/display/intel_display_device.h
@@ -307,10 +307,10 @@ struct intel_display_runtime_info {
bool has_3dlut;
bool has_hdcp;
+ bool has_dbuf_overlap_detection;
bool has_dmc;
bool has_dsc;
bool edp_typec_support;
- bool has_dbuf_overlap_detection;
};
struct intel_display_device_info {
--
2.45.2
next prev parent reply other threads:[~2026-10-13 20:48 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-13 20:46 [PATCH v4 0/5] SKL_DSSM / DE_CAP cleanup Michał Grzelak
2026-10-13 20:47 ` [PATCH v4 1/5] drm/i915/display: clean SKL_DSSM register macros Michał Grzelak
2026-10-13 20:47 ` [PATCH v4 2/5] drm/i915/3dlut: disable 3D LUT for pre-GLK Michał Grzelak
2026-10-13 20:59 ` sashiko-bot
2026-10-13 20:47 ` [PATCH v4 3/5] drm/i915/3dlut: log 3D LUT's status Michał Grzelak
2026-10-13 20:47 ` [PATCH v4 4/5] drm/i915/3dlut: disable 3D LUT if unsupported Michał Grzelak
2026-10-13 20:47 ` Michał Grzelak [this message]
2026-10-13 20:53 ` [PATCH v4 5/5] drm/i915/display: log eDP TC support and DBuf overlap detection state sashiko-bot
2026-10-13 21:24 ` ✗ CI.checkpatch: warning for SKL_DSSM / DE_CAP cleanup Patchwork
2026-10-13 21:26 ` ✓ CI.KUnit: success " Patchwork
2026-10-14 2:57 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-14 13:16 ` ✗ Xe.CI.FULL: failure " 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=20261013204705.1574475-6-michal.grzelak@linux.intel.com \
--to=michal.grzelak@linux.intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@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