From: Kalle Valo <kvalo@codeaurora.org>
To: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
Cc: linux-wireless@vger.kernel.org, wcn36xx@lists.infradead.org,
linux-arm-msm@vger.kernel.org, loic.poulain@linaro.org,
benl@squareup.com, bryan.odonoghue@linaro.org
Subject: Re: [PATCH] wcn36xx: Indicate beacon not connection loss on MISSED_BEACON_IND
Date: Mon, 1 Nov 2021 14:19:37 +0000 (UTC) [thread overview]
Message-ID: <163577637326.7461.17837845723571403340.kvalo@codeaurora.org> (raw)
In-Reply-To: <20211027232529.657764-1-bryan.odonoghue@linaro.org>
Bryan O'Donoghue <bryan.odonoghue@linaro.org> wrote:
> Firmware can trigger a missed beacon indication, this is not the same as a
> lost signal.
>
> Flag to Linux the missed beacon and let the WiFi stack decide for itself if
> the link is up or down by sending its own probe to determine this.
>
> We should only be signalling the link is lost when the firmware indicates
>
> Fixes: 8e84c2582169 ("wcn36xx: mac80211 driver for Qualcomm WCN3660/WCN3680 hardware")
> Signed-off-by: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
> Signed-off-by: Kalle Valo <kvalo@codeaurora.org>
Patch applied to ath-next branch of ath.git, thanks.
588b45c88ae1 wcn36xx: Indicate beacon not connection loss on MISSED_BEACON_IND
--
https://patchwork.kernel.org/project/linux-wireless/patch/20211027232529.657764-1-bryan.odonoghue@linaro.org/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-11-01 14:19 UTC|newest]
Thread overview: 2+ messages / expand[flat|nested] mbox.gz Atom feed top
2021-10-27 23:25 [PATCH] wcn36xx: Indicate beacon not connection loss on MISSED_BEACON_IND Bryan O'Donoghue
2021-11-01 14:19 ` Kalle Valo [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=163577637326.7461.17837845723571403340.kvalo@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=benl@squareup.com \
--cc=bryan.odonoghue@linaro.org \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=wcn36xx@lists.infradead.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox;
as well as URLs for NNTP newsgroup(s).