Regular Displayport output from DP0 eDP

Autonomous Machines Jetson & Embedded Systems Jetson TX2
1

Hello,
I am trying to get Displayport output on a custom carrier board to which I have routed DP0 to a mini-dp connector.

On the reference schematic it says this is normally eDP but from the TRM it says DP can be output, by configuring HPD and pulls on the aux channel.
The device tree as been configured for both sor1 and sor to output on dp1 and dp0 and the nvdisplay’s enabled.
I can see video on dp1 however nothing when switching to dp0.

When I plug in to a monitor I get the following output for dp0.

[  132.332331] tegradc 15220000.nvdisplay: dp: plug event received
[  132.338455] hpd: state 3 (Disabled), hpd 1, pending_hpd_evt 1
[  132.344323] hpd: switching from state 3 (Disabled) to state 0 (Reset)
[  132.387324] hpd: state 0 (Reset), hpd 1, pending_hpd_evt 0
[  132.392893] tegradc 15220000.nvdisplay: blank - powerdown
[  132.398474] hpd: hpd_switch 0
[  132.401561] tegradc 15210000.nvdisplay: blank - powerdown
[  132.401660] hpd: switching from state 0 (Reset) to state 1 (Check Plug)
[  132.411332] hpd: state 1 (Check Plug), hpd 1, pending_hpd_evt 0
[  132.411350] hpd: switching from state 1 (Check Plug) to state 2 (Check EDID)
[  132.426986] tegradc 15220000.nvdisplay: blank - powerdown
[  132.471290] hpd: state 2 (Check EDID), hpd 1, pending_hpd_evt 0
[  132.477905] tegradc 15220000.nvdisplay: dp: aux write retry (0x10000100) -- 1
[  132.486613] tegradc 15220000.nvdisplay: dp: aux write retry (0x10000100) -- 0
[  132.495329] tegradc 15220000.nvdisplay: dp: aux write got error (0x10000100)
[  132.502414] tegradc 15220000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[  132.512090] tegradc 15220000.nvdisplay: dp: aux write retry (0x10000100) -- 1
[  132.520687] tegradc 15220000.nvdisplay: dp: aux write retry (0x10000100) -- 0
[  132.529309] tegradc 15220000.nvdisplay: dp: aux write got error (0x10000100)
[  132.536523] tegradc 15220000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[  132.546201] tegradc 15220000.nvdisplay: dp: aux write retry (0x10000100) -- 1
[  132.554749] tegradc 15220000.nvdisplay: dp: aux write retry (0x10000100) -- 0
[  132.563270] tegradc 15220000.nvdisplay: dp: aux write got error (0x10000100)
[  132.570359] tegradc 15220000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[  132.579976] tegradc 15220000.nvdisplay: dp: aux write retry (0x10000100) -- 1
[  132.588492] tegradc 15220000.nvdisplay: dp: aux write retry (0x10000100) -- 0
[  132.596996] tegradc 15220000.nvdisplay: dp: aux write got error (0x10000100)
[  132.604102] tegradc 15220000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[  132.613190] tegradc 15220000.nvdisplay: dp: failed to exit panel power save mode (0xfffffff2)
[  132.621745] hpd: edid read prepare failed
[  132.625618] tegradc 15220000.nvdisplay: blank - powerdown
[  132.631250] hpd: hpd_switch 0
[  132.634232] tegradc 15210000.nvdisplay: blank - powerdown
[  132.634276] hpd: switching from state 2 (Check EDID) to state 3 (Disabled)
[  132.646625] tegradc 15220000.nvdisplay: blank - powerdown

Since dp0 says eDP is there an additional setting that I should be looking for to properly enable regular displayport?
fdt.txt (371 KB)

2

Please try to use rel-28 to verify DP function first. It seems there were some problem in rel-32 DP driver.

3

I forgot to mention but we are on 28.2.1 with kernel 4.4

4

What DTB are you using?

5

My device tree is tegra186-quill-p3310-1000-c03-00-base.dts. The entire decompiled fdt is in the original post(fdt.txt).
The changes that were added to my dts were from tegra186-quill-p3310-1000-a00-00-dsi-dp.dts to enable dp1 except I left the default dc-or-node nvdisplay@15210000 as sor1 instead of sor. That by itself works fine.

When I try to enable dp0 using sor on nvdisplay@15220000, enable dp-display, and enable dpaux@1504000.
At this point both sor and sor1 are enabled. when a monitor is plugged into dp1 everything is normal. when dp0 is used I get the error in the OP.

6

We swapped the regular full sized working DP connector with a mini DP and the above error is now present on the previously working nvdisplay. Therefore we believe the issue is in the pin map to the mini-dp connector.