summaryrefslogtreecommitdiff
path: root/drivers/net/wireless/ath/ath10k/wow.h
diff options
context:
space:
mode:
authorRyan Hsu <ryanhsu@qti.qualcomm.com>2017-08-31 15:36:16 +0300
committerKalle Valo <kvalo@qca.qualcomm.com>2017-08-31 21:17:04 +0300
commit393b706cf20c2b612ca88fb2e48b43e3e376796f (patch)
treef7a2d1f99fdd9a53e156a1e11141ae629f653af9 /drivers/net/wireless/ath/ath10k/wow.h
parent32faa3f0ee509176aeac0009e3ee93f9b15f07a5 (diff)
ath10k: configure and enable the wakeup capability
ACPI will rely on device driver to tell it if the device could support wakeup function when system in D3 state. This has caused some platform can't support remote wakeup correctly, because the ACPI wakeup GPE is not enabled, hence registers the .set_wakeup callback to handle it if device supports wakeup. Tested with QCA6174 hw3.0, firmware ('WLAN.RM.4.4.1-00008-QCARMSWP-1') Signed-off-by: Ryan Hsu <ryanhsu@qti.qualcomm.com> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
Diffstat (limited to 'drivers/net/wireless/ath/ath10k/wow.h')
-rw-r--r--drivers/net/wireless/ath/ath10k/wow.h1
1 files changed, 1 insertions, 0 deletions
diff --git a/drivers/net/wireless/ath/ath10k/wow.h b/drivers/net/wireless/ath/ath10k/wow.h
index abbb04b6d1bd..9745b9ddc7f5 100644
--- a/drivers/net/wireless/ath/ath10k/wow.h
+++ b/drivers/net/wireless/ath/ath10k/wow.h
@@ -28,6 +28,7 @@ int ath10k_wow_init(struct ath10k *ar);
int ath10k_wow_op_suspend(struct ieee80211_hw *hw,
struct cfg80211_wowlan *wowlan);
int ath10k_wow_op_resume(struct ieee80211_hw *hw);
+void ath10k_wow_op_set_wakeup(struct ieee80211_hw *hw, bool enabled);
#else