ath11k.lists.infradead.org archive mirror
 help / color / mirror / Atom feed
From: wi nk <wink@technolu.st>
To: Kalle Valo <kvalo@codeaurora.org>
Cc: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>,
	Mitchell Nordine <mail@mitchellnordine.com>
Subject: Re: Ordering Dell XPS 13 9310 to test QCA6390
Date: Wed, 13 Jan 2021 11:40:21 +0100	[thread overview]
Message-ID: <CAHUdJJWpHWznHOhdtuRjbH2tr9F5kagGUbNsFO_f7MfY=w_3Gg@mail.gmail.com> (raw)
In-Reply-To: <87h7nli16d.fsf@codeaurora.org>

On Wed, Jan 13, 2021 at 11:25 AM Kalle Valo <kvalo@codeaurora.org> wrote:
>
> Kalle Valo <kvalo@codeaurora.org> writes:
>
> > Mitchell Nordine <mail@mitchellnordine.com> writes:
> >
> >>> But I have now ordered Dell XPS 13 laptop and I should get it in
> >> three weeks, keeping fingers crossed. That should make things easier
> >> as I can test patches myself.
> >>
> >> Hi Kalle, you may already be aware of this, but I just wanted to make sure!
> >>
> >> Not all Dell XPS 13 9310 laptops come with the AX500 connectivity chip
> >> (the one that uses the QCA6390). It seems that only the models with
> >> 32GB RAM tend to come with the AX500 wifi chip.
> >>
> >> Most models appear to come with the AX1650 which I believe uses a
> >> totally different chip and driver that is already well supported in
> >> Linux.
> >>
> >> It might be worth double-checking the model that you have ordered has the AX500.
> >
> > I had heard about that so I did order the 32 GB RAM model and multiple
> > times specified that I only want AX500. So I'm optimistic that I should
> > get the right chip, but you never know how it goes :)
>
> I got the XPS 13 9310 now and it indeed had AX500. But it also has an
> updated BIOS:
>
> [    0.000000] DMI: Dell Inc. XPS 13 9310/0MRT12, BIOS 1.1.4 11/23/2020
>
> And with that I can get 32 MSI vectors:
>
> [    2.758219] ath11k_pci 0000:56:00.0: WARNING: ath11k PCI support is experimental!
> [    2.758778] ath11k_pci 0000:56:00.0: BAR 0: assigned [mem 0x8c300000-0x8c3fffff 64bit]
> [    2.758797] ath11k_pci 0000:56:00.0: enabling device (0000 -> 0002)
> [    2.759086] ath11k_pci 0000:56:00.0: MSI vectors: 32
> [    3.208447] ath11k_pci 0000:56:00.0: qmi req mem_seg[0] 0x3f000000 3522560 1
> [    3.208449] ath11k_pci 0000:56:00.0: qmi req mem_seg[1] 0x3f500000 884736 4
> [    3.215355] ath11k_pci 0000:56:00.0: chip_id 0x0 chip_family 0xb board_id 0xff soc_id 0xffffffff
> [    3.215358] ath11k_pci 0000:56:00.0: fw_version 0x101c06cc fw_build_timestamp 2020-06-24 19:50 fw_build_id
>
> --
> 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

Kalle,

  I did see the updated BIOS from a few weeks ago, but I've been a
little hesitant to update since I wasn't sure what would happen or if
I could downgrade.  So to confirm, the new BIOS is allowing the driver
to obtain all 32 msi vectors removing the need for the single MSI
patching?  Does the MHI / M2 behavior also change to work properly?

Thanks!

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

  reply	other threads:[~2021-01-13 10:40 UTC|newest]

Thread overview: 21+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2020-12-16 14:41 Ordering Dell XPS 13 9310 to test QCA6390 Mitchell Nordine
2020-12-16 15:46 ` Kalle Valo
2021-01-13 10:25   ` Kalle Valo
2021-01-13 10:40     ` wi nk [this message]
2021-01-13 11:54       ` Kalle Valo
2021-01-13 12:02         ` wi nk
2021-01-13 15:22           ` [**EXTERNAL**] " Luo, Sining
2021-01-13 17:05             ` Kalle Valo
2021-01-13 18:29               ` Luo, Sining
2021-01-16 14:10                 ` Justin Mazzola Paluska
2021-02-12  7:14                   ` Kalle Valo
2021-02-13 19:10                     ` Justin Mazzola Paluska
2021-02-22 16:10           ` Kalle Valo
2021-02-24  9:14             ` Stelian Pop
2021-02-24 21:33               ` Justin Mazzola Paluska
2021-02-24 22:02                 ` Stelian Pop
2021-02-24 22:38                   ` Justin Mazzola Paluska
2021-02-25  8:21                     ` Stelian Pop
2021-03-06 20:22                     ` Wren Turkal
2021-03-06 20:49                       ` Stelian Pop
2021-03-07  4:48                         ` Wren Turkal

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='CAHUdJJWpHWznHOhdtuRjbH2tr9F5kagGUbNsFO_f7MfY=w_3Gg@mail.gmail.com' \
    --to=wink@technolu.st \
    --cc=ath11k@lists.infradead.org \
    --cc=kvalo@codeaurora.org \
    --cc=mail@mitchellnordine.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).