From: Shashank Sharma <shashank.sharma@intel.com>
To: ville.syrjala@linux.intel.com, ander.conselvan.de.oliveira@intel.com
Cc: daniel.vetter@intel.com, intel-gfx@lists.freedesktop.org,
Thierry Reding <treding@nvidia.com>,
dri-devel@lists.freedesktop.org
Subject: [PATCH v10 2/6] drm/edid: check for HF-VSDB block
Date: Mon, 13 Mar 2017 16:54:00 +0530 [thread overview]
Message-ID: <1489404244-16608-3-git-send-email-shashank.sharma@intel.com> (raw)
In-Reply-To: <1489404244-16608-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
V6: Rebase
V7: Rebase
V8: Rebase
V9: Rebase
V10: 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 5da5a85..3e0aafa 100644
--- a/drivers/gpu/drm/drm_edid.c
+++ b/drivers/gpu/drm/drm_edid.c
@@ -3251,6 +3251,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
_______________________________________________
Intel-gfx mailing list
Intel-gfx@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/intel-gfx
next prev parent reply other threads:[~2017-03-13 11:24 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-13 11:23 [PATCH v10 0/6] HDMI 2.0: Scrambling in DRM layer Shashank Sharma
2017-03-13 11:23 ` [PATCH v10 1/6] drm: Add SCDC helpers Shashank Sharma
2017-03-13 11:24 ` Shashank Sharma [this message]
2017-03-13 11:24 ` [PATCH v10 3/6] drm/edid: detect SCDC support in HF-VSDB Shashank Sharma
2017-03-24 19:08 ` [Intel-gfx] " Daniel Vetter
2017-03-25 9:23 ` Sharma, Shashank
2017-03-25 9:35 ` Sharma, Shashank
2017-03-13 11:24 ` [PATCH v10 4/6] " Shashank Sharma
2017-03-13 11:24 ` [PATCH v10 5/6] drm/i915: enable scrambling Shashank Sharma
2017-03-14 13:39 ` [Intel-gfx] " Ander Conselvan De Oliveira
2017-03-13 11:24 ` [PATCH v10 6/6] drm/i915: allow HDMI 2.0 clock rates Shashank Sharma
2017-03-13 12:17 ` ✓ Fi.CI.BAT: success for HDMI 2.0: Scrambling in DRM layer (rev10) 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=1489404244-16608-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=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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.