From: Kalle Valo <kvalo@kernel.org>
To: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
Cc: <ath11k@lists.infradead.org>, <robh@kernel.org>,
<krzysztof.kozlowski+dt@linaro.org>,
<linux-wireless@vger.kernel.org>, <devicetree@vger.kernel.org>
Subject: Re: [PATCH v3 2/2] ath11k: Add WoW support for WCN6750
Date: Fri, 02 Sep 2022 15:22:51 +0300 [thread overview]
Message-ID: <87h71qartw.fsf@kernel.org> (raw)
In-Reply-To: <20220902112520.24804-3-quic_mpubbise@quicinc.com> (Manikanta Pubbisetty's message of "Fri, 2 Sep 2022 16:55:20 +0530")
Manikanta Pubbisetty <quic_mpubbise@quicinc.com> writes:
> Add support for WoW on WCN6750 chipset.
>
> 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
>
> Signed-off-by: Manikanta Pubbisetty <quic_mpubbise@quicinc.com>
In the future please always add "wifi:" to wireless patches. No need to
resend because of this, I can fix it.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2022-09-02 12:29 UTC|newest]
Thread overview: 7+ messages / expand[flat|nested] mbox.gz Atom feed top
2022-09-02 11:25 [PATCH v3 0/2] Add WoW support for WCN6750 Manikanta Pubbisetty
2022-09-02 11:25 ` [PATCH v3 1/2] dt: bindings: net: add bindings to add WoW support on WCN6750 Manikanta Pubbisetty
2022-09-08 13:10 ` Krzysztof Kozlowski
2022-09-19 13:03 ` Kalle Valo
2022-09-02 11:25 ` [PATCH v3 2/2] ath11k: Add WoW support for WCN6750 Manikanta Pubbisetty
2022-09-02 12:22 ` Kalle Valo [this message]
2022-09-10 6:59 ` Kalle Valo
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=87h71qartw.fsf@kernel.org \
--to=kvalo@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=devicetree@vger.kernel.org \
--cc=krzysztof.kozlowski+dt@linaro.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_mpubbise@quicinc.com \
--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).