I just wanted to say there is only nvidia,out-hotplug-state under sor1
1 Like
Hi www,
I have news, please have a look at the dmesg log:
hotplug_state = 1 is now one
[ 1.062594] DEBUG of _dc.c → hotplug_state = 1
[ 328.525767] tegradc tegradc.0: blank - powerdown
output_2021-06-20_17-40-31.log (81.5 KB)
Can you share how did you make it to have correct hotplug_state?
first of all thank you. I have learned a lot
This is still the debug patch… but not the real solution.
Please share us your latest dts and dmesg. Also, tell us what you’ve changed to make the hotplug_state work.
I know that. But already a success. Because the hardware works
The problem is the kernel only starts when the screen is off! After about 10s I turn on the screen and a picture comes up.
I have copy nvidia,out-hotplug-state = <1>; to →
disp-default-out {
nvidia,out-type = <TEGRA_DC_OUT_DP>;
nvidia,out-align = <TEGRA_DC_ALIGN_MSB>;
nvidia,out-order = <TEGRA_DC_ORDER_RED_BLUE>;
nvidia,out-flags = <TEGRA_DC_OUT_CONTINUOUS_MODE>;
nvidia,out-pins = <TEGRA_DC_OUT_PIN_H_SYNC TEGRA_DC_OUT_PIN_POL_LOW
TEGRA_DC_OUT_PIN_V_SYNC TEGRA_DC_OUT_PIN_POL_LOW
TEGRA_DC_OUT_PIN_PIXEL_CLOCK TEGRA_DC_OUT_PIN_POL_LOW
TEGRA_DC_OUT_PIN_DATA_ENABLE TEGRA_DC_OUT_PIN_POL_HIGH>;
nvidia,out-parent-clk = “pll_d2”;
nvidia,out-hotplug-state = <1>;
};
What I had also done before, now it goes
Where is the full dts and dmesg? I don’t see any attachment.
Also, do you mean your configuration for nvidia,out-hotplug-state in device tree was wrong?
I have so many windows open :-)
It comes soon…
This can also be. But I sometimes had the problem that the kernel restarted with panic when I had nvidia,out-hotplug-state = <1>;.I can no longer really understand it that way
Here is the current dts and dmesg file:
dts:
dts_20.06.2021.txt (325.7 KB)
dmesg:
dmesg_output_2021-06-20_18-45-03.log (94.3 KB)
Just want to know, does it always take 5 mins to see such training pass log from your dmesg?
31.864933] vdd-usb-hub-en: disabling
[ 331.305343] tegradc tegradc.0: blank - powerdown
[ 331.364582] dp lt: state 5 (link training pass), pending_lt_evt 1
And can you try to just dump the log from the beginning? Please do not wait for like 1500 second and dump the log.
No, the first comes [ 2.129200] dp lt: state 5 (link training pass), pending_lt_evt 1
Sorry now I understand :-)
Yes, I always get a link training pass, but not after 5min
[ 2.129200] dp lt: state 5 (link training pass), pending_lt_evt 1
[ 1013.944755] dp lt: switching from state 5 (link training pass) to state 0 (Reset)
[ 1013.944790] dp lt: state 0 (Reset), pending_lt_evt 0
[ 1013.944808] DEBUG hotplug_state = 1
[ 1013.944824] dp lt: link training force disable
[ 1013.944849] dp lt: switching from state 0 (Reset) to state 4 (link training fail/disable)
Can you paste your board schematic again? Actually, it was really blurred and hardly to read… Need a clear version.
Of course with pleasure. Do you suspect a problem with the circuit?
What works yes is the differential pairs TXD0-TXD3.
And DP_HPD I just measured again → 1,8V on Pin 96 when the screen is connected.
Do you suspect an error with DP1 AUX CH N/P?
I have checked the circuit board several times, and also replaced the circuit board once.
What I can do again Check C40 and C46 for 100nF → Because they are in line.
Greetings…
Sorry for late reply.
Can you share me the result of this command?
sudo busybox devmem 0x7000319c
Hello WayneWWW,
nice to hear from you :-) I am glad for your help.
Of course:
The output is: 0x00000140
For the overview:
For all who read along. No hardware error could be found. The DP interface incl. DP1 AUX CH N/P is working.
Hi,
When devkit DP hotplug is working, the pinmux setting is 0x00000040.
According to this table, it means the LPDR is disabled. Can you try to directly write 0x00000040 to your 0x7000319c and try hotplug case again?