Sure, DP_AUX is responsible for the HPD event, but the logs (see attached full dmesg log) mention i2c errors for the modified nvdisplay.
[ 1.473184] tegradc 15200000.nvdisplay: dp: Failed for I2C write addr:80, size:1, stat:0x10000100
That was the cause that brought me into the i2c direction.
Effectively, the problem is a failure to exit panel power save mode due to failed DPCD write:
[ 1.501545] tegradc 15200000.nvdisplay: dp: Failed to write DPCD data. CMD 0x600, Status 0x10000100
[ 1.501576] tegradc 15200000.nvdisplay: dp: failed to exit panel power save mode (0xfffffff2)
I am not quite sure if this could relate to some regulator settings which seem to be misconfigured for this DP out:
[ 1.475974] tegradc 15200000.nvdisplay: dp: couldn't get regulator vdd-dp-pwr
[ 1.475997] tegradc 15200000.nvdisplay: dp: couldn't get regulator avdd-dp-pll
[ 1.476018] tegradc 15200000.nvdisplay: dp: couldn't get regulator vdd-edp-sec-mode
[ 1.476039] tegradc 15200000.nvdisplay: dp: couldn't get regulator vdd-dp-pad
(All lines taken from outputs attached below!)
Also, i am actually a bit confused about the following statements from you:
Most of other properties may still be the HDMI one so it is not able to work with dp by just changing 1~2 lines.
in contrast to:
Basically, the hint in the last citation worked for us, but leads to the mentioned errors above.
We just confirmed the compatibility of our schematics to the reference by A/B comparison and 4-eyes principle.
For completeness, see attached schematics below.
ac10x.dts (246.5 KB)
dmesg.log (108.9 KB)
ac100-r1_scm.pdf (1.2 MB)