11-19-2020 02:28 AM
Maybe somebody can help me to clearify a question regarding the HDMI2.0 Tx Subsystem form Xilinx.
The HDMI example design from Xilinx supports CEA-conform output timings, which are defined by a VIC (Video Identifier Code).
Does the HDMI2.0 Tx Subsysten also support custom timings, which are not supported by the CEA?
For example, if I would like to output a 1920x2160@60Hz timing over HDMI, would this be possible to achieve this ?
If so, what do I have to do to achieve this?
11-19-2020 08:01 PM
11-23-2020 04:54 AM
Okay can you explain how to do it?
> Would you refer VESA CVT to decide video timing ?
I want to use a custom timing => Not Vesa CVT compliant...
11-23-2020 01:24 PM
11-24-2020 12:19 AM
It is not of interrest if it is a VESA CVT or a CEA timing !
I need the information how to apply a custom timing by using the HDMI Tx Subsystem !
11-24-2020 04:37 AM
thank you for this information. AR #68227 is more or less describing what I'm looking for.
If I understand it correct, you have to add a custom timing before you compile the code. But I'm looking for a way to programm a custom timing during runtime, while the custom timing is not known at compile time. I get the timing information during runtime. So I cannot add the timing to teh timing table as described in AR #668227. Is this also anyhow supported?
11-24-2020 05:08 AM - edited 11-24-2020 07:28 AM
I think the main problem to achieve this is the following call:
XV_HdmiTxSs_SetStream(&HdmiTxSs, XVIDC_VM_3840x2160_60_P, XVIDC_CSF_RGB, XVIDC_BPC_8, NULL);
The function above contains the video mode parameter XVIDC_VM_3840x2160_60_P, which is used to point to the corrsponding entry in the timing table.
If I only get the timing information during runtime, and if i want to program this timing during runtime, I cannot use the function above.
When I go deeper in the driver function XV_HdmiTxSs_SetStream(), I will find the following code:
If I'm correct, the TimingPtr points to the timing information in the timing table. If so, I could manipulate the TimingPtr, so that it is pointing to a variable of type XVidC_VideoTiming, which could contain a custom timing, and which could be loaded upfront. But this requires a change in the driver file...
Is there a better way to do it?
11-24-2020 05:15 AM - edited 11-24-2020 07:29 AM
there is maybe a better way to do it. If it would be possible to manipulate the timing table below during runtime, it could be achieved, wihtout chaning the driver files...
but the structure is defined as const. I'm not sure if I can change it...