Table of Contents

Introduction

ZynqMP SoC has a Serdes/SIOU(Serial Input and Output block) module which provides High Speed Physical interface
for the below High Speed peripherals present in the SoC
USB (2 controllers)
SATA (1 controller with two lanes)
Display Port (1 controller with two lanes)
SGMII (4 controllers)
PCIe (1 controller with four lanes)
The inputs to Serdes is PIPE interface and output from it is are four High speed serial lanes. PHY provides 4 output lanes only for 14(PIPE) inputs (as mentioned above: 2 + 2 + 4 + 2+ 4 = 14). All the inputs are routed to PHY output lanes with a Mux (Interconnect matrix). Only some combinations are valid i.e, one cannot set Mux to use USB1 on lane 0 as such. PHY driver validates dts entries for the correct combination of controller and serdes lanes.

Note:

Due to the new driver introduce in upstream flow, we have (kernel and devicetree flow) configurations based on the release:

Support till 2020.2 release

Support form 2021.1 release

HW/IP Features

The ZynqMP PS shall incorporate a quad GT. Features include
A quad-transceiver
Supports PCIe, SATA, USB3.0, SGMII and DisplayPort requirements
1,2, or 4 lane PCIe support at 2.5 or 5.0Gbps
1 or 2 lane DisplayPort (TX only) at 1.62, 2.7, or 5.4Gbps
1-2 SATA channels at 1.5, 3.0 or 6.0Gbps
1-2 USB3.0 channel at 5.0Gbps
1-4 Ethernet SGMII channels at 1.25Gbps
Support SGMII for data only (no clock, or clock optional)
Support any 4 of the standards simultaneously
Provide flexible host-programmable multiplexing function for connecting the GT resources to the PS masters (DisplayPort, PCIe, SATA, GEM).
Kernel Configuration
Support till 2020.2 release:

Device Drivers------> Phy Subsystem--> <*> Xilinx ZynqMP phy driver

By enabling the above we need to see the below mentioned Kconfig parameter enabled
CONFIG_PHY_XIILINX_ZYNQMP=y

Support form 2021.1 release:

Device Drivers------>
     Phy Subsystem-->
		-*- PHY Core
         -*- Xilinx ZynqMP PHY driver 

By enabling the above we need to see the below mentioned Kconfig parameter enabled

CONFIG_PHY_XILINX_ZYNQMP=y

Devicetree

Support till 2020.2 release:

Device nodes should specify the configuration required in their "phys" property, containing a phandle to the phy port node and a device type
The phys property should be as mentioned below:

phys = <PHANDLE CONTOLLER_TYPE CONTROLLER_INSTANCE LANE_NUM LANE_FREQ>;
PHANDLE can be any among &lane0 or &lane1 or &lane2 or &lane3
CONTROLLER_TYPE can be any among PHY_TYPE_PCIE or PHY_TYPE_SATA or PHY_TYPE_USB or PHY_TYPE_DP or PHY_TYPE_SGMII
CONTROLLER_INSTANCE depends on CONTROLLER TYPE used, can be any of below

PHY_TYPE_PCIE : 0 or 1 or 2 or 3
PHY_TYPE_SATA : 0 or 1
PHY_TYPE_USB : 0 or 1
PHY_TYPE_DP : 0 or 1
PHY_TYPE_SGMII: 0 or 1 or 2 or 3

LANE_NUM depends on which lane clock is used as ref clk, can be 0 or 1 or 2 or 3
LANE_FREQ is the Frequency that controller can operate, can be any among 19.2Mhz,20Mhz,24Mhz,26Mhz,27Mhz,28.4Mhz,40Mhz,52Mhz,100Mhz,108Mhz,125Mhz,135Mhz,150Mhz

Example
Below Code should is required for probing the serdes driver. This should be added in zynqmp.dtsi

serdes: zynqmp_phy@fd400000 { compatible = "xlnx,zynqmp-psgtr"; status = "okay"; reg = <0x0 0xfd400000 0x0 0x40000>, <0x0 0xfd3d0000 0x0 0x1000>, <0x0 0xfd1a0000 0x0 0x1000>, <0x0 0xff5e0000 0x0 0x1000>; reg-names = "serdes", "siou", "fpd", "lpd"; xlnx,tx_termination_fix; lane0: lane@0 { #phy-cells = <4>; }; lane1: lane@1 { #phy-cells = <4>; }; lane2: lane@2 { #phy-cells = <4>; }; lane3: lane@3 { #phy-cells = <4>; }; };

The below code configures the USB 0 instance to use lane 2 and get 26 MHZ lane refclk from lane 2.

usb@fe200000 { ... phys = <&&lane2 PHY_TYPE_USB3 0 2 2600000>; ... };

This below code configures the SATA 1 instance to use lane 3 and get 125MHZ lane refclk from lane 1.

ahci@fd0c0000 { ... phys = <&&lane3 PHY_TYPE_SATA 1 1 125000000>; ... };

Support form 2021.1 release:

In the new upstreamed flow the below are the changes that need to be added

phys = <PHANDLE LANE_NUM CONTOLLER_TYPE CONTROLLER_INSTANCE LANE_FREQ>;

PHANDLE = &psgtr

LANE_NUM = 0, 1, 2, 3

CONTOLLER_TYPE = PHY_TYPE_PCIE or PHY_TYPE_SATA or PHY_TYPE_USB or PHY_TYPE_DP or PHY_TYPE_SGMII

CONTROLLER_INSTANCE =

Depends on controller type used, can be any of below mentioned

PHY_TYPE_PCIE : 0 or 1 or 2 or 3

PHY_TYPE_SATA : 0 or 1

PHY_TYPE_USB : 0 or 1

PHY_TYPE_DP : 0 or 1

PHY_TYPE_SGMII: 0 or 1 or 2 or 3

LANE_FREQ = refclk number that has the desired frequency

Example:

PSGTR changes:

                refclk4:psgtr_dp_clock {
                        compatible = "fixed-clock";
                        #clock-cells = <0x00>;
                        clock-frequency = <27000000>;
                };

                refclk3:psgtr_usb_clock {
                        compatible = "fixed-clock";
                        #clock-cells = <0x00>;
                        clock-frequency = <26000000>;
                };

                refclk2:psgtr_sata_clock {
                        compatible = "fixed-clock";
                        #clock-cells = <0x00>;
                        clock-frequency = <125000000>;
                };

                refclk1:psgtr_pcie_clock {
                        compatible = "fixed-clock";
                        #clock-cells = <0x00>;
                        clock-frequency = <150000000>;
                };

                psgtr: phy@fd400000 {
                        compatible = "xlnx,zynqmp-psgtr-v1.1";
                        reg = <0x00 0xfd400000 0x00 0x40000 0x00 0xfd3d0000 0x00 0x1000>;
                        reg-names = "serdes\0siou";
                        #clock-cells = <0x01>;
                        clocks = <&refclk1 &refclk2 &refclk3 &refclk4>;
						/* ref clk instances used per lane */
                        clock-names = "ref0\0ref1\0ref2\0ref3";
                        #phy-cells = <0x04>;
                        status = "okay";
                };

SATA instance 1 using Lane 3 refclk:125MHZ:

                ahci@fd0c0000 {
                        compatible = "ceva,ahci-1v84";
                        status = "okay";
                        reg = <0x00 0xfd0c0000 0x00 0x2000>;
      					.....
                        /* psgtr_phandle....lane number... controller_type...instance....refclk */
                        phys = <&psgtr 0x3 PHY_TYPE_SATA 0x01 0x1>;
                        reset-names = "sata_rst";
                        resets = <0x1a 0x10>;
                };

USB instance 0 lane 2 refclk 26MHZ:

      usb0@ff9d0000 {
                        #address-cells = <0x02>;
                        #size-cells = <0x02>;
                        status = "okay";
                        compatible = "xlnx,zynqmp-dwc3";
                        reg = <0x00 0xff9d0000 0x00 0x100>;
                        clock-names = "bus_clk\0ref_clk";
    					....
                        resets = <0x1a 0x3b 0x1a 0x3d 0x1a 0x3f>;
                        reset-names = "usb_crst\0usb_hibrst\0usb_apbrst";
						......
                        dwc3@fe200000 {
                                compatible = "snps,dwc3";
                                status = "okay";
                                reg = <0x00 0xfe200000 0x00 0x40000>;
                                interrupt-parent = <0x04>;
                                interrupt-names = "dwc_usb3\0otg\0hiber";
                                interrupts = <0x00 0x41 0x04 0x00 0x45 0x04 0x00 0x4b 0x04>;
                                #stream-id-cells = <0x01>;
								.....
                                dr_mode = "host";
                                maximum-speed = "super-speed";
            		            phy-names = "usb3-phy";
								/* psgtr_phandle....lane number... controller_type...instance....refclk */
		                        phys = <&psgtr 0x2 PHY_TYPE_USB 0x00 0x02>;
                        };
                };

Test Procedure

As this driver is being used by SATA, USB, PCIe, SGMII and DP protocols. Testing the functionality of any of those protocols will automatically test this IP.
Expected O/P
Once linux is booted type "grep | gtr" and check whether PLL lock is happening, the below output is expected

root@Xilinx-ZCU102-2016_3:~# dmesg | grep gtr [ 6.575387] xilinx-psgtr fd400000.zynqmp_phy: Lane:3 type:3 protocol:2 pll_locked:yes [ 6.808627] xilinx-psgtr fd400000.zynqmp_phy: Lane:2 type:0 protocol:3 pll_locked:yes [ 7.570858] xilinx-psgtr fd400000.zynqmp_phy: Lane:1 type:8 protocol:4 pll_locked:yes

Mainline Status
The current driver available in the Xilinx Linux git is in sync with the open-source kernel.
Change log

2016.3
Summary:
Correct swing and preemphasis values
Reset the de-emphasis and swing control for DP
Added separate function for bypassing scrambler/descrambler and encoder/decoder feature
Add SGMII support to serdes driver
Fix kernel-doc format for xpsgtr_set_rxwidth
Add missing header to declare exported functions
Change serdes calibration logic to ICM_CFG1

2016.4
NONE

2017.1
Removed tx_termination_fix flag and added the calibration fix based on the silicon revision
Use reset-controller framework to assert/de-assert reset signals while configuring serdes lanes
Corrected the logic for freeing NVMEM buffer
Corrected the logic for waiting for assert/de-assert to happen
Added configuring USB PIPE3 signals during reset release
2017.2
None

2017.3
Use the configured GT lane instead of hardcoding a value into ICM_CFG1 for tx termination fix
2017.4
Export functions for asserting/de-asserting usb core reset 52f8f

2018.1
Summary:
Reinitialize gt lane for USB only if required 6d786
Use EEMI framework for performing ULPI reset sequence f366d

2018.2
None

2018.3
None
2019.1
Defer probe if firmware is not ready 6a634
2019.2
None
2020.1
None
2020.2
None

2021.1

zynqMp: Add PHY driver for the Xilinx ZynqMP Gigabit Transceiver
Fix unused-function compiler warning
Handle the clock enable/disable properly
Skip PHY initialization and PLL lock for USB

Note: This new psgtr configuration is applicable from release Xilinx - 2021.1.

2021.2

None

2022.1
Summary:

Kernel upgrade to 5.15
Fix bus width setting for SGMII 5d691d

2022.2

None

2023.1

Kernel upgrade to 6.1
Updated Comment Description- SGMII is validated on SOM KR260. 7f2f1a1

2023.2

None

2024.1

Kernel upgrade to 6.6

2024.2

phy: xilinx: phy-zynqmp: Fix SGMII linkup failure on resume 4dd8383fcbe1

Xilinx Wiki

Zynq Ultrascale MPSOC Linux SIOU driver

Introduction

Kernel Configuration

Support till 2020.2 release:

Support form 2021.1 release:

Devicetree

Support till 2020.2 release:

Support form 2021.1 release:

Test Procedure

Expected O/P

Mainline Status

Change log

Related Links