aboutsummaryrefslogtreecommitdiffstats
path: root/drivers/pcmcia/yenta_socket.h
diff options
context:
space:
mode:
authorLennert Buytenhek <buytenh@wantstofly.org>2008-07-14 16:56:55 -0400
committerLennert Buytenhek <buytenh@marvell.com>2008-07-24 00:22:42 -0400
commit8fa89bf5de066b11190ac804903021700c2b1185 (patch)
tree78bbb31e5aaddf9c9ad214705bfbb08b85576f36 /drivers/pcmcia/yenta_socket.h
parentc010b2f76c3032e48097a6eef291d8593d5d79a6 (diff)
mv643xx_eth: fix TX hang erratum workaround
The previously merged TX hang erratum workaround ("mv643xx_eth: work around TX hang hardware issue") assumes that TX_END interrupts are delivered simultaneously with or after their corresponding TX interrupts, but this is not always true in practise. In particular, it appears that TX_END interrupts are issued as soon as descriptor fetch returns an invalid descriptor, which may happen before earlier descriptors have been fully transmitted and written back to memory as being done. This hardware behavior can lead to a situation where the current driver code mistakenly assumes that the MAC has given up transmitting before noticing the packets that it is in fact still currently working on, causing the driver to re-kick the transmit queue, which will only cause the MAC to re-fetch the invalid head descriptor, and generate another TX_END interrupt, et cetera, until the packets in the pipe finally finish transmitting and have their descriptors written back to memory, which will then finally break the loop. Fix this by having the erratum workaround not check the 'number of unfinished descriptor', but instead, to compare the software's idea of what the head descriptor pointer should be to the hardware's head descriptor pointer (which is updated on the same conditions as the TX_END interupt is generated on, i.e. possibly before all previous descriptors have been transmitted and written back). Signed-off-by: Lennert Buytenhek <buytenh@marvell.com>
Diffstat (limited to 'drivers/pcmcia/yenta_socket.h')
0 files changed, 0 insertions, 0 deletions