From: Marius Vlad <marius.c.vlad@intel.com>
To: intel-gfx@lists.freedesktop.org
Subject: [PATCH v2] drm/i915: Support HDMI EDID injection
Date: Wed, 3 Feb 2016 18:49:09 +0200 [thread overview]
Message-ID: <1454518149-10421-1-git-send-email-marius.c.vlad@intel.com> (raw)
In-Reply-To: <1454418061-10178-1-git-send-email-marius.c.vlad@intel.com>
Make a copy of drm_property_blob data for user-supplied EDID blobs.
v2: Allocate and memcopy drm_property_blob->data instead of pointing
to it.
Signed-off-by: Marius Vlad <marius.c.vlad@intel.com>
---
drivers/gpu/drm/i915/intel_hdmi.c | 10 ++++++++++
1 file changed, 10 insertions(+)
diff --git a/drivers/gpu/drm/i915/intel_hdmi.c b/drivers/gpu/drm/i915/intel_hdmi.c
index 8698a64..4c9bb5f 100644
--- a/drivers/gpu/drm/i915/intel_hdmi.c
+++ b/drivers/gpu/drm/i915/intel_hdmi.c
@@ -1355,6 +1355,16 @@ intel_hdmi_set_edid(struct drm_connector *connector, bool force)
intel_gmbus_get_adapter(dev_priv,
intel_hdmi->ddc_bus));
+ /*
+ * Use the user-supplied EDID blob in case we don't have an
+ * EDID from the display.
+ */
+ if (!edid && connector->override_edid) {
+ edid = kmemdup(connector->edid_blob_ptr->data,
+ connector->edid_blob_ptr->length,
+ GFP_KERNEL);
+ }
+
intel_display_power_put(dev_priv, POWER_DOMAIN_GMBUS);
}
--
2.7.0
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
http://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2016-02-03 16:47 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2016-02-02 13:01 [PATCH] drm/i915: Support HDMI EDID injection Marius Vlad
2016-02-02 13:18 ` ✓ Fi.CI.BAT: success for " Patchwork
2016-02-02 15:32 ` [PATCH] " Jani Nikula
2016-02-02 16:00 ` Marius Vlad
2016-02-03 16:49 ` Marius Vlad [this message]
2016-02-03 17:15 ` ✗ Fi.CI.BAT: warning for drm/i915: Support HDMI EDID injection (rev2) 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=1454518149-10421-1-git-send-email-marius.c.vlad@intel.com \
--to=marius.c.vlad@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;
as well as URLs for NNTP newsgroup(s).