UPGRADE YOUR BROWSER

We have detected your current browser version is not the latest one. Xilinx.com uses the latest web technologies to bring you the best online experience possible. Please upgrade to a Xilinx.com supported browser:Chrome, Firefox, Internet Explorer 11, Safari. Thank you!

Reply

2017.1 DisplayPort issues

Accepted Solution Solved
Highlighted
Participant
Posts: 53
Registered: ‎12-02-2014
Accepted Solution

2017.1 DisplayPort issues

Hi, I have a design similar to 2016.4 TRD (system-dm5) displayport only design.

 

I'm trying to test it with the 2017.1 linux kernel.  I boot successfully, but I have the following errors regarding the DisplayPort:

 

# dmesg | grep -in xilinx-
177:[ 4.375606] xilinx-psgtr: probe of fd400000.zynqmp_phy failed with error -2
178:[ 4.376552] xilinx-dpdma fd4c0000.dma: Xilinx DPDMA engine is probed
180:[ 4.376704] xilinx-zynqmp-dma fd500000.dma: ZynqMP DMA driver Probe success
182:[ 4.376818] xilinx-zynqmp-dma fd510000.dma: ZynqMP DMA driver Probe success
184:[ 4.376929] xilinx-zynqmp-dma fd520000.dma: ZynqMP DMA driver Probe success
186:[ 4.377042] xilinx-zynqmp-dma fd530000.dma: ZynqMP DMA driver Probe success
188:[ 4.377156] xilinx-zynqmp-dma fd540000.dma: ZynqMP DMA driver Probe success
190:[ 4.377269] xilinx-zynqmp-dma fd550000.dma: ZynqMP DMA driver Probe success
192:[ 4.377382] xilinx-zynqmp-dma fd560000.dma: ZynqMP DMA driver Probe success
194:[ 4.377494] xilinx-zynqmp-dma fd570000.dma: ZynqMP DMA driver Probe success
201:[ 5.599268] xilinx-drm-dp-sub fd4aa000.dp_sub: Xilinx DisplayPort Subsystem is probed
294:[ 6.277155] xilinx-dp-snd-pcm amba:dp_snd_pcm0: Xilinx DisplayPort Sound PCM probed
295:[ 6.284758] xilinx-dp-snd-pcm amba:dp_snd_pcm1: Xilinx DisplayPort Sound PCM probed
296:[ 6.292454] xilinx-dp-snd-codec amba:dp_snd_codec0: Xilinx DisplayPort Sound Codec probed
297:[ 6.302975] xilinx-dp-snd-card amba:dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
298:[ 6.316143] xilinx-dp-snd-card amba:dp_snd_card: xilinx-dp-snd-codec-dai <-> xilinx-dp-snd-codec-dai mapping ok
299:[ 6.328563] xilinx-dp-snd-card amba:dp_snd_card: Xilinx DisplayPort Sound Card probed
315:[ 6.425407] xilinx-drm-dp fd4a0000.dp: failed to get phy lane
323:[ 6.489428] xilinx-drm-dp fd4a0000.dp: failed to get phy lane

 

 

Any idea what could cause the failure to find the DP phy lane?  I'm assuming some other DP subsystem must be failing first, and that's why I'm seeing the failure to find the phy lane.


Accepted Solutions
Visitor
Posts: 10
Registered: ‎04-11-2017

Re: 2017.1 DisplayPort issues

I had a similiar problem (we use our own Yocto recipes based on meta-Xilinx).

The solution for me was to add:

CONFIG_NVMEM_ZYNQMP=y

View solution in original post


All Replies
Visitor
Posts: 10
Registered: ‎04-11-2017

Re: 2017.1 DisplayPort issues

I had a similiar problem (we use our own Yocto recipes based on meta-Xilinx).

The solution for me was to add:

CONFIG_NVMEM_ZYNQMP=y

Participant
Posts: 53
Registered: ‎12-02-2014

Re: 2017.1 DisplayPort issues

I did not have that config item set, but enabling it didn't change my results at all.  Perhaps there are some other kernel config items I'm missing then.

Participant
Posts: 53
Registered: ‎12-02-2014

Re: 2017.1 DisplayPort issues

here's some more info after making some changes to match modern device tree:

 

# dmesg | grep -in fail
57:[ 1.024573] CPU1: failed to come online
58:[ 1.024578] CPU1: failed in unknown state : 0x0
59:[ 2.049228] CPU2: failed to come online
60:[ 2.049233] CPU2: failed in unknown state : 0x0
61:[ 3.073886] CPU3: failed to come online
62:[ 3.073891] CPU3: failed in unknown state : 0x0
80:[ 3.247982] Failed to initialise IOMMU /amba/smmu@fd800000
281:[ 6.130670] cpu cpu0: failed to get clock: -2
282:[ 6.134947] cpufreq-dt: probe of cpufreq-dt failed with error -2
327:[ 7.468120] xilinx-psgtr fd400000.zynqmp_phy: Failed to release reset
328:[ 7.474475] phy phy-fd400000.zynqmp_phy.1: phy init failed --> -110
329:[ 7.480724] xilinx-drm-dp fd4a0000.dp: failed to init phy lane 0
330:[ 7.486721] xilinx-drm-dp: probe of fd4a0000.dp failed with error -110
331:[ 8.492119] xilinx-psgtr fd400000.zynqmp_phy: Failed to release reset
332:[ 8.498472] phy phy-fd400000.zynqmp_phy.3: phy init failed --> -110
333:[ 8.504727] ahci-ceva: probe of fd0c0000.ahci failed with error -110
334:[ 11.508163] xilinx-psgtr fd400000.zynqmp_phy: Failed to release reset
335:[ 11.514520] phy phy-fd400000.zynqmp_phy.2: phy init failed --> -110
336:[ 11.520768] dwc3 fe200000.dwc3: failed to initialize core
337:[ 11.526160] dwc3: probe of fe200000.dwc3 failed with error -110
# Openbox-Message: Failed to open the display from the DISPLAY environment variable.

Participant
Posts: 53
Registered: ‎12-02-2014

Re: 2017.1 DisplayPort issues

It was a combination of PMUFW being a problem (PMUFW is expecting FSBL to pass a config object to PMUFW, but uboot SPL does not).  I ended up just modifying 2016.4 PMUFW to report as 2017.1 to proceed for now.

 

And a few kernel config options were necessary:

 

CONFIG_PM

CONFIG_ZYNQMP_RESET_CONTROLLER

CONFIG_NVMEM_ZYNQMP

 

Thanks,

 

Justin D.