5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Wren Turkal]

I have no device for the wifi on my computer. 5.13 worked pretty well. I 
also found others reporting similar issues:
https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362

Here's info about the hardware on my laptop:
➜  ~ sudo dmidecode -s system-product-name
XPS 13 9310

➜  ~ sudo dmidecode -s bios-version
3.0.4

➜  ~ sudo lspci -s 72:00 -vvv
72:00.0 Unassigned class [ff00]: Qualcomm QCA6390 Wireless Network 
Adapter [AX500-DBS (2x2)]
	Subsystem: Rivet Networks Device a501
	Control: I/O- Mem+ BusMaster+ SpecCycle- MemWINV- VGASnoop- ParErr- 
Stepping- SERR- FastB2B- DisINTx+
	Status: Cap+ 66MHz- UDF- FastB2B- ParErr- DEVSEL=fast >TAbort- <TAbort- 
<MAbort- >SERR- <PERR- INTx-
	Latency: 0
	Interrupt: pin ? routed to IRQ 179
	Region 0: Memory at a2500000 (64-bit, non-prefetchable) [size=1M]
	Capabilities: [40] Power Management version 3
		Flags: PMEClk- DSI- D1- D2- AuxCurrent=0mA PME(D0+,D1-,D2-,D3hot+,D3cold+)
		Status: D0 NoSoftRst+ PME-Enable- DSel=0 DScale=0 PME-
	Capabilities: [50] MSI: Enable+ Count=32/32 Maskable+ 64bit-
		Address: fee00c18  Data: 0000
		Masking: fffffc00  Pending: 00000000
	Capabilities: [70] Express (v2) Endpoint, MSI 00
		DevCap:	MaxPayload 128 bytes, PhantFunc 0, Latency L0s unlimited, L1 
unlimited
			ExtTag- AttnBtn- AttnInd- PwrInd- RBE+ FLReset- SlotPowerLimit 10.000W
		DevCtl:	CorrErr- NonFatalErr- FatalErr- UnsupReq-
			RlxdOrd+ ExtTag- PhantFunc- AuxPwr- NoSnoop+
			MaxPayload 128 bytes, MaxReadReq 512 bytes
		DevSta:	CorrErr+ NonFatalErr- FatalErr- UnsupReq+ AuxPwr+ TransPend-
		LnkCap:	Port #0, Speed 8GT/s, Width x1, ASPM L0s L1, Exit Latency L0s 
<1us, L1 <64us
			ClockPM- Surprise- LLActRep- BwNot- ASPMOptComp+
		LnkCtl:	ASPM Disabled; RCB 64 bytes, Disabled- CommClk+
			ExtSynch- ClockPM- AutWidDis- BWInt- AutBWInt-
		LnkSta:	Speed 5GT/s (downgraded), Width x1 (ok)
			TrErr- Train- SlotClk+ DLActive- BWMgmt- ABWMgmt-
		DevCap2: Completion Timeout: Range ABCD, TimeoutDis+ NROPrPrP- LTR+
			 10BitTagComp- 10BitTagReq- OBFF Not Supported, ExtFmt- EETLPPrefix-
			 EmergencyPowerReduction Not Supported, EmergencyPowerReductionInit-
			 FRS- TPHComp+ ExtTPHComp-
			 AtomicOpsCap: 32bit- 64bit- 128bitCAS-
		DevCtl2: Completion Timeout: 50us to 50ms, TimeoutDis- LTR+ OBFF Disabled,
			 AtomicOpsCtl: ReqEn-
		LnkCap2: Supported Link Speeds: 2.5-8GT/s, Crosslink- Retimer- 
2Retimers- DRS-
		LnkCtl2: Target Link Speed: 5GT/s, EnterCompliance- SpeedDis-
			 Transmit Margin: Normal Operating Range, EnterModifiedCompliance- 
ComplianceSOS-
			 Compliance De-emphasis: -6dB
		LnkSta2: Current De-emphasis Level: -6dB, EqualizationComplete- 
EqualizationPhase1-
			 EqualizationPhase2- EqualizationPhase3- LinkEqualizationRequest-
			 Retimer- 2Retimers- CrosslinkRes: unsupported
	Capabilities: [100 v2] Advanced Error Reporting
		UESta:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
		UEMsk:	DLP- SDES- TLP- FCP- CmpltTO- CmpltAbrt- UnxCmplt- RxOF- 
MalfTLP- ECRC- UnsupReq- ACSViol-
		UESvrt:	DLP+ SDES+ TLP- FCP+ CmpltTO- CmpltAbrt- UnxCmplt- RxOF+ 
MalfTLP+ ECRC- UnsupReq- ACSViol-
		CESta:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		CEMsk:	RxErr- BadTLP- BadDLLP- Rollover- Timeout- AdvNonFatalErr+
		AERCap:	First Error Pointer: 00, ECRCGenCap+ ECRCGenEn- ECRCChkCap+ 
ECRCChkEn-
			MultHdrRecCap- MultHdrRecEn- TLPPfxPres- HdrLogCap-
		HeaderLog: 00000000 00000000 00000000 00000000
	Capabilities: [148 v1] Secondary PCI Express
		LnkCtl3: LnkEquIntrruptEn- PerformEqu-
		LaneErrStat: 0
	Capabilities: [158 v1] Transaction Processing Hints
		No steering table available
	Capabilities: [1e4 v1] Latency Tolerance Reporting
		Max snoop latency: 3145728ns
		Max no snoop latency: 3145728ns
	Capabilities: [1ec v1] L1 PM Substates
		L1SubCap: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+ L1_PM_Substates+
			  PortCommonModeRestoreTime=70us PortTPowerOnTime=0us
		L1SubCtl1: PCI-PM_L1.2+ PCI-PM_L1.1+ ASPM_L1.2+ ASPM_L1.1+
			   T_CommonMode=0us LTR1.2_Threshold=98304ns
		L1SubCtl2: T_PwrOn=44us
	Kernel driver in use: ath11k_pci
	Kernel modules: ath11k_pci

Thanks for all the dev on this,
wt
-- 
You're more amazing than you think! ymatyt.com

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

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

(adding linux-wireless, regressions and some mhi folks)

Wren Turkal <wt@penguintechs.org> writes:

> I have no device for the wifi on my computer. 5.13 worked pretty well.
> I also found others reporting similar issues:
> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
>
> Here's info about the hardware on my laptop:
> ➜  ~ sudo dmidecode -s system-product-name
> XPS 13 9310
>
> ➜  ~ sudo dmidecode -s bios-version
> 3.0.4

Do you get the same mhi error as in the forum post?

qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22

MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
v5.14-rc6 kernel right now.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

(adding linux-wireless, regressions and some mhi folks)

Wren Turkal <wt@penguintechs.org> writes:

> I have no device for the wifi on my computer. 5.13 worked pretty well.
> I also found others reporting similar issues:
> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
>
> Here's info about the hardware on my laptop:
> ➜  ~ sudo dmidecode -s system-product-name
> XPS 13 9310
>
> ➜  ~ sudo dmidecode -s bios-version
> 3.0.4

Do you get the same mhi error as in the forum post?

qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22

MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
v5.14-rc6 kernel right now.

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

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Nicolas Schichan]

On 23/08/2021 14:53, Kalle Valo wrote:
> (adding linux-wireless, regressions and some mhi folks)
> 
> Wren Turkal <wt@penguintechs.org> writes:
> 
>> I have no device for the wifi on my computer. 5.13 worked pretty well.
>> I also found others reporting similar issues:
>> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
>>
>> Here's info about the hardware on my laptop:
>> ➜  ~ sudo dmidecode -s system-product-name
>> XPS 13 9310
>>
>> ➜  ~ sudo dmidecode -s bios-version
>> 3.0.4
> 
> Do you get the same mhi error as in the forum post?
> 
> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
> 
> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
> v5.14-rc6 kernel right now.

Hello,

I have hit the same issue on Linux 5.14-rc7:

[   14.780566] qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22

This looks to be caused by commit:

ce78ffa3ef16 net: really fix the build...

Reverting this commit results in ath11k being able to load without errors.

Regards,

-- 
Nicolas Schichan

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Nicolas Schichan]

On 23/08/2021 14:53, Kalle Valo wrote:
> (adding linux-wireless, regressions and some mhi folks)
> 
> Wren Turkal <wt@penguintechs.org> writes:
> 
>> I have no device for the wifi on my computer. 5.13 worked pretty well.
>> I also found others reporting similar issues:
>> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
>>
>> Here's info about the hardware on my laptop:
>> ➜  ~ sudo dmidecode -s system-product-name
>> XPS 13 9310
>>
>> ➜  ~ sudo dmidecode -s bios-version
>> 3.0.4
> 
> Do you get the same mhi error as in the forum post?
> 
> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
> 
> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
> v5.14-rc6 kernel right now.

Hello,

I have hit the same issue on Linux 5.14-rc7:

[   14.780566] qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22

This looks to be caused by commit:

ce78ffa3ef16 net: really fix the build...

Reverting this commit results in ath11k being able to load without errors.

Regards,

-- 
Nicolas Schichan


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

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

(Adding Dave and Jakub to CC)

Nicolas Schichan <nschichan@freebox.fr> writes:

> On 23/08/2021 14:53, Kalle Valo wrote:
>> (adding linux-wireless, regressions and some mhi folks)
>> 
>> Wren Turkal <wt@penguintechs.org> writes:
>> 
>>> I have no device for the wifi on my computer. 5.13 worked pretty well.
>>> I also found others reporting similar issues:
>>> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
>>>
>>> Here's info about the hardware on my laptop:
>>> ➜  ~ sudo dmidecode -s system-product-name
>>> XPS 13 9310
>>>
>>> ➜  ~ sudo dmidecode -s bios-version
>>> 3.0.4
>> 
>> Do you get the same mhi error as in the forum post?
>> 
>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>> 
>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
>> v5.14-rc6 kernel right now.
>
> Hello,
>
> I have hit the same issue on Linux 5.14-rc7:
>
> [   14.780566] qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>
> This looks to be caused by commit:
>
> ce78ffa3ef16 net: really fix the build...
>
> Reverting this commit results in ath11k being able to load without errors.

Thanks, this helps a lot. Commit ce78ffa3ef16 was introduced in
v5.14-rc5 so I assume that's the first release which broke ath11k.

Dave, what build issue did you fix with commit ce78ffa3ef16? Could we
revert the commit? The problem is that, unless we fix this issue, with
v5.14 WLAN will be broken on a quite few newer Dell laptops.

Unfortunately I'm travelling right now and I'm not able to look at this
in detail until Thursday or so. And I assume Linus will make the final
v5.14 release on Sunday so we are on a tight schedule :/

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

(Adding Dave and Jakub to CC)

Nicolas Schichan <nschichan@freebox.fr> writes:

> On 23/08/2021 14:53, Kalle Valo wrote:
>> (adding linux-wireless, regressions and some mhi folks)
>> 
>> Wren Turkal <wt@penguintechs.org> writes:
>> 
>>> I have no device for the wifi on my computer. 5.13 worked pretty well.
>>> I also found others reporting similar issues:
>>> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
>>>
>>> Here's info about the hardware on my laptop:
>>> ➜  ~ sudo dmidecode -s system-product-name
>>> XPS 13 9310
>>>
>>> ➜  ~ sudo dmidecode -s bios-version
>>> 3.0.4
>> 
>> Do you get the same mhi error as in the forum post?
>> 
>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>> 
>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
>> v5.14-rc6 kernel right now.
>
> Hello,
>
> I have hit the same issue on Linux 5.14-rc7:
>
> [   14.780566] qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>
> This looks to be caused by commit:
>
> ce78ffa3ef16 net: really fix the build...
>
> Reverting this commit results in ath11k being able to load without errors.

Thanks, this helps a lot. Commit ce78ffa3ef16 was introduced in
v5.14-rc5 so I assume that's the first release which broke ath11k.

Dave, what build issue did you fix with commit ce78ffa3ef16? Could we
revert the commit? The problem is that, unless we fix this issue, with
v5.14 WLAN will be broken on a quite few newer Dell laptops.

Unfortunately I'm travelling right now and I'm not able to look at this
in detail until Thursday or so. And I assume Linus will make the final
v5.14 release on Sunday so we are on a tight schedule :/

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

[regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

(Adding Linus and Greg)

Kalle Valo <kvalo@codeaurora.org> writes:

> (Adding Dave and Jakub to CC)
>
> Nicolas Schichan <nschichan@freebox.fr> writes:
>
>> On 23/08/2021 14:53, Kalle Valo wrote:
>>> (adding linux-wireless, regressions and some mhi folks)
>>> 
>>> Wren Turkal <wt@penguintechs.org> writes:
>>> 
>>>> I have no device for the wifi on my computer. 5.13 worked pretty well.
>>>> I also found others reporting similar issues:
>>>> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
>>>>
>>>> Here's info about the hardware on my laptop:
>>>> ➜  ~ sudo dmidecode -s system-product-name
>>>> XPS 13 9310
>>>>
>>>> ➜  ~ sudo dmidecode -s bios-version
>>>> 3.0.4
>>> 
>>> Do you get the same mhi error as in the forum post?
>>> 
>>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>>> 
>>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
>>> v5.14-rc6 kernel right now.
>>
>> Hello,
>>
>> I have hit the same issue on Linux 5.14-rc7:
>>
>> [   14.780566] qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>>
>> This looks to be caused by commit:
>>
>> ce78ffa3ef16 net: really fix the build...
>>
>> Reverting this commit results in ath11k being able to load without errors.
>
> Thanks, this helps a lot. Commit ce78ffa3ef16 was introduced in
> v5.14-rc5 so I assume that's the first release which broke ath11k.
>
> Dave, what build issue did you fix with commit ce78ffa3ef16? Could we
> revert the commit? The problem is that, unless we fix this issue, with
> v5.14 WLAN will be broken on a quite few newer Dell laptops.

I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
really fix the build...")[1] is for handling a conflict between net-next
and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
mhi: Add inbound buffers allocation flag"). Greg mentions this in a
commit[2]:

commit 813272ed5238b37c81e448b302048e8008570121
Merge: de0534df9347 36a21d51725a
Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    Merge 5.14-rc5 into char-misc-next
    
    We need the fixes in here as well, and resolves some merge issues with
    the mhi codebase.

If my assumption is correct when I propose that we revert commit
ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
0092a1e3f763 is in -next, not in Linus' tree yet) and commit
ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
char-misc-next can be then later fixed during the merge window.

Will this work for everyone? If no objections, I'll submit the revert to
Linus later today. We are getting really close to final v5.14 release so
not much time left to fix this.

Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
v5.14-rc5, users have reported (and I have confirmed) that at least
QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
supported by ath11k are currently broken.

[1] https://git.kernel.org/linus/ce78ffa3ef16

[2] https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/commit/?h=char-misc-next&id=813272ed5238b37c81e448b302048e8008570121

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

[regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

(Adding Linus and Greg)

Kalle Valo <kvalo@codeaurora.org> writes:

> (Adding Dave and Jakub to CC)
>
> Nicolas Schichan <nschichan@freebox.fr> writes:
>
>> On 23/08/2021 14:53, Kalle Valo wrote:
>>> (adding linux-wireless, regressions and some mhi folks)
>>> 
>>> Wren Turkal <wt@penguintechs.org> writes:
>>> 
>>>> I have no device for the wifi on my computer. 5.13 worked pretty well.
>>>> I also found others reporting similar issues:
>>>> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
>>>>
>>>> Here's info about the hardware on my laptop:
>>>> ➜  ~ sudo dmidecode -s system-product-name
>>>> XPS 13 9310
>>>>
>>>> ➜  ~ sudo dmidecode -s bios-version
>>>> 3.0.4
>>> 
>>> Do you get the same mhi error as in the forum post?
>>> 
>>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>>> 
>>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
>>> v5.14-rc6 kernel right now.
>>
>> Hello,
>>
>> I have hit the same issue on Linux 5.14-rc7:
>>
>> [   14.780566] qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>>
>> This looks to be caused by commit:
>>
>> ce78ffa3ef16 net: really fix the build...
>>
>> Reverting this commit results in ath11k being able to load without errors.
>
> Thanks, this helps a lot. Commit ce78ffa3ef16 was introduced in
> v5.14-rc5 so I assume that's the first release which broke ath11k.
>
> Dave, what build issue did you fix with commit ce78ffa3ef16? Could we
> revert the commit? The problem is that, unless we fix this issue, with
> v5.14 WLAN will be broken on a quite few newer Dell laptops.

I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
really fix the build...")[1] is for handling a conflict between net-next
and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
mhi: Add inbound buffers allocation flag"). Greg mentions this in a
commit[2]:

commit 813272ed5238b37c81e448b302048e8008570121
Merge: de0534df9347 36a21d51725a
Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>

    Merge 5.14-rc5 into char-misc-next
    
    We need the fixes in here as well, and resolves some merge issues with
    the mhi codebase.

If my assumption is correct when I propose that we revert commit
ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
0092a1e3f763 is in -next, not in Linus' tree yet) and commit
ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
char-misc-next can be then later fixed during the merge window.

Will this work for everyone? If no objections, I'll submit the revert to
Linus later today. We are getting really close to final v5.14 release so
not much time left to fix this.

Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
v5.14-rc5, users have reported (and I have confirmed) that at least
QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
supported by ath11k are currently broken.

[1] https://git.kernel.org/linus/ce78ffa3ef16

[2] https://git.kernel.org/pub/scm/linux/kernel/git/gregkh/char-misc.git/commit/?h=char-misc-next&id=813272ed5238b37c81e448b302048e8008570121

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Greg Kroah-Hartman]

On Thu, Aug 26, 2021 at 05:25:04PM +0300, Kalle Valo wrote:
> (Adding Linus and Greg)
> 
> Kalle Valo <kvalo@codeaurora.org> writes:
> 
> > (Adding Dave and Jakub to CC)
> >
> > Nicolas Schichan <nschichan@freebox.fr> writes:
> >
> >> On 23/08/2021 14:53, Kalle Valo wrote:
> >>> (adding linux-wireless, regressions and some mhi folks)
> >>> 
> >>> Wren Turkal <wt@penguintechs.org> writes:
> >>> 
> >>>> I have no device for the wifi on my computer. 5.13 worked pretty well.
> >>>> I also found others reporting similar issues:
> >>>> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
> >>>>
> >>>> Here's info about the hardware on my laptop:
> >>>> ➜  ~ sudo dmidecode -s system-product-name
> >>>> XPS 13 9310
> >>>>
> >>>> ➜  ~ sudo dmidecode -s bios-version
> >>>> 3.0.4
> >>> 
> >>> Do you get the same mhi error as in the forum post?
> >>> 
> >>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
> >>> 
> >>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
> >>> v5.14-rc6 kernel right now.
> >>
> >> Hello,
> >>
> >> I have hit the same issue on Linux 5.14-rc7:
> >>
> >> [   14.780566] qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
> >>
> >> This looks to be caused by commit:
> >>
> >> ce78ffa3ef16 net: really fix the build...
> >>
> >> Reverting this commit results in ath11k being able to load without errors.
> >
> > Thanks, this helps a lot. Commit ce78ffa3ef16 was introduced in
> > v5.14-rc5 so I assume that's the first release which broke ath11k.
> >
> > Dave, what build issue did you fix with commit ce78ffa3ef16? Could we
> > revert the commit? The problem is that, unless we fix this issue, with
> > v5.14 WLAN will be broken on a quite few newer Dell laptops.
> 
> I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
> really fix the build...")[1] is for handling a conflict between net-next
> and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
> mhi: Add inbound buffers allocation flag"). Greg mentions this in a
> commit[2]:
> 
> commit 813272ed5238b37c81e448b302048e8008570121
> Merge: de0534df9347 36a21d51725a
> Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
>     Merge 5.14-rc5 into char-misc-next
>     
>     We need the fixes in here as well, and resolves some merge issues with
>     the mhi codebase.
> 
> If my assumption is correct when I propose that we revert commit
> ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
> 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
> ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
> char-misc-next can be then later fixed during the merge window.
> 
> Will this work for everyone? If no objections, I'll submit the revert to
> Linus later today. We are getting really close to final v5.14 release so
> not much time left to fix this.
> 
> Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
> v5.14-rc5, users have reported (and I have confirmed) that at least
> QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
> supported by ath11k are currently broken.

No objection from me for reverting that, if it fixes the problems you
are seeing for 5.14-final.

The goal was for the mhi changes to go through the networking tree in
the first place, I don't see how this got out of sync.

If this is reverted, some help on how to resolve the merge issues it
will cause would be appreciated.

thanks,

greg k-h

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Greg Kroah-Hartman]

On Thu, Aug 26, 2021 at 05:25:04PM +0300, Kalle Valo wrote:
> (Adding Linus and Greg)
> 
> Kalle Valo <kvalo@codeaurora.org> writes:
> 
> > (Adding Dave and Jakub to CC)
> >
> > Nicolas Schichan <nschichan@freebox.fr> writes:
> >
> >> On 23/08/2021 14:53, Kalle Valo wrote:
> >>> (adding linux-wireless, regressions and some mhi folks)
> >>> 
> >>> Wren Turkal <wt@penguintechs.org> writes:
> >>> 
> >>>> I have no device for the wifi on my computer. 5.13 worked pretty well.
> >>>> I also found others reporting similar issues:
> >>>> https://forum.manjaro.org/t/kernel5-14-rc6-ath11k-on-qca6390-regression-mhi-probe-failure/79362
> >>>>
> >>>> Here's info about the hardware on my laptop:
> >>>> ➜  ~ sudo dmidecode -s system-product-name
> >>>> XPS 13 9310
> >>>>
> >>>> ➜  ~ sudo dmidecode -s bios-version
> >>>> 3.0.4
> >>> 
> >>> Do you get the same mhi error as in the forum post?
> >>> 
> >>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
> >>> 
> >>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
> >>> v5.14-rc6 kernel right now.
> >>
> >> Hello,
> >>
> >> I have hit the same issue on Linux 5.14-rc7:
> >>
> >> [   14.780566] qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
> >>
> >> This looks to be caused by commit:
> >>
> >> ce78ffa3ef16 net: really fix the build...
> >>
> >> Reverting this commit results in ath11k being able to load without errors.
> >
> > Thanks, this helps a lot. Commit ce78ffa3ef16 was introduced in
> > v5.14-rc5 so I assume that's the first release which broke ath11k.
> >
> > Dave, what build issue did you fix with commit ce78ffa3ef16? Could we
> > revert the commit? The problem is that, unless we fix this issue, with
> > v5.14 WLAN will be broken on a quite few newer Dell laptops.
> 
> I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
> really fix the build...")[1] is for handling a conflict between net-next
> and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
> mhi: Add inbound buffers allocation flag"). Greg mentions this in a
> commit[2]:
> 
> commit 813272ed5238b37c81e448b302048e8008570121
> Merge: de0534df9347 36a21d51725a
> Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> 
>     Merge 5.14-rc5 into char-misc-next
>     
>     We need the fixes in here as well, and resolves some merge issues with
>     the mhi codebase.
> 
> If my assumption is correct when I propose that we revert commit
> ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
> 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
> ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
> char-misc-next can be then later fixed during the merge window.
> 
> Will this work for everyone? If no objections, I'll submit the revert to
> Linus later today. We are getting really close to final v5.14 release so
> not much time left to fix this.
> 
> Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
> v5.14-rc5, users have reported (and I have confirmed) that at least
> QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
> supported by ath11k are currently broken.

No objection from me for reverting that, if it fixes the problems you
are seeing for 5.14-final.

The goal was for the mhi changes to go through the networking tree in
the first place, I don't see how this got out of sync.

If this is reverted, some help on how to resolve the merge issues it
will cause would be appreciated.

thanks,

greg k-h

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Jakub Kicinski]

On Thu, 26 Aug 2021 16:38:35 +0200 Greg Kroah-Hartman wrote:
> > I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
> > really fix the build...")[1] is for handling a conflict between net-next
> > and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
> > mhi: Add inbound buffers allocation flag"). Greg mentions this in a
> > commit[2]:
> > 
> > commit 813272ed5238b37c81e448b302048e8008570121
> > Merge: de0534df9347 36a21d51725a
> > Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > 
> >     Merge 5.14-rc5 into char-misc-next
> >     
> >     We need the fixes in here as well, and resolves some merge issues with
> >     the mhi codebase.
> > 
> > If my assumption is correct when I propose that we revert commit
> > ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
> > 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
> > ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
> > char-misc-next can be then later fixed during the merge window.
> > 
> > Will this work for everyone? If no objections, I'll submit the revert to
> > Linus later today. We are getting really close to final v5.14 release so
> > not much time left to fix this.
> > 
> > Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
> > v5.14-rc5, users have reported (and I have confirmed) that at least
> > QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
> > supported by ath11k are currently broken.  
> 
> No objection from me for reverting that, if it fixes the problems you
> are seeing for 5.14-final.
> 
> The goal was for the mhi changes to go through the networking tree in
> the first place, I don't see how this got out of sync.
> 
> If this is reverted, some help on how to resolve the merge issues it
> will cause would be appreciated.

Also no objections here. FWIW I'm about to send the last PR for
networking, still waiting on BPF. You can send the revert to netdev, 
or directly to Linus as you prefer. LMK.

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Jakub Kicinski]

On Thu, 26 Aug 2021 16:38:35 +0200 Greg Kroah-Hartman wrote:
> > I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
> > really fix the build...")[1] is for handling a conflict between net-next
> > and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
> > mhi: Add inbound buffers allocation flag"). Greg mentions this in a
> > commit[2]:
> > 
> > commit 813272ed5238b37c81e448b302048e8008570121
> > Merge: de0534df9347 36a21d51725a
> > Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
> > 
> >     Merge 5.14-rc5 into char-misc-next
> >     
> >     We need the fixes in here as well, and resolves some merge issues with
> >     the mhi codebase.
> > 
> > If my assumption is correct when I propose that we revert commit
> > ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
> > 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
> > ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
> > char-misc-next can be then later fixed during the merge window.
> > 
> > Will this work for everyone? If no objections, I'll submit the revert to
> > Linus later today. We are getting really close to final v5.14 release so
> > not much time left to fix this.
> > 
> > Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
> > v5.14-rc5, users have reported (and I have confirmed) that at least
> > QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
> > supported by ath11k are currently broken.  
> 
> No objection from me for reverting that, if it fixes the problems you
> are seeing for 5.14-final.
> 
> The goal was for the mhi changes to go through the networking tree in
> the first place, I don't see how this got out of sync.
> 
> If this is reverted, some help on how to resolve the merge issues it
> will cause would be appreciated.

Also no objections here. FWIW I'm about to send the last PR for
networking, still waiting on BPF. You can send the revert to netdev, 
or directly to Linus as you prefer. LMK.

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Jakub Kicinski <kuba@kernel.org> writes:

> On Thu, 26 Aug 2021 16:38:35 +0200 Greg Kroah-Hartman wrote:
>> > I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
>> > really fix the build...")[1] is for handling a conflict between net-next
>> > and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
>> > mhi: Add inbound buffers allocation flag"). Greg mentions this in a
>> > commit[2]:
>> > 
>> > commit 813272ed5238b37c81e448b302048e8008570121
>> > Merge: de0534df9347 36a21d51725a
>> > Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> > 
>> >     Merge 5.14-rc5 into char-misc-next
>> >     
>> >     We need the fixes in here as well, and resolves some merge issues with
>> >     the mhi codebase.
>> > 
>> > If my assumption is correct when I propose that we revert commit
>> > ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
>> > 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
>> > ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
>> > char-misc-next can be then later fixed during the merge window.
>> > 
>> > Will this work for everyone? If no objections, I'll submit the revert to
>> > Linus later today. We are getting really close to final v5.14 release so
>> > not much time left to fix this.
>> > 
>> > Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
>> > v5.14-rc5, users have reported (and I have confirmed) that at least
>> > QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
>> > supported by ath11k are currently broken.  
>> 
>> No objection from me for reverting that, if it fixes the problems you
>> are seeing for 5.14-final.
>> 
>> The goal was for the mhi changes to go through the networking tree in
>> the first place, I don't see how this got out of sync.
>> 
>> If this is reverted, some help on how to resolve the merge issues it
>> will cause would be appreciated.
>
> Also no objections here. FWIW I'm about to send the last PR for
> networking, still waiting on BPF. You can send the revert to netdev, 
> or directly to Linus as you prefer. LMK.

I prefer take it via the net tree if possible, so if you can wait ~2h
and I'll send it to you.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Jakub Kicinski <kuba@kernel.org> writes:

> On Thu, 26 Aug 2021 16:38:35 +0200 Greg Kroah-Hartman wrote:
>> > I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
>> > really fix the build...")[1] is for handling a conflict between net-next
>> > and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
>> > mhi: Add inbound buffers allocation flag"). Greg mentions this in a
>> > commit[2]:
>> > 
>> > commit 813272ed5238b37c81e448b302048e8008570121
>> > Merge: de0534df9347 36a21d51725a
>> > Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> > 
>> >     Merge 5.14-rc5 into char-misc-next
>> >     
>> >     We need the fixes in here as well, and resolves some merge issues with
>> >     the mhi codebase.
>> > 
>> > If my assumption is correct when I propose that we revert commit
>> > ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
>> > 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
>> > ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
>> > char-misc-next can be then later fixed during the merge window.
>> > 
>> > Will this work for everyone? If no objections, I'll submit the revert to
>> > Linus later today. We are getting really close to final v5.14 release so
>> > not much time left to fix this.
>> > 
>> > Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
>> > v5.14-rc5, users have reported (and I have confirmed) that at least
>> > QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
>> > supported by ath11k are currently broken.  
>> 
>> No objection from me for reverting that, if it fixes the problems you
>> are seeing for 5.14-final.
>> 
>> The goal was for the mhi changes to go through the networking tree in
>> the first place, I don't see how this got out of sync.
>> 
>> If this is reverted, some help on how to resolve the merge issues it
>> will cause would be appreciated.
>
> Also no objections here. FWIW I'm about to send the last PR for
> networking, still waiting on BPF. You can send the revert to netdev, 
> or directly to Linus as you prefer. LMK.

I prefer take it via the net tree if possible, so if you can wait ~2h
and I'll send it to you.

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Jakub Kicinski <kuba@kernel.org> writes:

> On Thu, 26 Aug 2021 16:38:35 +0200 Greg Kroah-Hartman wrote:
>> > I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
>> > really fix the build...")[1] is for handling a conflict between net-next
>> > and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
>> > mhi: Add inbound buffers allocation flag"). Greg mentions this in a
>> > commit[2]:
>> > 
>> > commit 813272ed5238b37c81e448b302048e8008570121
>> > Merge: de0534df9347 36a21d51725a
>> > Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> > 
>> >     Merge 5.14-rc5 into char-misc-next
>> >     
>> >     We need the fixes in here as well, and resolves some merge issues with
>> >     the mhi codebase.
>> > 
>> > If my assumption is correct when I propose that we revert commit
>> > ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
>> > 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
>> > ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
>> > char-misc-next can be then later fixed during the merge window.
>> > 
>> > Will this work for everyone? If no objections, I'll submit the revert to
>> > Linus later today. We are getting really close to final v5.14 release so
>> > not much time left to fix this.
>> > 
>> > Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
>> > v5.14-rc5, users have reported (and I have confirmed) that at least
>> > QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
>> > supported by ath11k are currently broken.  
>> 
>> No objection from me for reverting that, if it fixes the problems you
>> are seeing for 5.14-final.
>> 
>> The goal was for the mhi changes to go through the networking tree in
>> the first place, I don't see how this got out of sync.
>> 
>> If this is reverted, some help on how to resolve the merge issues it
>> will cause would be appreciated.
>
> Also no objections here. FWIW I'm about to send the last PR for
> networking, still waiting on BPF. You can send the revert to netdev, 
> or directly to Linus as you prefer. LMK.

I prefer take it via the net tree if possible, so if you can wait ~2h
and I'll send it to you.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Kalle Valo <kvalo@codeaurora.org> writes:

> Jakub Kicinski <kuba@kernel.org> writes:
>
>> On Thu, 26 Aug 2021 16:38:35 +0200 Greg Kroah-Hartman wrote:
>>> > I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
>>> > really fix the build...")[1] is for handling a conflict between net-next
>>> > and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
>>> > mhi: Add inbound buffers allocation flag"). Greg mentions this in a
>>> > commit[2]:
>>> > 
>>> > commit 813272ed5238b37c81e448b302048e8008570121
>>> > Merge: de0534df9347 36a21d51725a
>>> > Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>> > 
>>> >     Merge 5.14-rc5 into char-misc-next
>>> >     
>>> >     We need the fixes in here as well, and resolves some merge issues with
>>> >     the mhi codebase.
>>> > 
>>> > If my assumption is correct when I propose that we revert commit
>>> > ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
>>> > 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
>>> > ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
>>> > char-misc-next can be then later fixed during the merge window.
>>> > 
>>> > Will this work for everyone? If no objections, I'll submit the revert to
>>> > Linus later today. We are getting really close to final v5.14 release so
>>> > not much time left to fix this.
>>> > 
>>> > Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
>>> > v5.14-rc5, users have reported (and I have confirmed) that at least
>>> > QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
>>> > supported by ath11k are currently broken.  
>>> 
>>> No objection from me for reverting that, if it fixes the problems you
>>> are seeing for 5.14-final.
>>> 
>>> The goal was for the mhi changes to go through the networking tree in
>>> the first place, I don't see how this got out of sync.
>>> 
>>> If this is reverted, some help on how to resolve the merge issues it
>>> will cause would be appreciated.
>>
>> Also no objections here. FWIW I'm about to send the last PR for
>> networking, still waiting on BPF. You can send the revert to netdev, 
>> or directly to Linus as you prefer. LMK.
>
> I prefer take it via the net tree if possible, so if you can wait ~2h
> and I'll send it to you.

I now submitted the revert, please take it into the net tree if you
still can:

https://patchwork.kernel.org/project/netdevbpf/patch/20210826172816.24478-1-kvalo@codeaurora.org/

I also tested the build with various QRTR options and didn't see any
build errors.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Kalle Valo <kvalo@codeaurora.org> writes:

> Jakub Kicinski <kuba@kernel.org> writes:
>
>> On Thu, 26 Aug 2021 16:38:35 +0200 Greg Kroah-Hartman wrote:
>>> > I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
>>> > really fix the build...")[1] is for handling a conflict between net-next
>>> > and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
>>> > mhi: Add inbound buffers allocation flag"). Greg mentions this in a
>>> > commit[2]:
>>> > 
>>> > commit 813272ed5238b37c81e448b302048e8008570121
>>> > Merge: de0534df9347 36a21d51725a
>>> > Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>> > 
>>> >     Merge 5.14-rc5 into char-misc-next
>>> >     
>>> >     We need the fixes in here as well, and resolves some merge issues with
>>> >     the mhi codebase.
>>> > 
>>> > If my assumption is correct when I propose that we revert commit
>>> > ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
>>> > 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
>>> > ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
>>> > char-misc-next can be then later fixed during the merge window.
>>> > 
>>> > Will this work for everyone? If no objections, I'll submit the revert to
>>> > Linus later today. We are getting really close to final v5.14 release so
>>> > not much time left to fix this.
>>> > 
>>> > Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
>>> > v5.14-rc5, users have reported (and I have confirmed) that at least
>>> > QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
>>> > supported by ath11k are currently broken.  
>>> 
>>> No objection from me for reverting that, if it fixes the problems you
>>> are seeing for 5.14-final.
>>> 
>>> The goal was for the mhi changes to go through the networking tree in
>>> the first place, I don't see how this got out of sync.
>>> 
>>> If this is reverted, some help on how to resolve the merge issues it
>>> will cause would be appreciated.
>>
>> Also no objections here. FWIW I'm about to send the last PR for
>> networking, still waiting on BPF. You can send the revert to netdev, 
>> or directly to Linus as you prefer. LMK.
>
> I prefer take it via the net tree if possible, so if you can wait ~2h
> and I'll send it to you.

I now submitted the revert, please take it into the net tree if you
still can:

https://patchwork.kernel.org/project/netdevbpf/patch/20210826172816.24478-1-kvalo@codeaurora.org/

I also tested the build with various QRTR options and didn't see any
build errors.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Kalle Valo <kvalo@codeaurora.org> writes:

> Jakub Kicinski <kuba@kernel.org> writes:
>
>> On Thu, 26 Aug 2021 16:38:35 +0200 Greg Kroah-Hartman wrote:
>>> > I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
>>> > really fix the build...")[1] is for handling a conflict between net-next
>>> > and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
>>> > mhi: Add inbound buffers allocation flag"). Greg mentions this in a
>>> > commit[2]:
>>> > 
>>> > commit 813272ed5238b37c81e448b302048e8008570121
>>> > Merge: de0534df9347 36a21d51725a
>>> > Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>>> > 
>>> >     Merge 5.14-rc5 into char-misc-next
>>> >     
>>> >     We need the fixes in here as well, and resolves some merge issues with
>>> >     the mhi codebase.
>>> > 
>>> > If my assumption is correct when I propose that we revert commit
>>> > ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
>>> > 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
>>> > ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
>>> > char-misc-next can be then later fixed during the merge window.
>>> > 
>>> > Will this work for everyone? If no objections, I'll submit the revert to
>>> > Linus later today. We are getting really close to final v5.14 release so
>>> > not much time left to fix this.
>>> > 
>>> > Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
>>> > v5.14-rc5, users have reported (and I have confirmed) that at least
>>> > QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
>>> > supported by ath11k are currently broken.  
>>> 
>>> No objection from me for reverting that, if it fixes the problems you
>>> are seeing for 5.14-final.
>>> 
>>> The goal was for the mhi changes to go through the networking tree in
>>> the first place, I don't see how this got out of sync.
>>> 
>>> If this is reverted, some help on how to resolve the merge issues it
>>> will cause would be appreciated.
>>
>> Also no objections here. FWIW I'm about to send the last PR for
>> networking, still waiting on BPF. You can send the revert to netdev, 
>> or directly to Linus as you prefer. LMK.
>
> I prefer take it via the net tree if possible, so if you can wait ~2h
> and I'll send it to you.

I now submitted the revert, please take it into the net tree if you
still can:

https://patchwork.kernel.org/project/netdevbpf/patch/20210826172816.24478-1-kvalo@codeaurora.org/

I also tested the build with various QRTR options and didn't see any
build errors.

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Jakub Kicinski]

On Thu, 26 Aug 2021 20:33:47 +0300 Kalle Valo wrote:
> >> Also no objections here. FWIW I'm about to send the last PR for
> >> networking, still waiting on BPF. You can send the revert to netdev, 
> >> or directly to Linus as you prefer. LMK.  
> >
> > I prefer take it via the net tree if possible, so if you can wait ~2h
> > and I'll send it to you.  
> 
> I now submitted the revert, please take it into the net tree if you
> still can:
> 
> https://patchwork.kernel.org/project/netdevbpf/patch/20210826172816.24478-1-kvalo@codeaurora.org/
> 
> I also tested the build with various QRTR options and didn't see any
> build errors.

Done, thank you!

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Jakub Kicinski]

On Thu, 26 Aug 2021 20:33:47 +0300 Kalle Valo wrote:
> >> Also no objections here. FWIW I'm about to send the last PR for
> >> networking, still waiting on BPF. You can send the revert to netdev, 
> >> or directly to Linus as you prefer. LMK.  
> >
> > I prefer take it via the net tree if possible, so if you can wait ~2h
> > and I'll send it to you.  
> 
> I now submitted the revert, please take it into the net tree if you
> still can:
> 
> https://patchwork.kernel.org/project/netdevbpf/patch/20210826172816.24478-1-kvalo@codeaurora.org/
> 
> I also tested the build with various QRTR options and didn't see any
> build errors.

Done, thank you!

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Jakub Kicinski <kuba@kernel.org> writes:

> On Thu, 26 Aug 2021 20:33:47 +0300 Kalle Valo wrote:
>> >> Also no objections here. FWIW I'm about to send the last PR for
>> >> networking, still waiting on BPF. You can send the revert to netdev, 
>> >> or directly to Linus as you prefer. LMK.  
>> >
>> > I prefer take it via the net tree if possible, so if you can wait ~2h
>> > and I'll send it to you.  
>> 
>> I now submitted the revert, please take it into the net tree if you
>> still can:
>> 
>> https://patchwork.kernel.org/project/netdevbpf/patch/20210826172816.24478-1-kvalo@codeaurora.org/
>> 
>> I also tested the build with various QRTR options and didn't see any
>> build errors.
>
> Done, thank you!

Thank you waiting for me :)

I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
laptop with QCA6390 and ath11k works without problems. So the issue
should be solved in the final v5.14 release.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Jakub Kicinski <kuba@kernel.org> writes:

> On Thu, 26 Aug 2021 20:33:47 +0300 Kalle Valo wrote:
>> >> Also no objections here. FWIW I'm about to send the last PR for
>> >> networking, still waiting on BPF. You can send the revert to netdev, 
>> >> or directly to Linus as you prefer. LMK.  
>> >
>> > I prefer take it via the net tree if possible, so if you can wait ~2h
>> > and I'll send it to you.  
>> 
>> I now submitted the revert, please take it into the net tree if you
>> still can:
>> 
>> https://patchwork.kernel.org/project/netdevbpf/patch/20210826172816.24478-1-kvalo@codeaurora.org/
>> 
>> I also tested the build with various QRTR options and didn't see any
>> build errors.
>
> Done, thank you!

Thank you waiting for me :)

I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
laptop with QCA6390 and ath11k works without problems. So the issue
should be solved in the final v5.14 release.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Jakub Kicinski <kuba@kernel.org> writes:

> On Thu, 26 Aug 2021 20:33:47 +0300 Kalle Valo wrote:
>> >> Also no objections here. FWIW I'm about to send the last PR for
>> >> networking, still waiting on BPF. You can send the revert to netdev, 
>> >> or directly to Linus as you prefer. LMK.  
>> >
>> > I prefer take it via the net tree if possible, so if you can wait ~2h
>> > and I'll send it to you.  
>> 
>> I now submitted the revert, please take it into the net tree if you
>> still can:
>> 
>> https://patchwork.kernel.org/project/netdevbpf/patch/20210826172816.24478-1-kvalo@codeaurora.org/
>> 
>> I also tested the build with various QRTR options and didn't see any
>> build errors.
>
> Done, thank you!

Thank you waiting for me :)

I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
laptop with QCA6390 and ath11k works without problems. So the issue
should be solved in the final v5.14 release.

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Nicolas Schichan]

On Fri, Aug 27, 2021 at 2:41 PM Kalle Valo <kvalo@codeaurora.org> wrote:
> Jakub Kicinski <kuba@kernel.org> writes:
> > Done, thank you!
>
> Thank you waiting for me :)
>
> I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
> laptop with QCA6390 and ath11k works without problems. So the issue
> should be solved in the final v5.14 release.
>

Good evening,

I have tested loading ath11k on v5.14.0 and I can confirm that the
driver loads fine now, with a phy and wlan interface being created as
a result.

Thanks and best regards,

-- 
Nicolas Schichan

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Nicolas Schichan]

On Fri, Aug 27, 2021 at 2:41 PM Kalle Valo <kvalo@codeaurora.org> wrote:
> Jakub Kicinski <kuba@kernel.org> writes:
> > Done, thank you!
>
> Thank you waiting for me :)
>
> I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
> laptop with QCA6390 and ath11k works without problems. So the issue
> should be solved in the final v5.14 release.
>

Good evening,

I have tested loading ath11k on v5.14.0 and I can confirm that the
driver loads fine now, with a phy and wlan interface being created as
a result.

Thanks and best regards,

-- 
Nicolas Schichan

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Nicolas Schichan]

On Fri, Aug 27, 2021 at 2:41 PM Kalle Valo <kvalo@codeaurora.org> wrote:
> Jakub Kicinski <kuba@kernel.org> writes:
> > Done, thank you!
>
> Thank you waiting for me :)
>
> I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
> laptop with QCA6390 and ath11k works without problems. So the issue
> should be solved in the final v5.14 release.
>

Good evening,

I have tested loading ath11k on v5.14.0 and I can confirm that the
driver loads fine now, with a phy and wlan interface being created as
a result.

Thanks and best regards,

-- 
Nicolas Schichan

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Nicolas Schichan <nschichan@freebox.fr> writes:

> On Fri, Aug 27, 2021 at 2:41 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>> Jakub Kicinski <kuba@kernel.org> writes:
>> > Done, thank you!
>>
>> Thank you waiting for me :)
>>
>> I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
>> laptop with QCA6390 and ath11k works without problems. So the issue
>> should be solved in the final v5.14 release.
>>
>
> Good evening,
>
> I have tested loading ath11k on v5.14.0 and I can confirm that the
> driver loads fine now, with a phy and wlan interface being created as
> a result.

Great, thanks for testing and letting us know. And espeacially huge
thanks for finding the commit which broke this!

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Nicolas Schichan <nschichan@freebox.fr> writes:

> On Fri, Aug 27, 2021 at 2:41 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>> Jakub Kicinski <kuba@kernel.org> writes:
>> > Done, thank you!
>>
>> Thank you waiting for me :)
>>
>> I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
>> laptop with QCA6390 and ath11k works without problems. So the issue
>> should be solved in the final v5.14 release.
>>
>
> Good evening,
>
> I have tested loading ath11k on v5.14.0 and I can confirm that the
> driver loads fine now, with a phy and wlan interface being created as
> a result.

Great, thanks for testing and letting us know. And espeacially huge
thanks for finding the commit which broke this!

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Nicolas Schichan <nschichan@freebox.fr> writes:

> On Fri, Aug 27, 2021 at 2:41 PM Kalle Valo <kvalo@codeaurora.org> wrote:
>> Jakub Kicinski <kuba@kernel.org> writes:
>> > Done, thank you!
>>
>> Thank you waiting for me :)
>>
>> I just tested commit 7e9965cddea8 from Linus' tree on Dell XPS 13 9310
>> laptop with QCA6390 and ath11k works without problems. So the issue
>> should be solved in the final v5.14 release.
>>
>
> Good evening,
>
> I have tested loading ath11k on v5.14.0 and I can confirm that the
> driver loads fine now, with a phy and wlan interface being created as
> a result.

Great, thanks for testing and letting us know. And espeacially huge
thanks for finding the commit which broke this!

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:

>> I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
>> really fix the build...")[1] is for handling a conflict between net-next
>> and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
>> mhi: Add inbound buffers allocation flag"). Greg mentions this in a
>> commit[2]:
>> 
>> commit 813272ed5238b37c81e448b302048e8008570121
>> Merge: de0534df9347 36a21d51725a
>> Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> 
>>     Merge 5.14-rc5 into char-misc-next
>>     
>>     We need the fixes in here as well, and resolves some merge issues with
>>     the mhi codebase.
>> 
>> If my assumption is correct when I propose that we revert commit
>> ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
>> 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
>> ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
>> char-misc-next can be then later fixed during the merge window.
>> 
>> Will this work for everyone? If no objections, I'll submit the revert to
>> Linus later today. We are getting really close to final v5.14 release so
>> not much time left to fix this.
>> 
>> Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
>> v5.14-rc5, users have reported (and I have confirmed) that at least
>> QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
>> supported by ath11k are currently broken.
>
> No objection from me for reverting that, if it fixes the problems you
> are seeing for 5.14-final.

Thanks!

> The goal was for the mhi changes to go through the networking tree in
> the first place, I don't see how this got out of sync.
>
> If this is reverted, some help on how to resolve the merge issues it
> will cause would be appreciated.

Yes, I'll help with this. I see that Stephen already reported the
reappeared merge issue. It's just that I'm not familiar with inner
workings of the MHI subsystem, but I can test code etc.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:

>> I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
>> really fix the build...")[1] is for handling a conflict between net-next
>> and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
>> mhi: Add inbound buffers allocation flag"). Greg mentions this in a
>> commit[2]:
>> 
>> commit 813272ed5238b37c81e448b302048e8008570121
>> Merge: de0534df9347 36a21d51725a
>> Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> 
>>     Merge 5.14-rc5 into char-misc-next
>>     
>>     We need the fixes in here as well, and resolves some merge issues with
>>     the mhi codebase.
>> 
>> If my assumption is correct when I propose that we revert commit
>> ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
>> 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
>> ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
>> char-misc-next can be then later fixed during the merge window.
>> 
>> Will this work for everyone? If no objections, I'll submit the revert to
>> Linus later today. We are getting really close to final v5.14 release so
>> not much time left to fix this.
>> 
>> Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
>> v5.14-rc5, users have reported (and I have confirmed) that at least
>> QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
>> supported by ath11k are currently broken.
>
> No objection from me for reverting that, if it fixes the problems you
> are seeing for 5.14-final.

Thanks!

> The goal was for the mhi changes to go through the networking tree in
> the first place, I don't see how this got out of sync.
>
> If this is reverted, some help on how to resolve the merge issues it
> will cause would be appreciated.

Yes, I'll help with this. I see that Stephen already reported the
reappeared merge issue. It's just that I'm not familiar with inner
workings of the MHI subsystem, but I can test code etc.

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

Re: [regression] Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Greg Kroah-Hartman <gregkh@linuxfoundation.org> writes:

>> I did some investiation and I suspect that commit ce78ffa3ef16 ("net:
>> really fix the build...")[1] is for handling a conflict between net-next
>> and char-misc-next trees related to Loic's commit 0092a1e3f763 ("bus:
>> mhi: Add inbound buffers allocation flag"). Greg mentions this in a
>> commit[2]:
>> 
>> commit 813272ed5238b37c81e448b302048e8008570121
>> Merge: de0534df9347 36a21d51725a
>> Author:     Greg Kroah-Hartman <gregkh@linuxfoundation.org>
>> 
>>     Merge 5.14-rc5 into char-misc-next
>>     
>>     We need the fixes in here as well, and resolves some merge issues with
>>     the mhi codebase.
>> 
>> If my assumption is correct when I propose that we revert commit
>> ce78ffa3ef16 for v5.14, AFAICS it's not really needed for v5.14 (commit
>> 0092a1e3f763 is in -next, not in Linus' tree yet) and commit
>> ce78ffa3ef16 breaks ath11k. And the conflict between net-next and
>> char-misc-next can be then later fixed during the merge window.
>> 
>> Will this work for everyone? If no objections, I'll submit the revert to
>> Linus later today. We are getting really close to final v5.14 release so
>> not much time left to fix this.
>> 
>> Just to reiterate why the urgency: commit ce78ffa3ef16 broke ath11k in
>> v5.14-rc5, users have reported (and I have confirmed) that at least
>> QCA6390 support is broken but I suspect all Qualcomm Wi-Fi 6 devices
>> supported by ath11k are currently broken.
>
> No objection from me for reverting that, if it fixes the problems you
> are seeing for 5.14-final.

Thanks!

> The goal was for the mhi changes to go through the networking tree in
> the first place, I don't see how this got out of sync.
>
> If this is reverted, some help on how to resolve the merge issues it
> will cause would be appreciated.

Yes, I'll help with this. I see that Stephen already reported the
reappeared merge issue. It's just that I'm not familiar with inner
workings of the MHI subsystem, but I can test code etc.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Wren Turkal]

On 8/23/21 5:53 AM, Kalle Valo wrote:
> Do you get the same mhi error as in the forum post?
> 
> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
> 
> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
> v5.14-rc6 kernel right now.

Yes, I get that same message in my logs.

FWIW, ath11k_pci now does not get loaded on boot. I can manually load 
it, but it doesn't seem to do anything.

wt
-- 
You're more amazing than you think! ymatyt.com

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Wren Turkal]

On 8/23/21 5:53 AM, Kalle Valo wrote:
> Do you get the same mhi error as in the forum post?
> 
> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
> 
> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
> v5.14-rc6 kernel right now.

Yes, I get that same message in my logs.

FWIW, ath11k_pci now does not get loaded on boot. I can manually load 
it, but it doesn't seem to do anything.

wt
-- 
You're more amazing than you think! ymatyt.com

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

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Wren Turkal <wt@penguintechs.org> writes:

> On 8/23/21 5:53 AM, Kalle Valo wrote:
>> Do you get the same mhi error as in the forum post?
>>
>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>>
>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
>> v5.14-rc6 kernel right now.
>
> Yes, I get that same message in my logs.
>
> FWIW, ath11k_pci now does not get loaded on boot. I can manually load
> it, but it doesn't seem to do anything.

Do you know if this automatic module loading is related to this qrtr
regression or a separate problem? Can you try Linus' tree and report if
the module load problem still exists? The qrtr regression is fixed now.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Wren Turkal <wt@penguintechs.org> writes:

> On 8/23/21 5:53 AM, Kalle Valo wrote:
>> Do you get the same mhi error as in the forum post?
>>
>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>>
>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
>> v5.14-rc6 kernel right now.
>
> Yes, I get that same message in my logs.
>
> FWIW, ath11k_pci now does not get loaded on boot. I can manually load
> it, but it doesn't seem to do anything.

Do you know if this automatic module loading is related to this qrtr
regression or a separate problem? Can you try Linus' tree and report if
the module load problem still exists? The qrtr regression is fixed now.

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

Re: 5.14 rc6 broken for QCA6390 on Dell XPS 13 9310

[Kalle Valo]

Wren Turkal <wt@penguintechs.org> writes:

> On 8/23/21 5:53 AM, Kalle Valo wrote:
>> Do you get the same mhi error as in the forum post?
>>
>> qcom_mhi_qrtr: probe of mhi0_IPCR failed with error -22
>>
>> MHI folks, any ideas? I have XPS 13 9310 myself but I'm not able to test
>> v5.14-rc6 kernel right now.
>
> Yes, I get that same message in my logs.
>
> FWIW, ath11k_pci now does not get loaded on boot. I can manually load
> it, but it doesn't seem to do anything.

Do you know if this automatic module loading is related to this qrtr
regression or a separate problem? Can you try Linus' tree and report if
the module load problem still exists? The qrtr regression is fixed now.

-- 
https://patchwork.kernel.org/project/linux-wireless/list/

https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches