Re: Ordering Dell XPS 13 9310 to test QCA6390

From: Kalle Valo <kvalo@codeaurora.org>
To: Justin Mazzola Paluska <jmp@justinmp.com>
Cc: "Luo, Sining" <sluo@ciena.com>,
	"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: Fri, 12 Feb 2021 09:14:08 +0200	[thread overview]
Message-ID: <87ft21sqpr.fsf@codeaurora.org> (raw)
In-Reply-To: <ef858ed0-b561-cf30-8741-bb3d85b22d83@justinmp.com> (Justin Mazzola Paluska's message of "Sat, 16 Jan 2021 09:10:58 -0500")

Justin Mazzola Paluska <jmp@justinmp.com> writes:

> On 1/13/21 1:29 PM, Luo, Sining wrote:
>> 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
>>
>
>
> For what it's worth, I upgraded my Dell XPS 13 9310 to BIOS 1.2.5 and
> can also report that the DMAR error is gone and I also get 32 MSI
> vectors.
>
> $ sudo dmesg | grep -e ath11k\\\|mhi
> [   17.317099] ath11k_pci 0000:56:00.0: WARNING: ath11k PCI support is
> experimental!
> [   17.317153] ath11k_pci 0000:56:00.0: BAR 0: assigned [mem
> 0x8c300000-0x8c3fffff 64bit]
> [   17.317170] ath11k_pci 0000:56:00.0: enabling device (0000 -> 0002)
> [   17.317336] ath11k_pci 0000:56:00.0: MSI vectors: 32
> [   17.375022] mhi 0000:56:00.0: Requested to power ON
> [   17.375181] mhi 0000:56:00.0: Power on setup success
> [   17.945671] ath11k_pci 0000:56:00.0: qmi req mem_seg[0] 0x33000000
> 3522560 1
> [   17.945675] ath11k_pci 0000:56:00.0: qmi req mem_seg[1] 0x33500000
> 884736 4
> [   17.953054] ath11k_pci 0000:56:00.0: chip_id 0x0 chip_family 0xb
> board_id 0xff soc_id 0xffffffff
> [   17.953056] ath11k_pci 0000:56:00.0: fw_version 0x101c06cc
> fw_build_timestamp 2020-06-24 19:50 fw_build_id
> [   18.127165] ath11k_pci 0000:56:00.0 wlp86s0: renamed from wlan0
>
> I'm still using the ath11k-qca6390-bringup-202012140938 branch.  I'm
> happy to try out new patches, particularly ones related to power
> management.  The laptop doesn't get into states lower than pc6 while
> the wireless card is running.  If I shut down the card, the laptop
> will opportunistically get down into the pc10 state, which leads to
> massive power savings.

I'm not familiar with pc states, do you have any pointers? How do you
check the states yourself?

At the moment in suspend we leave the firmware running in low power
state due to problems in MHI. The ideal state would be to power off the
firmware entirely, but that needs changes in MHI. But I suspect you are
not talking about suspend.

-- 
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