[0/2] wcn36xx: Fixup BMPS

Message ID	20211022140447.2846248-1-bryan.odonoghue@linaro.org
Headers	show Delivered-To: patch@linaro.org Received-SPF: pass (google.com: best guess record for domain of wcn36xx-bounces+patch=linaro.org@lists.infradead.org designates 2607:7c80:54:e::133 as permitted sender) client-ip=2607:7c80:54:e::133; From: Bryan O'Donoghue <bryan.odonoghue@linaro.org> To: kvalo@codeaurora.org, linux-wireless@vger.kernel.org, wcn36xx@lists.infradead.org Cc: loic.poulain@linaro.org, benl@squareup.com, daniel.thompson@linaro.org, bryan.odonoghue@linaro.org Subject: [PATCH 0/2] wcn36xx: Fixup BMPS Date: Fri, 22 Oct 2021 15:04:45 +0100 Message-Id: <20211022140447.2846248-1-bryan.odonoghue@linaro.org> MIME-Version: 1.0 preview: This is a fairly simple set of fixes for BMPS. In the first instance treating a series of BMPS entry fails as a connection loss. Three consecutive entry failures are treated a loss-of-signal. The second is a revert of a disable of BMPS for Open APs. We are finding that with our latest kernels no longer suffer from this bug. Content analysis details: (-0.2 points, 5.0 required) pts rule name description ---- ---------------------- -------------------------------------------------- -0.0 SPF_PASS SPF: sender matches SPF record 0.0 SPF_HELO_NONE SPF: HELO does not publish an SPF Record -0.1 DKIM_VALID_AU Message has a valid DKIM or DK signature from author's domain -0.1 DKIM_VALID Message has at least one valid DKIM or DK signature 0.1 DKIM_SIGNED Message has a DKIM or DK signature, not necessarily valid -0.1 DKIM_VALID_EF Message has a valid DKIM or DK signature from envelope-from domain -0.0 RCVD_IN_DNSWL_NONE RBL: Sender listed at https://www.dnswl.org/, no trust [2a00:1450:4864:20:0:0:0:42a listed in] [list.dnswl.org] Precedence: list Content-Type: text/plain; charset="us-ascii" Content-Transfer-Encoding: 7bit Sender: "wcn36xx" <wcn36xx-bounces@lists.infradead.org> Errors-To: wcn36xx-bounces+patch=linaro.org@lists.infradead.org
Series	wcn36xx: Fixup BMPS \| expand [0/2] wcn36xx: Fixup BMPS [1/2] wcn36xx: Treat repeated BMPS entry fail as connection loss [2/2] Revert "wcn36xx: Disable bmps when encryption is disabled"

Message ID

20211022140447.2846248-1-bryan.odonoghue@linaro.org

Headers

Received-SPF: pass (google.com: best guess record for domain of
	wcn36xx-bounces+patch=linaro.org@lists.infradead.org
	designates 2607:7c80:54:e::133 as permitted sender)
	client-ip=2607:7c80:54:e::133; 
From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: kvalo@codeaurora.org, linux-wireless@vger.kernel.org,
	wcn36xx@lists.infradead.org
Cc: loic.poulain@linaro.org, benl@squareup.com, daniel.thompson@linaro.org, 
	bryan.odonoghue@linaro.org
Subject: [PATCH 0/2] wcn36xx: Fixup BMPS
Date: Fri, 22 Oct 2021 15:04:45 +0100
Message-Id: <20211022140447.2846248-1-bryan.odonoghue@linaro.org>
MIME-Version: 1.0
Precedence: list
Content-Type: text/plain; charset="us-ascii"
Content-Transfer-Encoding: 7bit
Sender: "wcn36xx" <wcn36xx-bounces@lists.infradead.org>
Errors-To: wcn36xx-bounces+patch=linaro.org@lists.infradead.org

Series

wcn36xx: Fixup BMPS | expand

Message

Bryan O'Donoghue Oct. 22, 2021, 2:04 p.m. UTC

This is a fairly simple set of fixes for BMPS. In the first instance
treating a series of BMPS entry fails as a connection loss. Three
consecutive entry failures are treated a loss-of-signal.

The second is a revert of a disable of BMPS for Open APs. We are finding
that with our latest kernels no longer suffer from this bug.

Bryan O'Donoghue (2):
  wcn36xx: Treat repeated BMPS entry fail as connection loss
  Revert "wcn36xx: Disable bmps when encryption is disabled"

 drivers/net/wireless/ath/wcn36xx/main.c    | 10 ----------
 drivers/net/wireless/ath/wcn36xx/pmc.c     | 14 ++++++++++----
 drivers/net/wireless/ath/wcn36xx/wcn36xx.h |  3 ++-
 3 files changed, 12 insertions(+), 15 deletions(-)

-- 
2.33.0


_______________________________________________
wcn36xx mailing list
wcn36xx@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/wcn36xx