Versions Compared


  • This line was added.
  • This line was removed.
  • Formatting was changed.


Table of Contents


The Xilinx UHD SDI Rx Subsystem consists of UHD SDI Rx IP core, an SDI to native video bridge followed by a Native to AXI-4 S bridge. It is capable of detecting the SD, HD, 3GA, 3GB, 6G and 12G (upto 8 data streams) type SDI streams. The maximum resolution it supports is 4096x2160p60 in 12G mode. The SDI Rx IP allows the configuration of the modes to be detected at run time or a fixed mode. It also allows the Framer to be enabled. A video lock event is generated when the incoming SDI mode and transport stream is detected and is stable for a configurable number of video clocks as programmed in the Video Lockout Window. When the input video stream is stopped or the type changed, a video unlock event is generated. The IP gives out the CRC and EDH error status. When the bridges are enabled, then the AXI-4 Stream of YUV 422 10 bit per component and 2 pixels per clock is sent out.

The SDI Rx Subsystem driver (xilinx-sdirxss.c) is based on the V4L2 framework.
It creates a subdev node(/dev/v4l-subdev*) which can be used to query and configure the UHD SDI Rx Subsystem IP.
The SDI Rx IP would be the first node in the video capture pipeline.
It exposes various V4L controls which can be used to configure the subsystem like auto detection of SDI modes, Framer enable, etc and query the status like CRC status, EDH errors, etc.
It also exposes certain V4L events like video unlock, bridge overflow/underflow, video source change, etc which can be used by application to trigger certain actions.
The general description of V4L2 framework is documented here, v4l2-framework.txt.

IP/Driver Features

IP feature2018.1 on wards2019.22020.12020.22021.12021.2
IP version2.0
Supports AXI4-Stream, native video and native SDI user interfacesSupports only AXI4-Stream output interface
Support for 2 pixel per sampleYes
10-bit per color componentYesAdded support for 12 bit
Supports YUV 4:2:2 and YUV 4:2:0 color spaceYes

Added support for YUV444 in IP.

Driver doesn't support

Supports YUV 420 / 422 / 444 and RGB

HFR (High Frame Rate) Support 96/1.001, 96, 100, 120/1.001 and 120 HzNANot supported in driverSupported
AXI4-Lite interface for register access to configure different subsystem optionsYes
Audio supportSeparate driver
Standards compliance
  • SMPTE ST 259: SD-SDI at 270 Mb/s.
  • SMPTE RP 165: EDH for SD-SDI.
  • SMPTE ST 292: HD-SDI at 1.485 Gb/s and 1.485/1.001 Gb/s.
  • SMPTE ST 372: Dual Link HD-SDI.
  • SMPTE ST 424: 3G-SDI with data mapped by any ST 425-x mapping at 2.97 Gb/s and 2.97/1.001 Gb/s.
  • SMPTE ST 2081-1: 6G-SDI with data mapped by any ST 2081-x mapping at 5.94 Gb/s and 5.94/1.001 Gb/s.
  • SMPTE ST 2082-1: 12G-SDI with data mapped by any ST 2082-x mapping at 11.88 Gb/s and 11.88/1.001 Gb/s.
  • Dual link and quad link 6G-SDI and 12G-SDI are supported by instantiating two or four UHD-SDI Receiver subsystems.
  • SMPTE ST 352: Payload ID packets are fully supported.
HLG supportN.ASupported

Other driver features supported are -

  • Detect SD, HD, 3GA/3GB, 6G, 12G (upto 8 Data Streams)
  • Auto detect multiple modes OR Fixed Mode detection
  • Framer enable/disable
  • Programmable Video Lock Window
  • EDH & CRC error counters
  • Video Lock, Unlock, Bridge Over/UnderFlow interrupts
  • Separate bits to control SDI to Native and Native to AXI4-S bridge
  • ST352 Payload
  • Mode and Transport type detection
    • Fractional / Integral Frame rate
    • Interlaced / Progressive Transport
    • Family detection

Missing Features / Known Issues / Limitations in Driver

  • In case of a HD stream without payload, a progressive segmented frame (pSF) will be reported incorrectly as Interlaced as the driver relies on the IP's transport scan locked bit.
  • *Multiple instances capability not tested
  • *Tested with only 12G 8DS configuration
  • HD 1280x720p24 and HD 1280x720p23.98 - Incorrect colors are captured
  • In some 3GB 1080 modes, the colors in color bars are swapped.
  • Tested with Phabrix SDI generator and Omnitek Ultra4K
  • Doesn't support to YUV444 in 2019.2

Kernel Configuration


Device Tree Binding

The dts node should be defined with correct hardware configuration. How to define the node is documented in xlnx,sdirxss.txt

Test Procedure

The driver has been tested using the YAVTA tool.

Certain parameters like Framer enable, Video lockout window, etc can be configured using the YAVTA tool as follows -
For example, to list all the controls and current values
Code Block
yavta -l /dev/v4l-subdev0

#Below is sample output when video is not locked and not streaming
root@zcu106-zynqmp:~# yavta -l /dev/v4l-subdev0
Device /dev/v4l-subdev0 opened.
--- User Controls (class 0x00980001) ---
control 0x0098ca01 `SDI Rx : Enable Framer' min 0 max 1 step 1 default 1 current 1.
control 0x0098ca02 `SDI Rx : Video Lock Window' min 0 max -1 step 1 default 12288 current 12288.
control 0x0098ca03 `SDI Rx : EDH Error Count Enable' min 0 max 65535 step 0 default 0 current 0.
control 0x0098ca04 `SDI Rx : Modes search Mask' min 0 max 63 step 0 default 63 current 63.
unable to get control 0x0098ca05: Invalid argument (22).
control 0x0098ca05 `SDI Rx : Mode Detect Status' min 0 max 5 step 1 default 0 current n/a.
control 0x0098ca06 `SDI Rx : CRC Error status' min 0 max -1 step 1 default 0 current 0.
unable to get control 0x0098ca07: Invalid argument (22).
control 0x0098ca07 `SDI Rx : EDH Error Count' min 0 max 65535 step 1 default 0 current n/a.
unable to get control 0x0098ca08: Invalid argument (22).
control 0x0098ca08 `SDI Rx : EDH Status' min 0 max -1 step 1 default 0 current n/a.
unable to get control 0x0098ca09: Invalid argument (22).
control 0x0098ca09 `SDI Rx : TS is Interlaced' min 0 max 1 step 1 default 0 current n/a.
unable to get control 0x0098ca0a: Invalid argument (22).
control 0x0098ca0a `SDI Rx : Active Streams' min 1 max 16 step 1 default 1 current n/a.
unable to get control 0x0098ca0b: Invalid argument (22).
control 0x0098ca0b `SDI Rx : Is 3GB' min 0 max 1 step 1 default 0 current n/a.
11 controls found.
Unable to get format: Inappropriate ioctl for device (25).



Q1 - While running yavta for resolution AxB with our source box, we see "Unable to start streaming: Invalid argument (22)." Why is this happening?

Ans - One possible reason is that the resolution that the SDI source is generating and what is being passed to yavta don't match.

Run media-ctl to find out the resolution currently being identified by the SDI Rx IP driver.

Read your SDI source documentation to know how to manipulate the resolutions.

Q2 - The frame rate reported by yavta is significantly lesser than expected.

Ans - Depending on your design and system load, there may be a case where there may be frame drops.

But double check the ST352 payload in SDI Rx to verify if the SDI source connected is correctly generating the required frame rate (fps).

You may have to refer to PG205 to decode the RX FAMILY to get the resolution and RX Frame Rate (in case of zero payload in 2017.3/4)

Family Detection

rx_t_familyTransport Video FormatActive Pixels
0000SMPTE ST 2751920 x 1080
0001SMPTE ST 2961280 x 720
0010SMPTE ST 2048-22048x1080
0011SMPTE ST 2951920 x 1080
1000NTSC720 x 486
1001PAL720 x 576

Frame Rate

rx_t_rateFrame Rate
001023.98 Hz
001124 Hz
010047.95 Hz
010125 Hz
011029.97 Hz
011130 Hz
100048 Hz
100150 Hz
101059.94 Hz
101160 Hz

Q3 - After boot up, even though there is valid SDI source connected, the IP is unable to detect the source and video is not locked. Why could this happen?

Ans - Check if the IP's registers are not default values after kernel boots up. E.g. MODULE_CTRL register should be 0x3F30. If the registers are in default state, it may mean the clocking to the IP is not correct. Please check device tree to set the correct clock source.

Boards Supported

Driver has been tested on the following boards
  1. ZCU106 1.0

Known Issues

  • AR68766 - SMPTE UHD-SDI RX Subsystem - Release Notes and Known Issues for the Vivado 2017.3 tool and later versions

Change log



  • Summary
    • No change




  • Summary
    • Fixed driver based on comments received while upstreaming like enumerating media bus formats.
    • Fixed interrupt handling for combined lock/unlock interrupts and correctly clearing processed interrupts
  • Commits
    • 3de732f v4l: xilinx: sdirxss: Uninitialize the subsystem correctly

    • 23b13a3 v4l: xilinx: sdirxss: Check for 10bpc in dt

    • df18806 v4l: xilinx: sdirxss: Call xsdirx_streamflow_control() directly

    • 1df1d9f v4l: xilinx: sdirxss: Make functions static inline

    • 75b9c47 v4l: xilinx: sdirxss: Fix code formatting and comments

    • 4414443 v4l: xilinx: sdirxss: Correct handling of combined lock/unlock interrupts

    • 784427f v4l: xilinx: sdirxss: Clear processed interrupts only

    • 1c98050 v4l: xilinx: sdirxss: Add support to enumerate media bus formats

    • b1b4c50 v4l: xilinx: sdirxss: Replace single element array with variable

    • f3bd12b v4l: xilinx: sdirxss: Use clk_bulk_* apis

    • b996133 v4l: xilinx: sdirxss: Make structures constant