From: Pranay Samala <pranay.samala@intel.com>
To: intel-gfx@lists.freedesktop.org, intel-xe@lists.freedesktop.org,
dri-devel@lists.freedesktop.org
Cc: chaitanya.kumar.borah@intel.com, sameer.lattannavar@intel.com,
pranay.samala@intel.com
Subject: [PATCH v2 0/2] Expose HDR status in debugfs
Date: Tue, 6 Oct 2026 11:10:02 +0530 [thread overview]
Message-ID: <20261006054004.285744-1-pranay.samala@intel.com> (raw)
i915_display_info currently doesn't show whether HDR is active on a
connector. This series adds per-connector HDR details in three parts:
sink capability (from the EDID), whether userspace has set
HDR_OUTPUT_METADATA, and whether the driver has actually enabled HDR
output.
Patch 1 adds a small hdmi_eotf_get_name() helper to video/hdmi so the
EOTF can be printed by name. Patch 2 adds the debugfs output.
v2:
- Move the EOTF name helper to the common hdmi code (Jani)
- Use drm_printer for indentation instead of manual tabs (Jani)
- Treat any non-SDR EOTF as HDR capable
- Print the EDID luminance only when present, in nits
- Add units to the HDR output luminance values
Pranay Samala (2):
video/hdmi: Add hdmi_eotf_get_name()
drm/i915/debugfs: Add HDR status to i915_display_info
.../drm/i915/display/intel_display_debugfs.c | 90 +++++++++++++++++++
drivers/video/hdmi.c | 23 +++++
include/linux/hdmi.h | 2 +
3 files changed, 115 insertions(+)
--
2.53.0
next reply other threads:[~2026-10-06 5:40 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-10-06 5:40 Pranay Samala [this message]
2026-10-06 5:40 ` [PATCH v2 1/2] video/hdmi: Add hdmi_eotf_get_name() Pranay Samala
2026-10-06 5:48 ` sashiko-bot
2026-10-06 5:40 ` [PATCH v2 2/2] drm/i915/debugfs: Add HDR status to i915_display_info Pranay Samala
2026-10-06 5:48 ` ✓ CI.KUnit: success for Expose HDR status in debugfs Patchwork
2026-10-06 6:29 ` ✓ Xe.CI.BAT: " Patchwork
2026-10-06 15:01 ` ✓ 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=20261006054004.285744-1-pranay.samala@intel.com \
--to=pranay.samala@intel.com \
--cc=chaitanya.kumar.borah@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=intel-xe@lists.freedesktop.org \
--cc=sameer.lattannavar@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