From: Shashank Sharma <shashank.sharma@intel.com>
To: dri-devel@lists.freedesktop.org, intel-gfx@lists.freedesktop.org,
ville.syrjala@linux.intel.com,
ander.conselvan.de.oliveira@intel.com
Cc: jose.abreu@synopsys.com, daniel.vetter@intel.com, treding@nvidia.com
Subject: [PATCH v5 2/6] drm/edid: check for HF-VSDB block
Date: Tue, 28 Feb 2017 14:09:06 +0530 [thread overview]
Message-ID: <1488271150-7423-3-git-send-email-shashank.sharma@intel.com> (raw)
In-Reply-To: <1488271150-7423-1-git-send-email-shashank.sharma@intel.com>
From: Thierry Reding <treding@nvidia.com>
This patch implements a small function that finds if a
given CEA db is hdmi-forum vendor specific data block
or not.
V2: Rebase.
V3: Added R-B from Jose.
V4: Rebase
V5: Rebase
Signed-off-by: Thierry Reding <treding@nvidia.com>
Signed-off-by: Shashank Sharma <shashank.sharma@intel.com>
Reviewed-by: Jose Abreu <joabreu@synopsys.com>
---
drivers/gpu/drm/drm_edid.c | 15 +++++++++++++++
include/linux/hdmi.h | 1 +
2 files changed, 16 insertions(+)
diff --git a/drivers/gpu/drm/drm_edid.c b/drivers/gpu/drm/drm_edid.c
index e1743ab..055b511 100644
--- a/drivers/gpu/drm/drm_edid.c
+++ b/drivers/gpu/drm/drm_edid.c
@@ -3248,6 +3248,21 @@ static bool cea_db_is_hdmi_vsdb(const u8 *db)
return hdmi_id == HDMI_IEEE_OUI;
}
+static bool cea_db_is_hdmi_forum_vsdb(const u8 *db)
+{
+ unsigned int oui;
+
+ if (cea_db_tag(db) != VENDOR_BLOCK)
+ return false;
+
+ if (cea_db_payload_len(db) < 7)
+ return false;
+
+ oui = db[3] << 16 | db[2] << 8 | db[1];
+
+ return oui == HDMI_FORUM_IEEE_OUI;
+}
+
#define for_each_cea_db(cea, i, start, end) \
for ((i) = (start); (i) < (end) && (i) + cea_db_payload_len(&(cea)[(i)]) < (end); (i) += cea_db_payload_len(&(cea)[(i)]) + 1)
diff --git a/include/linux/hdmi.h b/include/linux/hdmi.h
index edbb4fc..d271ff2 100644
--- a/include/linux/hdmi.h
+++ b/include/linux/hdmi.h
@@ -35,6 +35,7 @@ enum hdmi_infoframe_type {
};
#define HDMI_IEEE_OUI 0x000c03
+#define HDMI_FORUM_IEEE_OUI 0xc45dd8
#define HDMI_INFOFRAME_HEADER_SIZE 4
#define HDMI_AVI_INFOFRAME_SIZE 13
#define HDMI_SPD_INFOFRAME_SIZE 25
--
1.9.1
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-02-28 8:39 UTC|newest]
Thread overview: 13+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-02-28 8:39 [PATCH v5 0/6] HDMI 2.0: Scrambling in DRM layer Shashank Sharma
2017-02-28 8:39 ` [PATCH v5 1/6] drm: Add SCDC helpers Shashank Sharma
2017-02-28 8:39 ` Shashank Sharma [this message]
2017-02-28 8:39 ` [PATCH v5 3/6] drm/edid: detect SCDC support in HF-VSDB Shashank Sharma
2017-02-28 8:39 ` [PATCH v5 4/6] " Shashank Sharma
2017-03-01 14:58 ` Ville Syrjälä
2017-03-02 2:37 ` Sharma, Shashank
2017-02-28 8:39 ` [PATCH v5 5/6] drm/i915: enable scrambling Shashank Sharma
2017-03-01 15:11 ` Ville Syrjälä
2017-03-02 2:55 ` Sharma, Shashank
2017-03-03 9:50 ` Ander Conselvan De Oliveira
2017-02-28 8:39 ` [PATCH v5 6/6] drm/i915: allow HDMI 2.0 clock rates Shashank Sharma
2017-02-28 8:53 ` ✓ Fi.CI.BAT: success for HDMI 2.0: Scrambling in DRM layer (rev5) 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=1488271150-7423-3-git-send-email-shashank.sharma@intel.com \
--to=shashank.sharma@intel.com \
--cc=ander.conselvan.de.oliveira@intel.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--cc=jose.abreu@synopsys.com \
--cc=treding@nvidia.com \
--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;
as well as URLs for NNTP newsgroup(s).