SNLA411 October   2022 DP83TC812R-Q1 , DP83TC812S-Q1 , DP83TC813R-Q1 , DP83TC813S-Q1

 

  1.   Abstract
  2.   Trademarks
  3. Introduction
    1. 1.1 System Block Diagram
    2. 1.2 Terminology
  4. TC10 Pin Descriptions
  5. Primary Functions of the PHY
    1. 3.1 Transition from Sleep to Wake-up mode
      1. 3.1.1 Local Wake Detection
      2. 3.1.2 WUP Transmission and Reception
    2. 3.2 Wake Forwarding
    3. 3.3 Transition to Sleep - Sleep Negotiation
      1. 3.3.1 Sleep Ack
      2. 3.3.2 Sleep Request
      3. 3.3.3 Sleep Silent
      4. 3.3.4 Sleep Fail
      5. 3.3.5 Sleep
      6. 3.3.6 Normal State
      7. 3.3.7 Other Transitions
        1. 3.3.7.1 Forced Sleep
        2. 3.3.7.2 Activity during Sleep Negotiation
        3. 3.3.7.3 Link Down during Sleep Negotiation
        4. 3.3.7.4 Sleep Silent to Standby
  6. Relevant Registers
  7. Power Supply Recommendation
    1. 5.1 Core Supply Network Recommendation
    2. 5.2 Networks with Shared Core Supplies
  8. Sequence of Events and Timing
    1. 6.1 Local Wake Timing
    2. 6.2 Remote Wake Timing
    3. 6.3 Successful Sleep Negotiation Timing
    4. 6.4 Sleep Abort Timing
    5. 6.5 WUR Timing
  9. Ethernet Network Wake-up
  10. Configuration for non-TC10 Applications
  11. Additional Features
    1. 9.1 WUR Initiation Through WAKE Pin
    2. 9.2 Programmable Wake-Forward Pulse Width
  12. 10Conclusion

Transition to Sleep - Sleep Negotiation

Sleep negotiation can be initiated from one of the two PHYs connected through link-up. Post the initiation, both of these PHYs go through negotiation and smoothly transition to sleep.

The sleep negotiation can be initiated (local sleep req) by programming reg<0x018C> = 0x0002 on any of the PHYs.
Note: Sleep can only be initiated when there is active link between the PHYs. Programming 0x018C = 0x0002 without the link-up will make the PHY initiate sleep immediately after the link is up.

The states the PHYs go through in the negotiation are explained in detail below.

Figure 3-1 Sleep State Diagram

The MAC/controller intervention is only needed to initiate the sleep and abort the Sleep. All other state transitions happen though interaction between both the PHYs and need no external intervention and are explained below for information purpose only.