DisplayPort TX IP AUX_CH fails to retry on NACK for an AUX_WR transaction

• Related Articles

• DisplayPort RX IP returns AUX_ACK instead of AUX_NACK when writing to an unsupported DPCD address

  Description: The DisplayPort IP generates an illegal response to an AUX request when accessing a reserved DPCD address. The DisplayPort RX IP should return AUX_NACK when writing to an unsupported DPCD address, but the design responds with AUX_ACK. ...

• DisplayPort TX IP unable to handle I2C_DEFER and I2C_NACK

  Description: The DisplayPort IP is not able to respond to I2C_DEFER and I2C_NACK correctly. Resolution: This will be fixed in the next DisplayPort IP release.

• DisplayPort RX IP AUX channel does not handle I2C write at the end of a transaction (MOT=0)

  Description: The DisplayPort IP does not return I2C_ACK when receiving the end-of-transaction MOT=0, so it cannot correctly close the I2C transaction. Resolution: This will be fixed in the next DisplayPort IP release.

• DisplayPort TX IP Version 2.1.0 does not support back-to-back video input without blanking interval

  Description DisplayPort TX IP version 2.1.0 requires the video input to provide blanking interval between active horizontal video lines to ensure correct video data packing. Failure symptoms include no video image output or black screen, even though ...

• DisplayPort TX IP link training sequence not compliant with the DisplayPort Specification

  Description: The DisplayPort IP link training sequence is a subset of the DisplayPort Specification and does not yet support voltage and pre-emphasis adjustment requests, link rate down-training, or lane count down-training. Resolution: This will be ...