Versions Compared

Old Version 11

changes.mady.by.user Vishal Sagar

Saved on

compared with

New Version 12

changes.mady.by.user Vishal Sagar

Saved on

Key

  • This line was added.
  • This line was removed.
  • Formatting was changed.
Comment: Updated for 2020.2

Table of Contents

Table of Contents
maxLevel1

Introduction

The Xilinx® Video PHY Controller LogiCORE™ IP core is designed for enabling plug-and-play connectivity with Video (DisplayPort and HDMI® technology) MAC Transmit or Receive subsystems. VideoPhy driver supports only HDMI protocol as of now. 
The interface between the video MAC and PHY layers are standardized to enable ease of use in accessing shared transceiver resources. The AXI4-Lite register interface is provided to enable dynamic accesses of transceiver controls/status


Video IP Layer

Driver Overview

The PHY is intended to simplify the use of serial transceivers and adds domain-specific configurability. The Video PHY Controller IP/Driver is not intended to be used as a stand alone IP and must be used with Xilinx Video MACs such as HDMI 1.4/2.0 Transmitter/Receiver Subsystems and DisplayPort TX/RX Subsystems.

As such PHY Linux Driver is implemented within the kernel PHY framework and is tightly coupled with HDMI Rx/Tx Linux drivers. This driver also hosts the common video files shared between the 3 Xilinx connectivity drivers (Vphy, HDMI Rx and HDMI Tx) and exports the relevant API’s for inter-driver communication. On kernel boot-up both HDMI Rx & Tx drivers will request 3 PHY lanes each for Rx & Tx and will defer until PNY driver has been initialized.

IP/Driver Features



IP Feature 2018.1 - 2019.1 2019.2 and onward
IP Version Supported2.22.2

AXI4-Lite support for register accesses

YY

Protocol Support: Display Port, HDMI

Only HDMIOnly HDMI

Full transceiver dynamic reconfiguration port (DRP) accesses and transceiver functions

YY

Independent TX and RX path line rates (device specific)

YY

Single quad support

YY

Phase-locked loop (PLL) switching support from software

YY

Transmit and Receiver user clocking

YY

Protocol specific functions (For example, HDMI Clock Detector)

Y

Y

Non-integer data recovery unit (NI-DRU) support for lower line rates. NI-DRU support is for the HDMI protocol only.

YY

Advanced Clocking Support (Display Port protocol only)

NN
Use of 4th GT channel as TX TMDS clockNY


HW IP Configuration

Only below depicted IP configuration is supported at this time


Known Issues and Limitations
  • Only 1 IP configuration supported (listed in HW IP Configuration section)
  • Supports only HDMI protocol at this time

Kernel Configuration Options for Driver

2018.1 and onwards: CONFIG_ARCH_ZYNQMP and CONFIG_GENERIC_PHY should be enabled
Driver is added as an out-of-tree kernel module and therefore requires no driver specific kernel configuration However to enable the driver user must include it in the rootfs. Following steps are required enable the driver
  • Make sure the meta-user layer has the recipe-hdmi included
  • For 2019.2 onwards

    • Add the recipe to petalinux image. Edit ./meta-user/conf/user-rootfsconfig and add the new recipe at the end

Code Block
themeMidnight
CONFIG_kernel-module-hdmi
  • For 2018.1 to 2019.1
    • Add the recipe to petalinux image. Edit ./meta-user/recipes-core/images/petalinux-image-full.bbappend and add the new recipe at the end
      • NOTE - While using 2018.1 petalinux, the file name was ./meta-user/recipes-core/images/petalinux-image.bbappend
Code Block
themeMidnight
IMAGE_INSTALL_append = " kernel-module-hdmi"
  • Next include the driver in the rootfs
Code Block
themeMidnight
% petalinux-config -c rootfs
  • Select "user-pakages->modules->kernel-module-hdmi", save and exit
  • Build the project
Code Block
themeMidnight
%petalinux-build

Device Tree Binding

The dts node should be defined with correct hardware configuration. How to define the node is documented in
2020.2: Documentation/devicetree/bindings/xlnx,vphy.txt
2020.1: Documentation/devicetree/bindings/xlnx,vphy.txt

...

Driver has been tested with HDMI FrameBuffer Example Design design


Change Log

2020.2

2020.1

2019.2

  • Summary
    • Driver updated for 2019.2
    • Enabled TX 4th GT channel support
    • Enabled suspend and resume
    • Updated license file for 2019.2
  • Commits
    • be354c license: Update the license 2019.2
    • c1d04e hdmi: Driver update till 20190906
    • 55a308 phy: Enabling 4th GT channel in TX
    • 7eeeb1 hdmitx:hdmirx:vphy: Enabling suspend and resume
    • b608fb hdmitx:hdmirx:phy: remove "addtogroup" from files
    • e8da36 hdmitx:hdmirx:vphy: Driver update till 20190814

2019.1

  • Summary
    • Made driver compliant with DTG tool generated Device tree nodes and updated the documentation.
    • Updated license file for 2019.1
  • Commits
    • cf0a56 hdmitx: hdmirx: vphy: Driver update 5Apr2019
    • fe84ed license: Update the license obtained from legal
    • 3b3484 dt:bindings: Updated the documentation on DT bindings
    • 947f4f tx: hdmirx: vphy: Driver update 14Mar2018
    • e96b83 hdmitx:hdmirx:vphy: Support for auto DTG

2018.3

  • Summary
    • Made dru clock optional depending on NI-DRU configured value
  • Commits
    • 5d42de hdmitx:hdmirx:vphy:dt:bindings: Drivers update 20181004
    • 1c0710 hdmitx:hdmirx:phy: Update driver version 20180817
    • 309e4f phy: Enabling DRU clock
    • f9994e hdmitx:hdmirx:phy: Updated driver IP version
    • e7802d vphy: make dru optional

2018.1

  • Summary
    • Added 0.5% margin to user clock frequency
  • Commits
    • c443f3 phy: vphy: add 0.5% margin to user clock freq
    • ebee44 Initial release of 2018.1 hdmi drivers as kernel modules

Related Links