| commit | db7ec38d8e99f449856c11ffaef363a8eb5af90f | |
| author | Mohammed Shafi Shajakhan <mshajakhan@atheros.com> | |
| Wed, 22 Dec 2010 06:50:12 +0000 (22 12:20 +0530) | ||
| committer | John W. Linville <linville@tuxdriver.com> | |
| Wed, 22 Dec 2010 20:44:22 +0000 (22 15:44 -0500) | ||
| tree | 41f0833fff19d7e7127a0cc795cedc9f465f8208 | treesnapshot (tar.gz zip) |
| parent | e6d8a817d00793eecd063b1548bbc954ab62b124 | commitdiff |
ath9k: Reset keycache on resume
It looks like some hardware registers are left into undefined state
after suspend/resume. At minimum, this can cause odd issues related to
key cache and hardware trying to encrypt/decrypt frames unexpectedly.
This seems to happen even when there is no keys configured, i.e., hardware
can end up touching TX frames just based of invalid key cache context
even if the driver is not asking a specific entry to be used. In
addition, RX can likely be affected. This patch fixes this issue.
Signed-off-by: Jouni Malinen <Jouni.Malinen@Atheros.com>
Signed-off-by: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
It looks like some hardware registers are left into undefined state
after suspend/resume. At minimum, this can cause odd issues related to
key cache and hardware trying to encrypt/decrypt frames unexpectedly.
This seems to happen even when there is no keys configured, i.e., hardware
can end up touching TX frames just based of invalid key cache context
even if the driver is not asking a specific entry to be used. In
addition, RX can likely be affected. This patch fixes this issue.
Signed-off-by: Jouni Malinen <Jouni.Malinen@Atheros.com>
Signed-off-by: Mohammed Shafi Shajakhan <mshajakhan@atheros.com>
Signed-off-by: John W. Linville <linville@tuxdriver.com>
| drivers/net/wireless/ath/ath9k/ath9k.h | diffblobblamehistory | |
| drivers/net/wireless/ath/ath9k/init.c | diffblobblamehistory | |
| drivers/net/wireless/ath/ath9k/pci.c | diffblobblamehistory |