From: Kalle Valo <kvalo@qca.qualcomm.com>
To: Maya Erez <qca_merez@qca.qualcomm.com>
Cc: Kalle Valo <kvalo@codeaurora.org>,
Lazar Alexei <QCA_ailizaro@QCA.qualcomm.com>,
<linux-wireless@vger.kernel.org>, <wil6210@qca.qualcomm.com>,
Maya Erez <qca_merez@qca.qualcomm.com>
Subject: Re: [v3,01/12] wil6210: run-time PM when interface down
Date: Sat, 2 Dec 2017 15:23:43 +0100 [thread overview]
Message-ID: <adcde2a0d5074b1f98251ef6a0acfeee@euamsexm01a.eu.qualcomm.com> (raw)
In-Reply-To: <1510665944-30198-2-git-send-email-qca_merez@qca.qualcomm.com>
Maya Erez <qca_merez@qca.qualcomm.com> wrote:
> Allow run-time suspend when interface is down, keep card alive when
> interface is up.
> If driver is in wmi only or debug_fw mode run-time PM won't suspend.
>
> Signed-off-by: Lazar Alexei <qca_ailizaro@qca.qualcomm.com>
> Signed-off-by: Maya Erez <qca_merez@qca.qualcomm.com>
> Signed-off-by: Kalle Valo <kvalo@qca.qualcomm.com>
12 patches applied to ath-next branch of ath.git, thanks.
94162666cd51 wil6210: run-time PM when interface down
5fad7241e821 wil6210: print human readable names of WMI commands and events
3ead1e016c25 wil6210: refresh FW capabilities during interface up
144a12a6d83f wil6210: abort properly in cfg suspend
26a6d5274865 wil6210: fix length check in __wmi_send
705d2fde94b2 wil6210: add block size checks during FW load
b5a8ffcae410 wil6210: missing length check in wmi_set_ie
51a58709495b wil6210: missing length check in wil_cfg80211_mgmt_tx
6804cd101c50 wil6210: get suspend reject reason and resume triggers from FW
680c242dc25e wil6210: fix PCIe bus mastering in case of interface down
05898dd98830 wil6210: remove suspend time statistics
bd8bdc6ca818 wil6210: update statistics for suspend
--
https://patchwork.kernel.org/patch/10057625/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
next prev parent reply other threads:[~2017-12-02 14:23 UTC|newest]
Thread overview: 14+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-11-14 13:25 [PATCH v3 00/12] wil6210 patches Maya Erez
2017-11-14 13:25 ` [PATCH v3 01/12] wil6210: run-time PM when interface down Maya Erez
2017-12-02 14:23 ` Kalle Valo [this message]
2017-11-14 13:25 ` [PATCH v3 02/12] wil6210: print human readable names of WMI commands and events Maya Erez
2017-11-14 13:25 ` [PATCH v3 03/12] wil6210: refresh FW capabilities during interface up Maya Erez
2017-11-14 13:25 ` [PATCH v3 04/12] wil6210: abort properly in cfg suspend Maya Erez
2017-11-14 13:25 ` [PATCH v3 05/12] wil6210: fix length check in __wmi_send Maya Erez
2017-11-14 13:25 ` [PATCH v3 06/12] wil6210: add block size checks during FW load Maya Erez
2017-11-14 13:25 ` [PATCH v3 07/12] wil6210: missing length check in wmi_set_ie Maya Erez
2017-11-14 13:25 ` [PATCH v3 08/12] wil6210: missing length check in wil_cfg80211_mgmt_tx Maya Erez
2017-11-14 13:25 ` [PATCH v3 09/12] wil6210: get suspend reject reason and resume triggers from FW Maya Erez
2017-11-14 13:25 ` [PATCH v3 10/12] wil6210: fix PCIe bus mastering in case of interface down Maya Erez
2017-11-14 13:25 ` [PATCH v3 11/12] wil6210: remove suspend time statistics Maya Erez
2017-11-14 13:25 ` [PATCH v3 12/12] wil6210: update statistics for suspend Maya Erez
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=adcde2a0d5074b1f98251ef6a0acfeee@euamsexm01a.eu.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=QCA_ailizaro@QCA.qualcomm.com \
--cc=kvalo@codeaurora.org \
--cc=linux-wireless@vger.kernel.org \
--cc=qca_merez@qca.qualcomm.com \
--cc=wil6210@qca.qualcomm.com \
/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).