diff options
| author | Stanislaw Gruszka <sgruszka@redhat.com> | 2014-06-05 13:52:24 +0200 |
|---|---|---|
| committer | John W. Linville <linville@tuxdriver.com> | 2014-06-19 15:49:15 -0400 |
| commit | ba08910e04e09088cac42ab6d5ceedd1239a3208 (patch) | |
| tree | 39030fe39a0c5a9a9101bc90c641c377ab3b4e19 /drivers/net/wireless/rt2x00/rt2x00queue.h | |
| parent | 283dafa1c69475596701da7767df471c0a71d8fb (diff) | |
| download | linux-stable-ba08910e04e09088cac42ab6d5ceedd1239a3208.tar.gz linux-stable-ba08910e04e09088cac42ab6d5ceedd1239a3208.tar.bz2 linux-stable-ba08910e04e09088cac42ab6d5ceedd1239a3208.zip | |
rt2x00: change beaconing setup on RT2800
As reported by Matthias, on 5572 chip, even if we clear up TXWI
of corresponding beacon, hardware still try to send it or do other
action that increase power consumption peak up to 1A.
To avoid the issue, setup beaconing dynamically by configuring offsets
of currently active beacons and MAC_BSSID_DW1_BSS_BCN_NUM variable,
which limit number of beacons that hardware will try to send.
Reported-by: Matthias Fend <Matthias.Fend@wolfvision.net>
Signed-off-by: Stanislaw Gruszka <sgruszka@redhat.com>
Acked-by: Helmut Schaa <helmut.schaa@googlemail.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
Diffstat (limited to 'drivers/net/wireless/rt2x00/rt2x00queue.h')
| -rw-r--r-- | drivers/net/wireless/rt2x00/rt2x00queue.h | 1 |
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/net/wireless/rt2x00/rt2x00queue.h b/drivers/net/wireless/rt2x00/rt2x00queue.h index c48125be0e34..2233b911a1d7 100644 --- a/drivers/net/wireless/rt2x00/rt2x00queue.h +++ b/drivers/net/wireless/rt2x00/rt2x00queue.h @@ -353,6 +353,7 @@ struct txentry_desc { */ enum queue_entry_flags { ENTRY_BCN_ASSIGNED, + ENTRY_BCN_ENABLED, ENTRY_OWNER_DEVICE_DATA, ENTRY_DATA_PENDING, ENTRY_DATA_IO_FAILED, |