This thread has been locked.

If you have a related question, please click the "Ask a related question" button in the top right corner. The newly created question will be automatically linked to this question.

SN65DP159: DP to HDMI 2.0

Part Number: SN65DP159


Hi ,

We have used SN65DP159 as a DP to HDMI retimer, and is default set to pin strapping mode.

If we would like to support up to HDMI 2.0, do we must change to I2C_EN mode, and configure the register to make it support 4K2K p60?

Thanks,
Claire

  • Hi Claire,

    No register settings are needed for the DP159 to support both HDMI 1.4B and HDMI 2.0 resolutions, it will snoop the DDC lines and automatically switch clock ratios as needed. Also, make sure to leave the TX_TERM_CTL pin in the "automatic" setting so the DP159 automatically switches the TX terminations based on data rate. Please note that in pin configuration mode, the DP159 will default to redriver mode at lower resolutions.

    Regards,
    JMMN
  • Hi JMMN,

    Thank you for the quick reply.  We will check on the TX_TERM_CTL pin.  

    If the DP159 can automatic switch the Tx termination based on the data rate. What does it mean in pin configuration, DP159 will redrive at lower resolution by default.  Does this mean we must have something incorrect in the TX_TERM_CTL pin?

    So that we keep seeing the output at the lower resolution?

    Thanks,

    Claire

  • Hi Claire,

    The DP159 is both a retimer and redriver, outputs will be seen in both modes. In its default pin configuration mode, the DP159 will operate as a redriver below 1G and a retimer above 1G. See section 9.4.1 and 9.4.2 in the datasheet for more information.

    Regards,
    JMMN
  • Hi JMMN,

    We are using SN65DP150RSB, from the datasheet, it shows the TX_TERM_CTL pin is NA. In this case, how can we make the DP159 automatically switch the Tx terminations based on the data rate?

    Thanks,
    Claire
  • Hi Claire,

    Ok, the DP159RSB defaults to TX_TERM_CTL in auto mode unless overwritten by I2C.

    Regards,
    JMMN
  • Hi JMMN,

    We have resolved this issue, it's functioning well in our platform.

    Thank you

    Claire