From: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
To: <ath11k@lists.infradead.org>
Cc: <linux-wireless@vger.kernel.org>, <devicetree@vger.kernel.org>,
<robh@kernel.org>,
Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
Subject: [PATCH v2 0/2] Add WoW support for WCN6750
Date: Mon, 29 Aug 2022 18:13:21 +0530 [thread overview]
Message-ID: <20220829124323.26874-1-quic_mpubbise@quicinc.com> (raw)
Add WoW support for WCN6750.
Unlike other chips where WoW exit happens after sending WoW wakeup
WMI command, exit from WoW suspend in the case of WCN6750 happens
upon sending a WoW exit SMP2P (Shared memory point to point) message
to the firmware.
Tested-on: WCN6750 hw1.0 AHB WLAN.MSL.1.0.1-00887-QCAMSLSWPLZ-1
Manikanta Pubbisetty (2):
dt: bindings: net: add bindings to add WoW support for WCN6750
ath11k: Add WoW support for WCN6750
---
V2:
- Replaced shift/mask operation with u32_encode_bits() before sending SMP2P message
- Rebased on ToT COMMIT SHA-ID: f60b230094cbf88c73808709e4f9c1cf09eb0b01
.../bindings/net/wireless/qcom,ath11k.yaml | 17 +++
drivers/net/wireless/ath/ath11k/ahb.c | 123 +++++++++++++++++-
drivers/net/wireless/ath/ath11k/ahb.h | 16 +++
drivers/net/wireless/ath/ath11k/core.c | 7 +
drivers/net/wireless/ath/ath11k/hw.h | 1 +
drivers/net/wireless/ath/ath11k/pcic.c | 32 +++++
drivers/net/wireless/ath/ath11k/pcic.h | 4 +
drivers/net/wireless/ath/ath11k/wow.c | 8 ++
8 files changed, 207 insertions(+), 1 deletion(-)
--
2.37.1
next reply other threads:[~2022-08-29 12:55 UTC|newest]
Thread overview: 5+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-08-29 12:43 Manikanta Pubbisetty [this message]
2022-08-29 12:43 ` [PATCH v2 1/2] dt: bindings: net: add bindings to add WoW support for WCN6750 Manikanta Pubbisetty
2022-08-30 17:25 ` Krzysztof Kozlowski
2022-09-02 5:25 ` Manikanta Pubbisetty
2022-08-29 12:43 ` [PATCH v2 2/2] ath11k: Add " Manikanta Pubbisetty
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=20220829124323.26874-1-quic_mpubbise@quicinc.com \
--to=quic_mpubbise@quicinc.com \
--cc=ath11k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=robh@kernel.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).