From: wi nk <wink@technolu.st>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: ath11k@lists.infradead.org
Subject: Re: ath11k-qca6390-bringup-202012140938: rebate to v5.10 and MHI M2 workaround
Date: Mon, 14 Dec 2020 17:51:41 +0100 [thread overview]
Message-ID: <CAHUdJJXFyNxbf7nBGxw+dsMswcVoxwbQ73U=9=3o+zM7p7kpHg@mail.gmail.com> (raw)
In-Reply-To: <87blew3e4q.fsf@codeaurora.org>
On Mon, Dec 14, 2020 at 10:56 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> (Bcc: people reporting qca6390 problems)
>
> Hi,
>
> there are updates in ath11k-qca6390-bringup branch[1] and the new tag
> is:
>
> ath11k-qca6390-bringup-202012140938
>
> The changes are:
>
> * rebase to v5.10 released last night
>
> * remove unneeded patch "HACK: ath11k: add delays to suspend and resume handlers"
>
> * add wink's workaround for MHI M2 issues: "HACK: mhi: disable M2 state"
>
> * add workaround for 32M firmare memory problem: "HACK: Revert
> "mm/page_alloc: place pages to tail in __free_pages_core()""
>
> * add patch: "ath11k: start vdev if a bss peer is already created"
>
> All feedback very welcome, both positive and negative. You can send
> them privately to me or to the public ath11k list.
>
> Especially I would like to hear how Dell XPS 13 9310 laptops are
> behaving. I'm hoping that ath11k would be usable using this branch,
> without any extra patches or memmap hacks. If I get positive feedback
> my plan is to send "dummy instructions" for a wider audience how to
> use QCA6390 on Dell laptops with Linux.
>
> In the reports try to include at least:
>
> * name of the bringup branch tag you used
>
> * if there are other changes in the kernel, patches, reverts etc
>
> * do you use the memmap kernel parameter
>
> * make and model of the laptop/computer (eg. Dell XPS 13 9310)
>
> * how much testing you did
>
> All feedback is very valuable and gives us guidance on what we need to
> focus on.
>
> Kalle
>
> [1] https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/log/?h=ath11k-qca6390-bringup
>
> --
> https://patchwork.kernel.org/project/linux-wireless/list/
>
> https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
Hi Kalle,
Thanks for the latest tag! I've built and booted it successfully a
number of times. The wifi connection has remained stable and seems to
be behaving nominally. I'll update here as I get some more testing
in.
tag: ath11k-qca6390-bringup-202012140938 , no other changes
hw: dell xps 9310 (13")
ps - I did notice a crash from the btqca driver I didn't see before,
but I'm not sure that's new.
--
ath11k mailing list
ath11k@lists.infradead.org
http://lists.infradead.org/mailman/listinfo/ath11k
next prev parent reply other threads:[~2020-12-14 16:51 UTC|newest]
Thread overview: 20+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-14 9:56 ath11k-qca6390-bringup-202012140938: rebate to v5.10 and MHI M2 workaround Kalle Valo
2020-12-14 12:28 ` Thomas Krause
2020-12-16 7:40 ` Kalle Valo
2020-12-14 16:51 ` wi nk [this message]
2020-12-16 5:41 ` Stephen Liang
2020-12-16 7:46 ` Kalle Valo
2020-12-18 21:27 ` Justin Mazzola Paluska
2020-12-19 16:44 ` Justin Mazzola Paluska
2020-12-19 21:46 ` Justin Mazzola Paluska
2020-12-21 17:11 ` Kalle Valo
2020-12-21 19:25 ` Justin Mazzola Paluska
2021-02-11 11:10 ` ath11k: qca6390 firmware crashes while connecting to 160 MHz channel Kalle Valo
2021-02-11 22:23 ` Justin Mazzola Paluska
2021-02-12 6:16 ` Kalle Valo
2021-02-13 18:36 ` Justin Mazzola Paluska
2021-03-01 7:21 ` Wen Gong
2021-03-01 7:54 ` Kalle Valo
2021-03-01 10:37 ` Wen Gong
2021-03-01 10:55 ` Kalle Valo
2021-05-19 4:14 ` Wen Gong
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='CAHUdJJXFyNxbf7nBGxw+dsMswcVoxwbQ73U=9=3o+zM7p7kpHg@mail.gmail.com' \
--to=wink@technolu.st \
--cc=ath11k@lists.infradead.org \
--cc=kvalo@codeaurora.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;
as well as URLs for NNTP newsgroup(s).