From: Brian Norris <briannorris@chromium.org>
To: Kalle Valo <kvalo@qca.qualcomm.com>, Kalle Valo <kvalo@codeaurora.org>
Cc: ath10k@lists.infradead.org, linux-wireless@vger.kernel.org,
Grant Grundler <grundler@chromium.org>,
linux-kernel@vger.kernel.org, Ryan Hsu <ryanhsu@qti.qualcomm.com>,
Michal Kazior <michal.kazior@tieto.com>
Subject: Re: [PATCH] ath10k: fix core PCI suspend when WoWLAN is supported but disabled
Date: Wed, 11 Oct 2017 17:38:06 -0700 [thread overview]
Message-ID: <20171012003805.GA89253@google.com> (raw)
In-Reply-To: <20170919232416.108247-1-briannorris@chromium.org>
Ping? Any comments? I know there's more than one way to slice this
problem, but it's most definitely a problem...
Brian
On Tue, Sep 19, 2017 at 04:24:16PM -0700, Brian Norris wrote:
> For devices where the FW supports WoWLAN but user-space has not
> configured it, we don't do any PCI-specific suspend/resume operations,
> because mac80211 doesn't call drv_suspend() when !wowlan. This has
> particularly bad effects for some platforms, because we don't stop the
> power-save timer, and if this timer goes off after the PCI controller
> has suspended the link, Bad Things will happen.
>
> Commit 32faa3f0ee50 ("ath10k: add the PCI PM core suspend/resume ops")
> got some of this right, in that it understood there was a problem on
> non-WoWLAN firmware. But it forgot the $subject case.
>
> Fix this by moving all the PCI driver suspend/resume logic exclusively
> into the driver PM hooks. This shouldn't affect WoWLAN support much
> (this just gets executed later on).
>
> I would just as well kill the entirety of ath10k_hif_suspend(), as it's
> not even implemented on the USB or SDIO drivers. I expect that we don't
> need the callback, except to return "supported" (i.e., 0) or "not
> supported" (i.e., -EOPNOTSUPP).
>
> Fixes: 32faa3f0ee50 ("ath10k: add the PCI PM core suspend/resume ops")
> Fixes: 77258d409ce4 ("ath10k: enable pci soc powersaving")
> Signed-off-by: Brian Norris <briannorris@chromium.org>
> Cc: Ryan Hsu <ryanhsu@qti.qualcomm.com>
> Cc: Kalle Valo <kvalo@qca.qualcomm.com>
> Cc: Michal Kazior <michal.kazior@tieto.com>
> ---
> drivers/net/wireless/ath/ath10k/pci.c | 24 ++++++++++++++----------
> 1 file changed, 14 insertions(+), 10 deletions(-)
>
> diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
> index bc1633945a56..4655c944e3fd 100644
> --- a/drivers/net/wireless/ath/ath10k/pci.c
> +++ b/drivers/net/wireless/ath/ath10k/pci.c
> @@ -2580,6 +2580,12 @@ void ath10k_pci_hif_power_down(struct ath10k *ar)
> #ifdef CONFIG_PM
>
> static int ath10k_pci_hif_suspend(struct ath10k *ar)
> +{
> + /* Nothing to do; the important stuff is in the driver suspend. */
> + return 0;
> +}
> +
> +static int ath10k_pci_suspend(struct ath10k *ar)
> {
> /* The grace timer can still be counting down and ar->ps_awake be true.
> * It is known that the device may be asleep after resuming regardless
> @@ -2592,6 +2598,12 @@ static int ath10k_pci_hif_suspend(struct ath10k *ar)
> }
>
> static int ath10k_pci_hif_resume(struct ath10k *ar)
> +{
> + /* Nothing to do; the important stuff is in the driver resume. */
> + return 0;
> +}
> +
> +static int ath10k_pci_resume(struct ath10k *ar)
> {
> struct ath10k_pci *ar_pci = ath10k_pci_priv(ar);
> struct pci_dev *pdev = ar_pci->pdev;
> @@ -3403,11 +3415,7 @@ static int ath10k_pci_pm_suspend(struct device *dev)
> struct ath10k *ar = dev_get_drvdata(dev);
> int ret;
>
> - if (test_bit(ATH10K_FW_FEATURE_WOWLAN_SUPPORT,
> - ar->running_fw->fw_file.fw_features))
> - return 0;
> -
> - ret = ath10k_hif_suspend(ar);
> + ret = ath10k_pci_suspend(ar);
> if (ret)
> ath10k_warn(ar, "failed to suspend hif: %d\n", ret);
>
> @@ -3419,11 +3427,7 @@ static int ath10k_pci_pm_resume(struct device *dev)
> struct ath10k *ar = dev_get_drvdata(dev);
> int ret;
>
> - if (test_bit(ATH10K_FW_FEATURE_WOWLAN_SUPPORT,
> - ar->running_fw->fw_file.fw_features))
> - return 0;
> -
> - ret = ath10k_hif_resume(ar);
> + ret = ath10k_pci_resume(ar);
> if (ret)
> ath10k_warn(ar, "failed to resume hif: %d\n", ret);
>
> --
> 2.14.1.690.gbb1197296e-goog
>
next prev parent reply other threads:[~2017-10-12 0:38 UTC|newest]
Thread overview: 11+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-09-19 23:24 [PATCH] ath10k: fix core PCI suspend when WoWLAN is supported but disabled Brian Norris
2017-10-12 0:38 ` Brian Norris [this message]
2017-10-12 0:43 ` Adrian Chadd
2017-10-12 3:58 ` Kalle Valo
2017-10-13 11:37 ` Kalle Valo
2017-10-19 14:32 ` Kalle Valo
2017-10-19 17:12 ` Brian Norris
2017-10-19 18:45 ` [PATCH] ath10k: fix build errors with !CONFIG_PM Brian Norris
2017-10-20 6:29 ` Kalle Valo
2017-10-27 13:44 ` Kalle Valo
2017-10-20 6:24 ` ath10k: fix core PCI suspend when WoWLAN is supported but disabled 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=20171012003805.GA89253@google.com \
--to=briannorris@chromium.org \
--cc=ath10k@lists.infradead.org \
--cc=grundler@chromium.org \
--cc=kvalo@codeaurora.org \
--cc=kvalo@qca.qualcomm.com \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=michal.kazior@tieto.com \
--cc=ryanhsu@qti.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).