summaryrefslogtreecommitdiffstats
path: root/drivers/net/wireless/ath/ath5k/attach.c
diff options
context:
space:
mode:
authorBruno Randolf <br1@einfach.org>2010-09-17 11:37:07 +0900
committerJohn W. Linville <linville@tuxdriver.com>2010-09-21 11:05:15 -0400
commit234132960dcf8ebd9d424d92a4dfb0e57fa63a17 (patch)
tree8cb08ec25b181921f9912f72cde3762549a3c520 /drivers/net/wireless/ath/ath5k/attach.c
parent923e5b3d3d773b9956b943ac64f782d5a127bdea (diff)
downloadop-kernel-dev-234132960dcf8ebd9d424d92a4dfb0e57fa63a17.zip
op-kernel-dev-234132960dcf8ebd9d424d92a4dfb0e57fa63a17.tar.gz
ath5k: Keep last descriptor in queue
If we return a TX descriptor to the pool of available descriptors, while a queues TXDP still points to it we could potentially run into all sorts of troube. It has been suggested that there is hardware which can set the descriptors done bit before it reads ds_link and moves on to the next descriptor. While the documentation says this is not true for newer chipsets (the descriptor contents are copied to some internal memory), we don't know about older hardware. To be safe, we always keep the last descriptor in the queue, and avoid dangling TXDP pointers. Unfortunately this does not fully resolve the problem - queues still get stuck! This is similar to what ath9k does. Signed-off-by: Bruno Randolf <br1@einfach.org> Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/wireless/ath/ath5k/attach.c')
0 files changed, 0 insertions, 0 deletions
OpenPOWER on IntegriCloud