From: Bryan O'Donoghue <bryan.odonoghue@linaro.org>
To: kvalo@codeaurora.org, wcn36xx@lists.infradead.org,
linux-wireless@vger.kernel.org
Cc: bryan.odonoghue@linaro.org, shawn.guo@linaro.org,
loic.poulain@linaro.org
Subject: [PATCH 0/3] wcn36xx: Firmware link monitor/keepalive offload
Date: Sat, 31 Oct 2020 02:23:08 +0000 [thread overview]
Message-ID: <20201031022311.1677337-1-bryan.odonoghue@linaro.org> (raw)
This patchset enables various firmware offload features for
- Link keepalive
- Link monitoring
Keepalive is a necessary precursor for an upcoming series on
wake on wlan, since we need to inform the firmware to keep the link up in
suspend.
Testing shows that LINK_FAIL_TX_CNT is a link monitor enable field. Once
set to non-zero link monitoring becomes active. This series activates
CONNECTION_MONITOR after enabling LINK_FAIL_TX_CNT thus offloading link
monitoring to the firmware.
Bryan O'Donoghue (3):
wcn36xx: Set LINK_FAIL_TX_CNT non zero on wcn3620/wcn3660
wcn36xx: Enable firmware link monitoring
wcn36xx: Enable firmware offloaded keepalive
drivers/net/wireless/ath/wcn36xx/main.c | 3 +++
drivers/net/wireless/ath/wcn36xx/smd.c | 1 +
2 files changed, 4 insertions(+)
--
2.28.0
next reply other threads:[~2020-10-31 2:22 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-10-31 2:23 Bryan O'Donoghue [this message]
2020-10-31 2:23 ` [PATCH 1/3] wcn36xx: Set LINK_FAIL_TX_CNT non zero on wcn3620/wcn3660 Bryan O'Donoghue
2020-10-31 9:33 ` Loic Poulain
2020-10-31 12:48 ` Bryan O'Donoghue
2020-10-31 2:23 ` [PATCH 2/3] wcn36xx: Enable firmware link monitoring Bryan O'Donoghue
2020-10-31 9:57 ` Loic Poulain
2020-10-31 13:02 ` Bryan O'Donoghue
2020-11-02 19:15 ` Loic Poulain
2020-10-31 2:23 ` [PATCH 3/3] wcn36xx: Enable firmware offloaded keepalive Bryan O'Donoghue
2020-10-31 9:39 ` Loic Poulain
2020-10-31 12:54 ` Bryan O'Donoghue
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=20201031022311.1677337-1-bryan.odonoghue@linaro.org \
--to=bryan.odonoghue@linaro.org \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=loic.poulain@linaro.org \
--cc=shawn.guo@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).