ZHCSBP5C september 2013 – october 2020 SN65DSI86
PRODUCTION DATA
Native Aux transaction is broken into two pieces: Request and Reply. The DSIx6 will always be the originator of the Request (sometimes under GPU control and other times under DSIx6 HW control) and the recipient of the Reply from the downstream device.
Request Syntax: <4-bit AUX_CMD> <20-bit AUX_ADDR> <7-bit AUX_LENGTH> <DATA0 … DATA15>
Reply Syntax: <4-bit AUX_CMD> <4’b0000> <DATA0 … DATA15>
AUX_CMD[3:0] | DESCRIPTION |
---|---|
0x0 | I2C-Over-Aux Write MOT = 0. |
0x1 | I2C-Over-Aux Read MOT = 0 |
0x2 | I2C-Over-Aux Write Status Update MOT = 0. |
0x3 | Reserved. DSIx6 will ignore. |
0x4 | I2C-Over-Aux Write MOT = 1 |
0x5 | I2C-Over-Aux Read MOT = 1 |
0x6 | I2C-Over-Aux Write Status Update MOT=1. |
0x7 | Reserved. SN65DSI86 will ignore. |
0x8 | Native Aux Write |
0x9 | Native Aux Read |
0xA through 0xF | Reserved. SN65DSI86 will ignore. |
For Native Aux Reply transactions, the DSIx6 will update the status field in the CFR with command provided by the eDP device. For example, if the eDP receiver replies with a AUX_DEFER, the DSIx6 will attempt the request seven times (100 µs between each attempt) before updating the AUX_DEFR status field with 1’b1. If the eDP receiver does NOT reply before the 400-µs reply timer times out, then the SN65DSI86 will wait 100 µs before trying the request again. The SN65DSI86 will retry the request 7 times before giving up and then update the AUX_RPLY_TOUT field with 1’b1.
Example: Native Aux read of the eDP receiver capability field at DCPD address 0x00000h through 0x00008