PPI Signals - 4.3 English

MIPI D-PHY LogiCORE IP Product Guide (PG202)

Document ID
PG202
Release Date
2023-05-16
Version
4.3 English
The MIPI D-PHY core provides PPI signaling for clock lane and data lane operation. The signal ports are listed in the following tables. In these tables <n> is the configurable data lane number (0 to 3).
Table 1. Common PPI Control Signals
Signal Direction Clock Domain Description
cl_ stopstate, dl<n>_stopstate Output Async Lane is in Stop state.

This active-High signal indicates that the Lane module (TX or RX) is currently in the Stop state. Also, the protocol can use this signal to indirectly determine if the PHY line levels are in the LP-11 state.

Note: This signal is asynchronous to any clock in the PPI.
cl_enable, dl<n>_enable Input Async Enable Lane Module.

This active-High signal forces the lane module out of “shutdown”. All line drivers, receivers, terminators, and contention detectors are turned off when Enable is Low. When Enable is Low, all other PPI inputs are ignored and all PPI outputs are driven to the default inactive state. Enable is level sensitive and does not depend on any clock.

cl_ulpsactivenot, dl<n>_ulpsactivenot Output Async ULP State (not) Active.

This active-Low signal is asserted to indicate that the Lane is in the ULP state. For a receiver, this signal indicates that the Lane is in the Ultra Low Power (ULP) state. At the beginning of the ULP state, ulpsactivenot is asserted together with rxulpsesc, or rxclkulpsnot for a clock lane. At the end of the ULP state, this signal becomes inactive to indicate that the Mark-1 state has been observed. Later, after a period of time (Twakeup), the rxulpsesc (or rxclkulpsnot) signal is deasserted.

Table 2. D-PHY TX Clock Lane High-Speed PPI Signal
Signal Direction Clock Domain Description
cl_txrequesths Input txbyteclkhs High-Speed Transmit Request and Data Valid.

For clock lanes, this active-High signal causes the lane module to begin transmitting a high-speed clock.

Note: cl_requesths should only be asserted after the init_done is High, until then it should be driven as 0
cl_txclkactivehs Output txbyteclkhs This active-High signal indicates that the clock is being transmitted on the clock lane.
Table 3. D-PHY TX Clock Lane Escape Mode PPI Signals
Signal Direction Clock Domain Description
cl_txulpsclk Input core_clk Transmit Ultra-Low Power State on Clock Lane.

This active-High signal is asserted to cause a clock lane module to enter the ULP state. The lane module remains in this mode until txulpsclk is deasserted.

cl_txulpsexit Input core_clk Transmit ULP Exit Sequence.

This active-High signal is asserted when the ULP state is active and the protocol is ready to leave the ULP state. The PHY leaves the ULP state and begins driving Mark-1 after txulpsexit is asserted. The PHY later drives the Stop state (LP-11) when txrequestesc is deasserted. txulpsexit is synchronous to txclkesc. This signal is ignored when the lane is not in the ULP state.

Table 4. D-PHY TX Data Lane High-Speed PPI Signals
Signal Direction Clock Domain Description
txbyteclkhs Output N/A High-Speed Transmit Byte Clock.

This is used to synchronize PPI signals in the high-speed transmit clock domain. AMD recommends that all transmitting data lane modules share one txbyteclkhs signal. The frequency of txbyteclkhs is exactly 1/8 the high-speed bit rate.

dl<n>_txdatahs[7:0] Input txbyteclkhs High-Speed Transmit Data.

Eight-bit high-speed data to be transmitted. The signal connected to txdatahs[0] is transmitted first. Data is captured on rising edges of txbyteclkhs.

dl<n>_txrequesths Input txbyteclkhs High-Speed Transmit Request and Data Valid.

A Low-to-High transition on txrequesths causes the Lane module to initiate a SoT sequence. A High-to-Low transition on txrequest causes the lane module to initiate an EoT sequence. For data lanes, this active-High signal also indicates that the protocol is driving valid data on txdatahs to be transmitted. The lane module accepts the data when both txrequesths and txreadyhs are active on the same rising txbyteclkhs clock edge. The protocol always provides valid transmit data when txrequesths is active. After asserted, txrequesths remains High until the data has been accepted, as indicated by txreadyhs. txrequesths is only asserted while txrequestesc is Low.

dl<n>_txreadyhs Output txbyteclkhs High-Speed Transmit Ready.

This active-High signal indicates that txdatahs[7:0] is accepted by the Lane module to be serially transmitted. txreadyhs is valid on rising edges of txbyteclkhs.

dl<n>_txskewcalhs Input txbyteclkhs High-Speed Transmit Skew Calibration.

A low-to-high transition on TxSkewCalHS causes the lane module to initiate a deskew calibration. A high-to-low transition on TxSkewCalHS causes the lane module to stop deskew pattern transmission and initiate an EoT sequence

Note: This pin is applicable only when the line rate is >1500 and the transmission of calibration packet is selected.
Table 5. D-PHY TX Data Lane Control Interface PPI Signal
Signal Direction Clock Domain Description
dl<n>_forcetxstopmode Input Aync Force Lane to Generate Stop State.

This signal allows the protocol to force a lane module into the Stop state during initialization or following an error situation, such as an expired timeout. When this signal is High, the lane module state machine is immediately forced into the Stop state.

Table 6. D-PHY TX Data Lane Escape Mode PPI Signals
Signal Direction Clock Domain Description
txclkesc Input N/A Escape Mode Transmit Clock.

This clock is directly used to generate escape sequences. The period of this clock determines the phase times for low-power signals as defined in the D-PHY specification.

dl<n>_txrequestesc Input txclkesc Escape Mode Transmit Request. This active-High signal, asserted together with exactly one of txlpdtesc, txulpsesc, or one bit of txtriggeresc, is used to request entry into escape mode. When in escape mode, the lane stays in escape mode until txrequestesc is deasserted. txrequestesc is only asserted by the protocol while txrequesths is Low. txrequesths has highest priority than txrequestesc.
dl<n>_txlpdtesc Input txclkesc Escape Mode Transmit Low-Power Data.

This active-High signal is asserted with txrequestesc to cause the lane module to enter low-power data transmission mode. The Lane module remains in this mode until txrequestesc is deasserted. txulpsesc and all bits of txtriggeresc[3:0] are Low when txlpdtesc is asserted.

dl<n>_txulpsexit Input txclkesc Transmit ULP Exit Sequence.

This active-High signal is asserted when the ULP state is active and the protocol is ready to leave the ULP state. The PHY leaves the ULP state and begins driving Mark-1 after txulpsexit is asserted. The PHY later drives the Stop state (LP-11) when txrequestesc is deasserted. txulpsexit is synchronous to txclkesc. This signal is ignored when the lane is not in the ULP state.

dl<n>_txulpsesc Input txclkesc Escape Mode Transmit Ultra-Low Power State.

This active-High signal is asserted with txrequestesc to cause the lane module to enter the ultra-low power state. The lane module remains in this mode until txrequestesc is deasserted. txlpdtesc and all bits of txtriggeresc[3:0] are Low when txulpsesc is asserted.

dl<n>_txtriggeresc[3:0] Input txclkesc Escape Mode Transmit Trigger 0-3.

One of these active-High signals is asserted with txrequestesc to cause the associated trigger to be sent across the lane interconnect. In the receiving lane module, the same bit of rxtriggeresc is then asserted and remains asserted until the lane interconnect returns to the Stop state, which happens when txrequestesc is deasserted at the transmitter. Only one bit of txtriggeresc[3:0] is asserted at any given time, and only when txlpdtesc and txulpsesc are both Low. The following mapping is done by the D-PHY TX module:

  • Reset-Trigger→txtriggeresc[3:0] = 4’b0001
  • Unknown-3→txtriggeresc[3:0] = 4’b0010
  • Unknown-4→txtriggeresc[3:0] = 4’b0100
  • Unknown-5→txtriggeresc[3:0] = 4’b1000
dl<n>_txdataesc[7:0] Input txclkesc Escape Mode Transmit Data.

This is the eight-bit Escape mode data to be transmitted in low-power data transmission mode. The signal connected to txdataesc[0] is transmitted first. Data is captured on rising edges of txclkesc.

dl<n>_txvalidesc Input txclkesc Escape Mode Transmit Data Valid.

This active-High signal indicates that the protocol is driving valid data on txdataesc[7:0] to be transmitted. The lane module accepts the data when txrequestesc, txvalidesc, and txreadyesc are all active on the same rising txclkesc clock edge.

dl<n>_txreadyesc Output txclkesc Escape Mode Transmit Ready.

This active-High signal indicates that txdataesc[7:0] is accepted by the lane module to be serially transmitted. txreadyesc is valid on rising edges of txclkesc.

Table 7. D-PHY RX Clock Lane PPI Signals
Signal Direction Clock Domain Description
cl_rxclkactivehs Output Async Receiver Clock Active.

This asynchronous, active-High signal indicates that a clock lane is receiving a Double Data Rate (DDR) clock signal.

cl_rxulpsclknot Output Asynch Receiver Ultra-Low Power State on Clock Lane.

This active-Low signal is asserted to indicate that the clock lane module has entered the ultra-low power state. The lane module remains in this mode with rxulpsclknot asserted until a Stop state is detected on the lane interconnect.

Table 8. D-PHY RX Data Lane High-Speed PPI Signals
Signal Direction Clock Domain Description
rxbyteclkhs Output N/A High-Speed Receive Byte Clock.

This is used to synchronize signals in the high-speed receive clock domain. The rxbyteclkhs is generated by dividing the received High-Speed DDR clock.

Note: This clock is not continuous and is only available for sampling when the RX clock lane is in high-speed mode.
dl<n>_rxdatahs[7:0] Output rxbyteclkhs High-Speed Receive Data.

Eight-bit high-speed data received by the lane module. The signal connected to rxdatahs[0] was received first. Data is transferred on rising edges of rxbyteclkhs.

dl<n>_rxvalidhs Output rxbyteclkhs High-Speed Receive Data Valid.

This active-High signal indicates that the lane module is driving data to the protocol on the rxdatahs[7:0] output. There is no rxreadyhs signal, and the protocol is expected to capture rxdatahs[7:0] on every rising edge of rxbyteclkhs where rxvalidhs is asserted. There is no provision for the protocol to slow down (throttle) the receive data.

dl<n>_rxactivehs Output rxbyteclkhs High-Speed Reception Active.

This active-High signal indicates that the lane module is actively receiving a high-speed transmission from the lane interconnect.

dl<n>_rxsynchs Output rxbyteclkhs Receiver Synchronization Observed.

This active-High signal indicates that the Lane module has seen an appropriate synchronization event. rxsynchs is High for one cycle of rxbyteclkhs at the beginning of a high-speed transmission when rxactivehs is first asserted.

dl<n>_rxskewcalhs Output rxbyteclkhs High-Speed Receive Skew Calibration.
This active-High signal indicates that the high speed deskew burst is being received.
Note: This pin is only available for line rate >1500 Mbps configuration.
Table 9. D-PHY RX Data Lane PPI Control Interface Signal
Signal Direction Clock Domain Description
dl<n>_forcerxmode Input Async Force Lane Module to Re-Initialization.

This signal allows the protocol to initialize a Lane module and should be released, that is, driven Low, only when the Dp and Dn inputs are in the Stop state for a time T_INIT, or longer.

Note: Assert this signal when the RX Data Lane is in stopstate. Asserting this signal in the middle of High-Speed data reception will result in data integrity failures.
Table 10. D-PHY RX Data Lane Escape Mode PPI Signals
Signal Direction Clock Domain Description
dl<n>_rxclkesc Output N/A Escape Mode Receive Clock.

This signal is used to transfer received data to the protocol during escape mode. This clock is generated from the two low-power signals in the lane interconnect. Because of the asynchronous nature of escape mode data transmission, this clock cannot be periodic.

dl<n>_rxlpdtesc Output core_clk Escape Low-Power Data Receive Mode.

This active-High signal is asserted to indicate that the lane module is in low-power data receive mode. While in this mode, received data bytes are driven onto the rxdataesc[7:0] output when rxvalidesc is active. The lane module remains in this mode with rxlpdtesc asserted until a Stop state is detected on the lane interconnect.

dl<n>_rxulpsesc Output Async Escape Ultra-Low Power (Receive) Mode. This active-High signal is asserted to indicate that the lane module has entered the ultra-low power state. The lane module remains in this mode with rxulpsesc asserted until a Stop state is detected on the lane interconnect.
dl<n>_rxtriggeresc[3:0] Output Async Escape Mode Receive Trigger 0-3.

These active-High signals indicate that a trigger event has been received. The asserted rxtriggeresc[3:0] signal remains active until a Stop state is detected on the lane interconnect. The following mapping is done by the D-PHY RX module:

  • Reset-Trigger → rxtriggeresc[3:0] = 4’b0001
  • Unknown-3 → rxtriggeresc[3:0] = 4’b0010
  • Unknown-4 → rxtriggeresc[3:0] = 4’b0100
  • Unknown-5 → rxtriggeresc[3:0] = 4’b1000
dl<n>_rxdataesc[7:0] Output core_clk Escape Mode Receive Data.

This is the eight-bit escape mode low-power data received by the lane module. The signal connected to rxdataesc[0] is received first. Data is transferred on rising edges of rxclkesc.

dl<n>_rxvalidesc Output core_clk Escape Mode Receive Data Valid.

This active-High signal indicates that the lane module is driving valid data to the protocol on the rxdataesc[7:0] output. There is no rxreadyesc signal, and the protocol is expected to capture rxdataesc[7:0] on every rising edge of rxclkesc where rxvalidesc is asserted. There is no provision for the protocol to slow down (throttle) the receive data.

Table 11. D-PHY RX Data Lane PPI Error Signals
Signal Direction Clock Domain Description
dl<n>_ errsoths Output rxbyteclkhs Start-of-Transmission (SoT) Error.

If the high-speed SoT leader sequence is corrupted, but in such a way that proper synchronization can still be achieved, this active-High signal is asserted for one cycle of rxbyteclkhs. This is considered to be a soft error in the leader sequence and confidence in the payload data is reduced.

dl<n>_errsotsynchs Output rxbyteclkhs Start-of-Transmission Synchronization Error.

If the high-speed SoT leader sequence is corrupted in a way that proper synchronization cannot be expected, this active-High signal is asserted for one cycle of rxbyteclkhs.

dl<n>_erresc Output Async Escape Entry Error.

If an unrecognized escape entry command is received, this active-High signal is asserted and remains asserted until the next change in line state.

dl<n>_errsyncesc Output Async Low-Power Data Transmission Synchronization Error.

If the number of bits received during a low-power data transmission is not a multiple of eight when the transmission ends, this active-High signal is asserted and remains asserted until the next change in line state.

dl<n>_errcontrol Output Async Control Error.

This active-High signal is asserted when an incorrect line state sequence is detected. For example, if a turn-around request or escape mode request is immediately followed by a Stop state instead of the required Bridge state, this signal is asserted and remains asserted until the next change in line state.