From: "Sharma, Shashank" <shashank.sharma@intel.com>
To: "Jose Abreu" <Jose.Abreu@synopsys.com>,
"Ville Syrjälä" <ville.syrjala@linux.intel.com>
Cc: Alex Deucher <alexander.deucher@amd.com>,
intel-gfx@lists.freedesktop.org, dri-devel@lists.freedesktop.org,
Daniel Vetter <daniel.vetter@intel.com>
Subject: Re: [PATCH v4 2/2] drm: Add HDMI 2.0 VIC support for AVI info-frames
Date: Thu, 23 Mar 2017 18:31:33 +0200 [thread overview]
Message-ID: <1c193ff8-b31b-d8c1-1023-ca5340287d5c@intel.com> (raw)
In-Reply-To: <54d9915e-eace-15a0-a37c-ccc4f76654d6@synopsys.com>
Regards
Shashank
On 3/23/2017 5:52 PM, Jose Abreu wrote:
> Hi Ville,
>
>
> On 23-03-2017 15:36, Ville Syrjälä wrote:
>> On Thu, Mar 23, 2017 at 05:14:19PM +0200, Shashank Sharma wrote:
>>> HDMI 1.4b support the CEA video modes as per range of CEA-861-D (VIC 1-64).
>>> For any other mode, the VIC filed in AVI infoframes should be 0.
>>> HDMI 2.0 sinks, support video modes range as per CEA-861-F spec, which is
>>> extended to (VIC 1-107).
>>>
>>> This patch adds a bool input variable, which indicates if the connected
>>> sink is a HDMI 2.0 sink or not. This will make sure that we don't pass a
>>> HDMI 2.0 VIC to a HDMI 1.4 sink.
>> The spec is unfortunately vague when it comes to the CEA-861-F VIC
>> transmission when there is a corresponding HDMI VIC for the same mode.
>> I'm not sure if it's telling us to set both or just one depending on
>> whether we're transmitting 3D video or not. Or at least I can't parse
>> that information from the spec. Anyone have a better crystal ball
>> in their possession?
>>
> I've been working in HDMI receivers and this is what I've got in
> a comment:
>
> 1282
> /*
>
> 1283 * Update current VIC: When transmitting any
> extended video format
> 1284 * indicated through use of the HDMI_VIC field in
> the HDMI Vendor
> 1285 * Specific InfoFrame or any other format which is
> not described in
> 1286 * the above cases, an HDMI Source shall set the AVI
> InfoFrame VIC
> 1287 * field to
> zero.
>
> 1288 */
>
> This was directly taken from the spec, can't remember exactly
> were though.
>
> So, the VIC in AVIIF must be set to 0 and the HDMI_VIC field in
> VSIF shall be set to the HDMI 4k VIC.
>
> Best regards,
> Jose Miguel Abreu
Even my understanding of the two specs seems similar
If its a HDMI 1.4b monitor, 2D mode
- VIC field in AVI_IF should be set to appropriate VIC [if VIC is
not listed in CEA-861-D (VIC 1-64), make VIC=0]
If its a HDMI 1.4b monitor, 3D mode
- VIC field in AVI_IF should be set to appropriate VIC, in
conjunction with 3D_structure field in HDMI VSIF
If its a HDMI 2.0 monitor, 2D mode
- VIC filed in the AVI_IF should be set to appropriate VIC (1-107)
If its a HDMI 2.0 monitor, 3D mode
- VIC field in AVI_IF should be set to appropriate VIC, in
conjunction with 3D_structure field in HDMI VSIF
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-03-23 16:31 UTC|newest]
Thread overview: 21+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-23 15:14 [PATCH v4 1/2] drm/edid: Complete CEA modedb(VIC 1-107) Shashank Sharma
2017-03-23 15:14 ` [PATCH v4 2/2] drm: Add HDMI 2.0 VIC support for AVI info-frames Shashank Sharma
2017-03-23 15:17 ` Ilia Mirkin
2017-03-23 15:22 ` Sharma, Shashank
2017-03-23 15:28 ` Ilia Mirkin
2017-03-23 16:33 ` Sharma, Shashank
2017-03-23 15:28 ` Jose Abreu
2017-03-23 15:45 ` Ville Syrjälä
2017-03-23 15:57 ` Jose Abreu
2017-03-23 16:08 ` Sharma, Shashank
2017-03-23 16:33 ` Jose Abreu
2017-03-23 16:43 ` Sharma, Shashank
2017-03-23 17:11 ` Jose Abreu
2017-03-23 17:42 ` Ville Syrjälä
2017-03-23 17:53 ` Jose Abreu
2017-03-23 18:14 ` Ville Syrjälä
2017-03-23 18:35 ` Jose Abreu
2017-03-23 15:36 ` Ville Syrjälä
2017-03-23 15:52 ` Jose Abreu
2017-03-23 16:31 ` Sharma, Shashank [this message]
2017-03-23 17:01 ` 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=1c193ff8-b31b-d8c1-1023-ca5340287d5c@intel.com \
--to=shashank.sharma@intel.com \
--cc=Jose.Abreu@synopsys.com \
--cc=alexander.deucher@amd.com \
--cc=daniel.vetter@intel.com \
--cc=dri-devel@lists.freedesktop.org \
--cc=intel-gfx@lists.freedesktop.org \
--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