All of lore.kernel.org
 help / color / mirror / Atom feed
From: Kalle Valo <kvalo@codeaurora.org>
To: "Luo\, Sining" <sluo@ciena.com>
Cc: "ath11k@lists.infradead.org" <ath11k@lists.infradead.org>,
	"wink@technolu.st" <wink@technolu.st>,
	"mail@mitchellnordine.com" <mail@mitchellnordine.com>
Subject: Re: Ordering Dell XPS 13 9310 to test QCA6390
Date: Wed, 13 Jan 2021 19:05:33 +0200	[thread overview]
Message-ID: <874kjkix7m.fsf_-_@codeaurora.org> (raw)
In-Reply-To: <075eed74b59afc9bc4f870aea6765f85d040cf47.camel@ciena.com> (Sining Luo's message of "Wed, 13 Jan 2021 15:22:31 +0000")

"Luo, Sining" <sluo@ciena.com> writes:

> On Wed, 2021-01-13 at 13:02 +0100, wi nk wrote:
>> On Wed, Jan 13, 2021 at 12:54 PM Kalle Valo <kvalo@codeaurora.org>
>> wrote:
>> > 
>> > wi nk <wink@technolu.st> writes:
>> > 
>> > > > 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
>> > > 
>> > >   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.
>> > 
>> > Makes sense, better to be careful.
>> > 
>> > > 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?
>> > 
>> > I have not tested these yet as I only did a quick 10 minute test. I
>> > was
>> > offline over two weeks so I have a lot of catching up to do, but
>> > will
>> > get back to you in next few days on these. My plan is to also test
>> > this
>> > new BIOS with the official 5.10 release from Linus (tag v5.10).
>> > 
>> > --
>> > https://urldefense.com/v3/__https://patchwork.kernel.org/project/linux-wireless/list/__;!!OSsGDw!d42JFwn6tITykEUQ6ZYtfIMif5BRPdVt_zOqCzoINc640OzwSHusv5X588g$
>> >  
>> > 
>> > https://urldefense.com/v3/__https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches__;!!OSsGDw!d42JFwn6tITykEUQ6ZYtfIMif5BRPdVt_zOqCzoINc640OzwSHusay1hmvY$
>> >  
>> 
>> Awesome, let me know how it goes.  I've got the 9310 branch running
>> 5.10.2 with no issues (16 days uptime) so I wouldn't expect you to see
>> anything super new there, good luck :D.
>> 
>> ps - Happy new year
>> 
>
> Hi Kalle and Wi,
>
> I've upgraded my 9310 BIOS to the same 1.1.4 since it's available:
>
> [    0.000000] DMI: Dell Inc. XPS 13 9310/0F7M4C, BIOS 1.1.4 11/23/2020
>
> But it's still getting a single MSI vector:
>
> [    3.143712] ath11k_pci 0000:56:00.0: WARNING: ath11k PCI support is
> experimental!
> [    3.143794] ath11k_pci 0000:56:00.0: BAR 0: assigned [mem 0x8c300000-
> 0x8c3fffff 64bit]
> [    3.143811] ath11k_pci 0000:56:00.0: enabling device (0000 -> 0002)
> [    3.143885] ath11k_pci 0000:56:00.0: MSI vectors: 1
> [    3.755747] ath11k_pci 0000:56:00.0: qmi req mem_seg[0] 0x57400000
> 3522560 1
> [    3.755748] ath11k_pci 0000:56:00.0: qmi req mem_seg[1] 0x54d00000
> 884736 4
> [    3.764110] ath11k_pci 0000:56:00.0: chip_id 0x0 chip_family 0xb
> board_id 0xff soc_id 0xffffffff
> [    3.764111] ath11k_pci 0000:56:00.0: fw_version 0x101c06cc
> fw_build_timestamp 2020-06-24 19:50 fw_build_id 
> [    3.933936] ath11k_pci 0000:56:00.0 wlp86s0: renamed from wlan0
>
> Does it mean that the single MSI issue is not from the BIOS? 

Do you have vt-d enabled in BIOS? IIRC that's needed for 32 vectors.

-- 
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:[~2021-01-13 17:05 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
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 [this message]
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=874kjkix7m.fsf_-_@codeaurora.org \
    --to=kvalo@codeaurora.org \
    --cc=ath11k@lists.infradead.org \
    --cc=mail@mitchellnordine.com \
    --cc=sluo@ciena.com \
    --cc=wink@technolu.st \
    /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.