Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

dp_rx/data/dp_rx.tcl: unbreak vid_phy direction #20

Open
wants to merge 1 commit into
base: master
Choose a base branch
from

Conversation

jacmet
Copy link

@jacmet jacmet commented Sep 26, 2024

Commit edb1f97 (vid_phy_ctrl:hdmi_gt_ctrl: Generate Channels only if connected to DP/HDMI) broke the vid_phy direction setting as it set the 4th cell to 1 instead of 0.

As specified by the binding, the 4th cell encodes the phy directions:

direction_tx = 0 for RX and 1 for TX

https://github.com/Xilinx/dp-modules/blob/xlnx_rel_v2024.1/Documentation/devicetree/bindings/xlnx%2Cvphy.txt

So setting it to 1 doesn't make any sense for the DP receiver core. This seems to be a cut'n'paste mistake from the similar logic in the DP transmitter core.

Fixes: edb1f97 ("vid_phy_ctrl:hdmi_gt_ctrl: Generate Channels only if connected to DP/HDMI")

Commit edb1f97 (vid_phy_ctrl:hdmi_gt_ctrl: Generate Channels only if
connected to DP/HDMI) broke the vid_phy direction setting as it set the 4th cell to 1 instead of 0.

As specified by the binding, the 4th cell encodes the phy directions:

  direction_tx = 0 for RX and 1 for TX

https://github.com/Xilinx/dp-modules/blob/xlnx_rel_v2024.1/Documentation/devicetree/bindings/xlnx%2Cvphy.txt

So setting it to 1 doesn't make any sense for the DP receiver core.  This
seems to be a cut'n'paste mistake from the similar logic in the DP
transmitter core.

Fixes: edb1f97 ("vid_phy_ctrl:hdmi_gt_ctrl: Generate Channels only if
       connected to DP/HDMI")
Signed-off-by: Peter Korsgaard <[email protected]>
@jacmet
Copy link
Author

jacmet commented Sep 26, 2024

@Rajukumar45 @varalaxmi-bingi fyi

@Rajukumar45
Copy link
Contributor

Hi @jacmet
Thanks for the updating us.
Yes, the edb1f97#diff-3c2b853a4920f6e2652b2d357ef1ffa1d5c384d1f4dcd89e4686f2088ca7e9edR70 should set to '0 1 1 0' instead of '0 1 1 1'.
We will fix this.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants