Ordering Dell XPS 13 9310 to test QCA6390

Wed Jan 13 13:29:11 EST 2021

On Wed, 2021-01-13 at 19:05 +0200, Kalle Valo wrote:
> "Luo, Sining" <sluo at 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 at codeaurora.org>
> > > wrote:
> > > > 
> > > > wi nk <wink at 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.
> 

Yes, it was enabled in BIOS, but it wasn't enabled at boot due to the
BIOS bug:
DMAR: [Firmware Bug]: Your BIOS is broken; DMAR reported at address 0!

I went ahead to upgrade the BIOS to 1.2.5. The DMAR error is now gone
and I can get 32 MSI vectors for the first time!

[    3.971218] ath11k_pci 0000:72:00.0: WARNING: ath11k PCI support is
experimental!
[    3.971285] ath11k_pci 0000:72:00.0: BAR 0: assigned [mem 0xa2500000-
0xa25fffff 64bit]
[    3.971302] ath11k_pci 0000:72:00.0: enabling device (0000 -> 0002)
[    3.971452] ath11k_pci 0000:72:00.0: MSI vectors: 32
[    4.609593] ath11k_pci 0000:72:00.0: qmi req mem_seg[0] 0x53c00000
3522560 1
[    4.609595] ath11k_pci 0000:72:00.0: qmi req mem_seg[1] 0x54100000
884736 4
[    4.616396] ath11k_pci 0000:72:00.0: chip_id 0x0 chip_family 0xb
board_id 0xff soc_id 0xffffffff
[    4.616398] ath11k_pci 0000:72:00.0: fw_version 0x101c06cc
fw_build_timestamp 2020-06-24 19:50 fw_build_id 
[    4.793650] ath11k_pci 0000:72:00.0 wlp114s0: renamed from wlan0