ATH11K Archive on lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: ath11k@lists.infradead.org
Subject: Re: ath11k-qca6390-bringup-202011191920: new suspend implementation
Date: Thu, 19 Nov 2020 21:52:26 +0200	[thread overview]
Message-ID: <87o8jtt98l.fsf@codeaurora.org> (raw)
In-Reply-To: <87sg95t9ez.fsf@codeaurora.org> (Kalle Valo's message of "Thu, 19 Nov 2020 21:48:36 +0200")

Kalle Valo <kvalo@codeaurora.org> writes:

> (Bcc: people reporting qca6390 problems)
>
> Hi,
>
> I collected all important QCA6390 fixes to ath11k-qca6390 branch so that
> there's a good baseline for all testing:
>
> https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/log/?h=ath11k-qca6390-bringup
>
> At the moment it's based on v5.10-rc4 and I will try to update it to a
> recent -rc release every few weeks or so. Everytime I update the branch
> I create a new tag and the latest tag is now:
>
> ath11k-qca6390-bringup-202011191920
>
> In this tag there's now a brand new implementation for suspend, which
> relies that the platform provides power to QCA6390 during suspend. Not
> all platforms do, but most of them should do that. ath11k also prints a
> warning whenever it notices that the firmware has crashed, but I'm not
> sure yet if it (the MHI subsystem to be exact) can detect every case.
>
> The MSI patch is mostly the same, it had just some refactoring since the
> last version. Unfortunately there's no solution still for the weird
> crashes some people are seeing.

Forgot to mention when debugging ath11k PCI issues it's a good idea to
enable MHI debug messages. To do that enable CONFIG_MHI_BUS_DEBUG and
CONFIG_DYNAMIC_DEBUG and run:

sudo sh -c "echo -n 'module mhi +p' > /sys/kernel/debug/dynamic_debug/control"

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

-- 
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k

  reply	other threads:[~2020-11-19 19:52 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-11-19 19:48 ath11k-qca6390-bringup-202011191920: new suspend implementation Kalle Valo
2020-11-19 19:52 ` Kalle Valo [this message]
2020-11-19 22:00   ` Pavel Procopiuc
2020-11-19 22:11     ` wi nk
2020-11-19 23:08       ` wi nk
2020-11-20 16:01         ` Kalle Valo
2020-11-20 16:59           ` wi nk
2020-11-20  8:16       ` Pavel Procopiuc
2020-11-20  9:40     ` Kalle Valo
2020-11-20 10:24       ` Pavel Procopiuc
2020-11-20 15:56         ` Kalle Valo
2020-11-21 23:44   ` Mitchell Nordine
2020-11-22 13:15     ` Mitchell Nordine
2020-11-22 15:07       ` wi nk
2020-11-23  3:14         ` wi nk
2020-11-23 23:30           ` wi nk
2020-11-23 23:38             ` wi nk
2020-11-26 22:45               ` wi nk
2020-12-02 18:51 ` Pavel Procopiuc

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=87o8jtt98l.fsf@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.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