lwn.git/drivers/net/wireless/iwlwifi/mvm/power.c, branch docs-fixes

iwlwifi: move under intel vendor directory

2015-11-18T12:28:30+00:00

Part of reorganising wireless drivers directory and Kconfig. Signed-off-by: Kalle Valo

iwlwifi: mvm: use short timeouts in P2P low latency if supported

2015-10-25T11:45:03+00:00

Those timeouts are used for AM-to-PSM transition. We already have those pairs defined for default and WOWLAN use cases. We expect that by using shorter threshold for low latency P2P, e.g. for Miracast video scenario, we might save a considerable amount of power. Signed-off-by: Johannes Berg Signed-off-by: Avri Altman Signed-off-by: Emmanuel Grumbach

iwlwifi: mvm: use wowlan RX/TX timeouts in D0i3

2015-10-25T11:45:03+00:00

In "hostless" mode (D3 or D0i3) the same parameters were intended to be used, but the code doesn't do that properly. Fix it. Signed-off-by: Johannes Berg Signed-off-by: Avri Altman Signed-off-by: Emmanuel Grumbach

iwlwifi: mvm: stop using DEVICE_POWER_FLAGS_CAM_MSK

2015-10-05T11:33:28+00:00

The firmware has always treated these two bits to mean that powersave is enabled when POWER_SAVE_ENA is set and CAM is clear; it doesn't use them in any non-combined way. Therefore, it's pointless to send it two bits, and the API should be cleaned up. Prepare the driver by removing the CAM bit and using only POWER_SAVE_ENA to indicate whether PS is enabled or not. Signed-off-by: Johannes Berg Signed-off-by: Luca Coelho

iwlwifi: mvm: correct skip-over-DTIM implementation

2015-10-05T09:28:50+00:00

The formula used in D0i3 should also be used in D3, instead of the hardcoded value. Additionally, the formula is actually wrong - if the calculation yields 0 then 1 should be used instead of disabling entirely. Also need to add 1 since the firmware needs 3 to skip 2, etc. To make all this clearer, centralize the calculation into a single function. Signed-off-by: Johannes Berg Signed-off-by: Luca Coelho

iwlwifi: mvm: Enable power management on low-latency bss

2015-08-16T07:37:12+00:00

Currently the driver disable power management on all low-latency interfaces, while it should disable it on WiDi interfaces only. Non-P2P interfaces that runs voice and video traffic should enable power management. Signed-off-by: Avri Altman Signed-off-by: Emmanuel Grumbach

iwlwifi: mvm: revert to our old skip over dtim policy

2015-08-04T18:29:39+00:00

Our firmware scheduler used to suffer from false wake-up on 500 time units. We had to came up with a formula to address this buggy behavior. Now that our firmware is fixed, we can go back to our old policy. Signed-off-by: Avri Altman Signed-off-by: Emmanuel Grumbach

iwlwifi: mvm: ignore CQM when setting beacon filtering in D0i3 enter flow

2015-08-04T07:11:50+00:00

CQM overwrites a few thresholds in the bf command. On the other hand, when entering D0i3 the thresholds are set to higher values on purpose, so ignore CQM in this case. Signed-off-by: Gregory Greenman Signed-off-by: Emmanuel Grumbach

iwlwifi: mvm: remove command/return value from RX handlers

2015-08-04T07:11:41+00:00

In the mvm driver, neither the old command nor the return value are used, so remove them. Signed-off-by: Johannes Berg Signed-off-by: Emmanuel Grumbach

Merge tag 'iwlwifi-next-for-kalle-2015-03-12' of https://git.kernel.org/pub/scm/linux/kernel/git/iwlwifi/iwlwifi-next

2015-03-13T13:09:18+00:00

* Location Aware Regulatory was added by Arik * 8000 device family work * Update to the BT Coex firmware API