LAN9116 Datasheet, PDF (90/109 Pages) SMSC Corporation – Highly Efficient Single-Chip 10/100 Non-PCI Ethernet Controller

LAN9116
6.0 TIMING DIAGRAMS
6.1 Host Interface Timing
The LAN9116 supports the following host cycles:
Read Cycles:
• PIO Reads (nCS or nRD controlled)
• PIO Burst Reads (nCS or nRD controlled)
• RX Data FIFO Direct PIO Reads (nCS or nRD controlled)
• RX Data FIFO Direct PIO Burst Reads (nCS or nRD controlled)
Write Cycles:
• PIO writes (nCS and nWR controlled)
• TX Data FIFO direct PIO writes (nCS or nWR controlled)
6.1.1 SPECIAL RESTRICTIONS ON BACK-TO-BACK WRITE/READ CYCLES
It is important to note that there are specific restrictions on the timing of back-to-back write-read operations. These
restrictions concern reading the control registers after any write cycle to the LAN9116 device. In many cases there is a
required minimum delay between writing to the LAN9116, and the subsequent side effect (change in the control register
value). For example, when writing to the TX Data FIFO, it takes up to 135ns for the level indication to change in the
TX_FIFO_INF register.
In order to prevent the host from reading stale data after a write operation, minimum wait periods must be enforced.
These periods are specified in Table 6-1, "Read After Write Timing Rules". The host processor is required to wait the
specified period of time after any write to the LAN9116 before reading the resource specified in the table. These wait
periods are for read operations that immediately follow any write cycle. Note that the required wait period is dependent
upon the register being read after the write.
Performing "dummy" reads of the BYTE_TEST register is a convenient way to ensure that the minimum write-to-read
timing restriction is met. Table 6-1 also shows the number of dummy reads that are required before reading the register
indicated. The number of BYTE_TEST reads in this table is based on the minimum timing for Tcycle (165ns). For micro-
processors with slower busses the number of reads may be reduced as long as the total time is equal to, or greater than
the time specified in the table. Note that dummy reads of the BYTE_TEST register are not required as long as the min-
imum time period is met.
TABLE 6-1: READ AFTER WRITE TIMING RULES
Register Name
Minimum Wait Time for Read Following
Any Write Cycle
(in ns)
ID_REV
0
IRQ_CFG
165
INT_STS
165
INT_EN
165
BYTE_TEST
0
FIFO_INT
165
RX_CFG
165
TX_CFG
165
HW_CFG
165
RX_DP_CTRL
165
RX_FIFO_INF
0
TX_FIFO_INF
165
Number of BYTE_TEST Reads
(Assuming T_cycle of 165ns)
0
1
1
1
0
1
1
1
1
1
0
1
DS00002268A-page 90
 2005-2016 Microchip Technology Inc.