From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: Andrzej Hajda <a.hajda@samsung.com>,
dri-devel@lists.freedesktop.org,
Intel Graphics Development <intel-gfx@lists.freedesktop.org>
Cc: Jose Abreu <Jose.Abreu@synopsys.com>,
daniel.vetter@intel.com, Alex Deucher <alexander.deucher@amd.com>
Subject: Re: [PATCH v3] drm/edid: Complete CEA modedb(VIC 1-107)
Date: Mon, 30 Jan 2017 16:59:55 +0530 [thread overview]
Message-ID: <1f1e9fd2-fff9-0ce3-11bb-15e59299dc04@intel.com> (raw)
In-Reply-To: <ec372709-ca1e-4382-bb1e-19da4e823d83@samsung.com>
I just realized that the CEA spec talks about picking HDMI 2.0/861-F VIC
over HDMI14b VIC in case of 3D side-by-side format (not in 2D),
In this case, we might have to add a check while loading the VIC filed
in AVI IF (as you suggested)
Will come back with a V2 (if required), once I have more information on
this.
>>> For example 3840x2160@30Hz has no VIC in HDMI 1.4 but it can
>>> be present in HDMI vendor specific block with HDMI_VIC 1, on the
>>> other side it has VIC 95 in HDMI 2.0. So before your patch
>>> AVI infoframe.video_code is set to 0, after your patch is set to 95.
>>>
>>>
Regards
Shashank
_______________________________________________
dri-devel mailing list
dri-devel@lists.freedesktop.org
https://lists.freedesktop.org/mailman/listinfo/dri-devel
next prev parent reply other threads:[~2017-01-30 11:29 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
[not found] <CGME20170129052952epcas1p241f5ad9f0396def0e260c5bad44cce27@epcas1p2.samsung.com>
2017-01-29 5:41 ` [PATCH v3] drm/edid: Complete CEA modedb(VIC 1-107) Shashank Sharma
2017-01-30 8:00 ` Andrzej Hajda
2017-01-30 8:45 ` Sharma, Shashank
2017-01-30 8:46 ` Sharma, Shashank
2017-01-30 9:22 ` Andrzej Hajda
2017-01-30 9:42 ` Sharma, Shashank
2017-01-30 10:17 ` Andrzej Hajda
2017-01-30 11:01 ` Sharma, Shashank
2017-01-30 11:29 ` Sharma, Shashank [this message]
2017-01-30 20:43 ` Harry Wentland
2017-01-31 14:52 ` [gfx-internal-devel] " 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=1f1e9fd2-fff9-0ce3-11bb-15e59299dc04@intel.com \
--to=shashank.sharma@intel.com \
--cc=Jose.Abreu@synopsys.com \
--cc=a.hajda@samsung.com \
--cc=alexander.deucher@amd.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--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 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.