diff mbox

ath10k: Disable PCI power save for QCA99X0

Message ID 1441088612-9517-1-git-send-email-c_traja@qti.qualcomm.com (mailing list archive)
State Changes Requested
Headers show

Commit Message

c_traja@qti.qualcomm.com Sept. 1, 2015, 6:23 a.m. UTC
From: Tamizh chelvam <c_traja@qti.qualcomm.com>

Frequent failures in waking up the target is observed during
interface (mostly observed with AP and Monitor mode) bring up
on x86, this failures lead to firmware crash. Disabling PCI
power save fixes this issue. Disabling ASPM also does not help,
as a work around disable PCI power save for QCA99X0.

The following kernel log is seen when this issue happens

kworker/dying (667) used greatest stack depth: 12208 bytes left
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x00040050: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a02c: -110
ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xfffffffe at 0x0004a02c: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a034: -110
ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xfffff81f at 0x0004a034: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a02c: -110
ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xffffffe1 at 0x0004a02c: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a42c: -110
ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xfffffffe at 0x0004a42c: -110
ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a434: -110
ath10k_pci 0000:07:00.0: firmware crashed! (uuid 40b345f1-db3d-4b97-bc54-6572994e02d5)

Signed-off-by: Tamizh chelvam <c_traja@qti.qualcomm.com>
---
 drivers/net/wireless/ath/ath10k/pci.c | 12 ++++++++++++
 1 file changed, 12 insertions(+)

Comments

Michal Kazior Sept. 1, 2015, 7:36 a.m. UTC | #1
On 1 September 2015 at 08:23,  <c_traja@qti.qualcomm.com> wrote:
> From: Tamizh chelvam <c_traja@qti.qualcomm.com>
>
> Frequent failures in waking up the target is observed during
> interface (mostly observed with AP and Monitor mode) bring up
> on x86, this failures lead to firmware crash. Disabling PCI
> power save fixes this issue. Disabling ASPM also does not help,
> as a work around disable PCI power save for QCA99X0.
>
> The following kernel log is seen when this issue happens
>
> kworker/dying (667) used greatest stack depth: 12208 bytes left
> ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x00040050: -110
> ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a02c: -110
> ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xfffffffe at 0x0004a02c: -110
> ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a034: -110
> ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xfffff81f at 0x0004a034: -110
> ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a02c: -110
> ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xffffffe1 at 0x0004a02c: -110
> ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a42c: -110
> ath10k_pci 0000:07:00.0: failed to wake target for write32 of 0xfffffffe at 0x0004a42c: -110
> ath10k_pci 0000:07:00.0: failed to wake target for read32 at 0x0004a434: -110
> ath10k_pci 0000:07:00.0: firmware crashed! (uuid 40b345f1-db3d-4b97-bc54-6572994e02d5)
>
> Signed-off-by: Tamizh chelvam <c_traja@qti.qualcomm.com>
> ---
>  drivers/net/wireless/ath/ath10k/pci.c | 12 ++++++++++++
>  1 file changed, 12 insertions(+)
>
> diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
> index 1046ab6..1ab4ee7 100644
> --- a/drivers/net/wireless/ath/ath10k/pci.c
> +++ b/drivers/net/wireless/ath/ath10k/pci.c
> @@ -1640,6 +1640,10 @@ static void ath10k_pci_hif_stop(struct ath10k *ar)
>         ath10k_pci_safe_chip_reset(ar);
>
>         ath10k_pci_irq_disable(ar);
> +
> +       if (QCA_REV_99X0(ar))
> +               ath10k_pci_sleep(ar);
> +

This re-introduces an issue that was originally fixed once
320e14b8db51 ("ath10k: fix some pci wake/sleep issues").

E.g. if you have shared irqs between ath10k and another NIC and ath10k
is put down then if the other NIC generates an interrupt ath10k will
read out its interrupt CSR as 0xdeadbeef which in turn will confuse
the driver and consume the interrupt preventing the other NIC driver
from working properly.

Also think of WoWLAN.


Micha?
diff mbox

Patch

diff --git a/drivers/net/wireless/ath/ath10k/pci.c b/drivers/net/wireless/ath/ath10k/pci.c
index 1046ab6..1ab4ee7 100644
--- a/drivers/net/wireless/ath/ath10k/pci.c
+++ b/drivers/net/wireless/ath/ath10k/pci.c
@@ -1640,6 +1640,10 @@  static void ath10k_pci_hif_stop(struct ath10k *ar)
 	ath10k_pci_safe_chip_reset(ar);
 
 	ath10k_pci_irq_disable(ar);
+
+	if (QCA_REV_99X0(ar))
+		ath10k_pci_sleep(ar);
+
 	ath10k_pci_irq_sync(ar);
 	ath10k_pci_flush(ar);
 
@@ -2315,6 +2319,14 @@  static int ath10k_pci_hif_power_up(struct ath10k *ar)
 
 	ath10k_dbg(ar, ATH10K_DBG_BOOT, "boot hif power up\n");
 
+	if (QCA_REV_99X0(ar)) {
+		ret = ath10k_pci_wake(ar);
+		if (ret) {
+			ath10k_warn(ar, "failed to wake target for qca99x0: %d\n", ret);
+			return ret;
+		}
+	}
+
 	pcie_capability_read_word(ar_pci->pdev, PCI_EXP_LNKCTL,
 				  &ar_pci->link_ctl);
 	pcie_capability_write_word(ar_pci->pdev, PCI_EXP_LNKCTL,