[linux-yocto] [PATCH] iwlwifi: mvm: don't allow sched scans without matches to be started

commit 5e56276e7555b34550d51459a801ff75eca8b907 upstream. The firmware can perform a scheduled scan with not matchsets passed, but it can't send notification that results were found. Since the userspace then cannot know when we got new results and the firmware wouldn't trigger a wake in case we

Re: [linux-yocto] [PATCH] iwlwifi: mvm: don't allow sched scans without matches to be started

Hi Bruce Ashfield, >What kernel version were you targeting with this backport ? It is for kernel 4.1.5. Best Regards Zheng Wu -Original Message- From: Bruce Ashfield [mailto:bruce.ashfi...@windriver.com] Sent: Friday, February 26, 2016 2:52 AM To: Zheng, Wu ;

Re: [linux-yocto] [PATCH] iwlwifi: mvm: don't allow sched scans without matches to be started

On 2016-02-25 1:17 AM, Wu Zheng wrote: commit 5e56276e7555b34550d51459a801ff75eca8b907 upstream. Great! What kernel version were you targeting with this backport ? Bruce The firmware can perform a scheduled scan with not matchsets passed, but it can't send notification that results were

[linux-yocto] [PATCH] iwlwifi: mvm: don't allow sched scans without matches to be started

commit 5e56276e7555b34550d51459a801ff75eca8b907 upstream. The firmware can perform a scheduled scan with not matchsets passed, but it can't send notification that results were found. Since the userspace then cannot know when we got new results and the firmware wouldn't trigger a wake in case we

[linux-yocto] [PATCH] iwlwifi: mvm: don't allow sched scans without matches to be started

The firmware can perform a scheduled scan with not matchsets passed, but it can't send notification that results were found. Since the userspace then cannot know when we got new results and the firmware wouldn't trigger a wake in case we are sleeping, it's better not to allow scans without