From: Kalle Valo <kvalo@codeaurora.org>
To: Janusz Dziedzic <janusz.dziedzic@gmail.com>
Cc: Carl Huang <cjhuang@codeaurora.org>,
ath11k@lists.infradead.org,
linux-wireless <linux-wireless@vger.kernel.org>
Subject: Re: [PATCH 0/6] ath11k: support one MSI vector
Date: Mon, 15 Nov 2021 12:43:34 +0200 [thread overview]
Message-ID: <87zgq5hf6x.fsf@codeaurora.org> (raw)
In-Reply-To: <CAFED-jnaYfXvz8S7d8orJmY+_=T-MRZ+v-c9OJFCg78HqS7=cw@mail.gmail.com> (Janusz Dziedzic's message of "Fri, 22 Oct 2021 10:04:46 +0200")
Janusz Dziedzic <janusz.dziedzic@gmail.com> writes:
> czw., 11 lut 2021 o 08:10 Kalle Valo <kvalo@codeaurora.org> napisał(a):
>>
>> Carl Huang <cjhuang@codeaurora.org> writes:
>>
>> > This patch set is to support one MSI vector for QCA6390.
>> >
>> > Carl Huang (6):
>> > ath11k: get msi_data again after request_irq is called
>> > ath11k: add ce and ext irq flag to indicate irq_handler
>> > ath11k: use ATH11K_PCI_IRQ_DP_OFFSET for dp irqx
>> > ath11k: refactor mulitple msi vector implementation
>> > ath11k: supports one MSI vector
>> > ath11k: do not restore ASPM in case of single MSI vector
>>
>> I did some cleanup and before submitting v2 I noticed the patchset (both
>> v1 and v2) is crashing during suspend on my Dell XPS 13 9310. We are
>> investigating the reason for that and will submit v2 once those are
>> fixed.
>>
> Hello Kalle,
>
> What is status for this series?
There's now a new version available:
https://patchwork.kernel.org/project/linux-wireless/cover/20211026041616.4956-1-bqiang@codeaurora.org/
If you can, please do test the version in the master-pending branch
(commit 9a914cfdbfd69):
https://git.kernel.org/pub/scm/linux/kernel/git/kvalo/ath.git/log/?h=master-pending
> I am using ath11k in my banana-pi-r64 (backports-5.15-rc6) board and hit:
> [ 162.392043] ath11k_pci 0000:01:00.0: failed to get 32 MSI vectors,
> only -28 available
> [ 162.399927] ath11k_pci 0000:01:00.0: failed to enable msi: -28
> [ 162.405778] ath11k_pci 0000:01:00.0: disabling bus mastering
> [ 162.411481] ath11k_pci: probe of 0000:01:00.0 failed with error -28
>
> I suspect this series should fix my issue?
Most likely this should fix it. You could also try changing your BIOS
settings to get more MSI vectors, IIRC enabling VT-d help on NUC boards
at least.
--
https://patchwork.kernel.org/project/linux-wireless/list/
https://wireless.wiki.kernel.org/en/developers/documentation/submittingpatches
prev parent reply other threads:[~2021-11-15 10:43 UTC|newest]
Thread overview: 10+ messages / expand[flat|nested] mbox.gz Atom feed top
2020-12-23 3:02 [PATCH 0/6] ath11k: support one MSI vector Carl Huang
2020-12-23 3:02 ` [PATCH 1/6] ath11k: get msi_data again after request_irq is called Carl Huang
2020-12-23 3:02 ` [PATCH 2/6] ath11k: add ce and ext irq flag to indicate irq_handler Carl Huang
2020-12-23 3:02 ` [PATCH 3/6] ath11k: use ATH11K_PCI_IRQ_DP_OFFSET for dp irqx Carl Huang
2020-12-23 3:02 ` [PATCH 4/6] ath11k: refactor mulitple msi vector implementation Carl Huang
2020-12-23 3:02 ` [PATCH 5/6] ath11k: supports one MSI vector Carl Huang
2020-12-23 3:02 ` [PATCH 6/6] ath11k: do not restore ASPM in case of single " Carl Huang
2021-02-11 7:07 ` [PATCH 0/6] ath11k: support one " Kalle Valo
2021-10-22 8:04 ` Janusz Dziedzic
2021-11-15 10:43 ` Kalle Valo [this message]
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=87zgq5hf6x.fsf@codeaurora.org \
--to=kvalo@codeaurora.org \
--cc=ath11k@lists.infradead.org \
--cc=cjhuang@codeaurora.org \
--cc=janusz.dziedzic@gmail.com \
--cc=linux-wireless@vger.kernel.org \
/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).