From: Kalle Valo <kvalo@qca.qualcomm.com>
To: "Guilherme Íscaro" <cabelitostos@gmail.com>
Cc: Ryan Hsu <ryanhsu@qti.qualcomm.com>,
"ath10k@lists.infradead.org" <ath10k@lists.infradead.org>
Subject: Re: Reporting a bug for QCA6174 802.11ac
Date: Fri, 31 Mar 2017 11:12:37 +0000 [thread overview]
Message-ID: <87tw69r97f.fsf@kamboji.qca.qualcomm.com> (raw)
In-Reply-To: <CAAf+CsCKx3p=TdWZxbSi9JRfKUicCqyAUaP-Kzxgj1N6XK0WqQ@mail.gmail.com> ("Guilherme \=\?utf-8\?Q\?\=C3\=8Dscaro\=22's\?\= message of "Tue, 28 Mar 2017 14:45:59 -0300")
Guilherme Íscaro <cabelitostos@gmail.com> writes:
> I would like to inform that I "fixed" the problem. After my last
> email, I cloned the linux repo and started to hack around the driver
> source code. By looking at the dmesg output that I provided to you
> guys, I noticed that for some reason the board was not being properly
> awake ( ath10k_pci_wake_wait() returns ETIMEOUT). I so sick with this
> problem that I hardcoded "ar_pci->pci_ps" to false, thus the board
> can't sleep now.
Sounds like a problem with your PCI bus or the platform/laptop so try
different PCI settings both on BIOS and kernel. I have seen lots of talk
about ASPM, especially with some iwlwifi devices, so you should also
investigate about that.
Please let us know if you find anything, it's always valuable
information. Have fun googling :)
--
Kalle Valo
_______________________________________________
ath10k mailing list
ath10k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath10k
next prev parent reply other threads:[~2017-03-31 11:13 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2017-03-20 15:31 Reporting a bug for QCA6174 802.11ac Guilherme Íscaro
2017-03-21 18:35 ` Ryan Hsu
2017-03-21 18:58 ` Guilherme Íscaro
2017-03-22 13:56 ` Guilherme Íscaro
2017-03-22 22:17 ` Guilherme Íscaro
2017-03-23 22:46 ` Ryan Hsu
2017-03-23 23:11 ` Guilherme Íscaro
2017-03-28 17:45 ` Guilherme Íscaro
2017-03-31 11:12 ` Kalle Valo [this message]
2017-03-31 15:11 ` Adrian Chadd
2017-04-05 19:48 ` Guilherme Íscaro
2017-04-06 3:52 ` 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=87tw69r97f.fsf@kamboji.qca.qualcomm.com \
--to=kvalo@qca.qualcomm.com \
--cc=ath10k@lists.infradead.org \
--cc=cabelitostos@gmail.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.