Re: [802.3_ISAAC] [EXTERNAL] Re: [802.3_ISAAC] Question on Baseline Text Proposal for TDD Based 802.3dm PHY
Hi, Ragnar,
The SILENT1 state is proposed by several of the TDD supporters, to allow some extra config/preparation time for the SLAVE to switch its transmit signal from 3Gsps(PAM2) to a final symbol rate of 6 Gsps PAM2. During this time, the MASTER switched to the transmission of 3Gsps PAM2 SEND_TA TDD cycles without interruption. The MASTER RX should expect the SLAVE TDD transmission may stop briefly ( for a few bursts), before SLAVE starts to transmit the High Rate TDD PAM2 signals( SEND_TA TDD cycles). When SLAVE TX doesn't need to switch rate, it could just pass through SILENT1 state and start SEND_TA transmission( with SEND_TA TDD timing).
The config_timer is proposed to specify the maximum time allowed for SLAVE to reconfigure its transmit circuit. So the expiration of this timer means something is wrong. SLAVE goes back to SILENT0 state, while MASTER stays in TRAINING1 state, until its link_inhibit_timer expires, as what you described. When MASTER enters TRAINING0 state, SLAVE re-achieves its loc_rcvr_status=OK, it enters TRAINING0 state, while restarting its link_inhibit_timer. If your concern is that the previous expiration of link_inhibit_timer may bring the SLAVE from TRAINING1 state back to DISABLE_TRANSMITTER state, we can add a short timer (similar to min_wait_timer, value TBD) to stay in TRAINING0 state, until SLAVE restart link_inhibit_timer.
For SLAVE, the actual exit condition from SILENT1 to TRAINING1 is loc_rcvr_status=OK and transmit_config_done/SEND_TA transmit ready. If this could help to clarify the intention of SILENT1 state, I am OK to add this signal into the proposal.
________________________________________________________________________
To unsubscribe from the STDS-802-3-ISAAC list, click the following link: https://listserv.ieee.org/cgi-bin/wa?SUBED1=STDS-802-3-ISAAC&A=1