From: Nischal Varide <nischal.varide@intel.com>
To: intel-gfx@lists.freedesktop.org, nischal.varide@intel.com,
uma.shankar@intel.com, anshuman.gupta@intel.com
Subject: [Intel-gfx] [RFC 0/1] drm/i915/display: Expose HDMI properties to userspace
Date: Thu, 6 May 2021 06:17:18 +0530 [thread overview]
Message-ID: <20210506004719.4121-1-nischal.varide@intel.com> (raw)
Right now the HDMI properties like vendor and product ids are hardcoded
in the function "intel_hdmi_compute_spd_infoframe()".
ret = hdmi_spd_infoframe_init(frame, "Intel", "Integrated gfx").
This patch enables the possibility of setting vendor and product fields
of the Infoframe structure in the userspace, instead of hardcoding in
the kernel.
The changes has been Tested by an IGT testcase , which will be floated
in few hours
Nischal Varide (1):
drm/i915/display: Expose HDMI properties to userspace
drivers/gpu/drm/i915/display/intel_atomic.c | 14 +++++++++++++
.../gpu/drm/i915/display/intel_connector.c | 20 +++++++++++++++++++
.../gpu/drm/i915/display/intel_connector.h | 1 +
.../drm/i915/display/intel_display_types.h | 5 +++++
drivers/gpu/drm/i915/display/intel_hdmi.c | 14 ++++++++++++-
drivers/gpu/drm/i915/display/intel_hdmi.h | 5 +++++
drivers/gpu/drm/i915/i915_drv.h | 1 +
7 files changed, 59 insertions(+), 1 deletion(-)
--
2.29.2
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next reply other threads:[~2021-05-06 7:39 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-05-06 0:47 Nischal Varide [this message]
2021-05-06 0:47 ` [Intel-gfx] [RFC 1/1] drm/i915/display: Expose HDMI properties to userspace Nischal Varide
2021-05-06 10:13 ` Jani Nikula
2021-05-06 8:26 ` [Intel-gfx] ✗ Fi.CI.CHECKPATCH: warning for " Patchwork
2021-05-06 8:54 ` [Intel-gfx] ✓ Fi.CI.BAT: success " Patchwork
2021-05-06 10:33 ` [Intel-gfx] ✗ Fi.CI.IGT: failure " Patchwork
2021-05-07 6:45 ` [Intel-gfx] [RFC 0/1] " Ville Syrjälä
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=20210506004719.4121-1-nischal.varide@intel.com \
--to=nischal.varide@intel.com \
--cc=anshuman.gupta@intel.com \
--cc=intel-gfx@lists.freedesktop.org \
--cc=uma.shankar@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