From: Aditya Kumar Singh <quic_adisi@quicinc.com>
To: Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Kalle Valo <kvalo@kernel.org>, Jeff Johnson <jjohnson@kernel.org>,
"Karthikeyan Periyasamy" <quic_periyasa@quicinc.com>,
Harshitha Prem <quic_hprem@quicinc.com>
Cc: Kalle Valo <quic_kvalo@quicinc.com>,
<linux-wireless@vger.kernel.org>, <ath12k@lists.infradead.org>,
<linux-kernel@vger.kernel.org>
Subject: Re: [PATCH 04/10] wifi: ath12k: fix firmware assert during reboot with hardware grouping
Date: Thu, 16 Jan 2025 16:13:03 +0530 [thread overview]
Message-ID: <4ef04d75-5ac8-4db4-8cde-25f9e097b020@quicinc.com> (raw)
In-Reply-To: <5925d874-1b8c-413a-a6ad-16d7ab299f4e@oss.qualcomm.com>
On 1/14/25 00:42, Jeff Johnson wrote:
> On 1/8/2025 8:25 PM, Aditya Kumar Singh wrote:
>> At present, during PCI shutdown, the power down is only executed for a
>> single device. However, when operating in a group, all devices need to be
>> powered down simultaneously. Failure to do so will result in a firmware
>> assertion.
>>
>> Hence, introduce a new ath12k_pci_hw_group_power_down() and call it during
>> power down. This will ensure that all partner devices are properly powered
>> down.
>>
>> Tested-on: QCN9274 hw2.0 PCI WLAN.WBE.1.3.1-00173-QCAHKSWPL_SILICONZ-1
>>
>> Signed-off-by: Aditya Kumar Singh<quic_adisi@quicinc.com>
>> ---
>> drivers/net/wireless/ath/ath12k/pci.c | 23 ++++++++++++++++++++++-
>> 1 file changed, 22 insertions(+), 1 deletion(-)
>>
>> diff --git a/drivers/net/wireless/ath/ath12k/pci.c b/drivers/net/wireless/ath/ath12k/pci.c
>> index 837be309cd45a2d037ee8c3bba8f7be0f457d6b2..7f6521a56ffc0f1e9687c94d6829a9c1f1887661 100644
>> --- a/drivers/net/wireless/ath/ath12k/pci.c
>> +++ b/drivers/net/wireless/ath/ath12k/pci.c
>> @@ -1751,13 +1751,34 @@ static void ath12k_pci_remove(struct pci_dev *pdev)
>> ath12k_core_free(ab);
>> }
>>
>> +static void ath12k_pci_hw_group_power_down(struct ath12k_hw_group *ag)
> don't you end up calling this for every device in the group?
> what prevents ath12k_pci_power_down(ab, false) from being called multiple
> times for the same ab?
That's true. ath12k_pci_power_down() has logic already that if device is
powered down, it will ignore the further call. This is handled via
previous patch.
--
Aditya
next prev parent reply other threads:[~2025-01-16 10:43 UTC|newest]
Thread overview: 23+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-01-09 4:25 [PATCH 00/10] wifi: ath12k: fixes for rmmod and recovery issues " Aditya Kumar Singh
2025-01-09 4:25 ` [PATCH 01/10] wifi: ath12k: prevent race condition in ath12k_core_hw_group_destroy() Aditya Kumar Singh
2025-01-13 19:06 ` Jeff Johnson
2025-01-09 4:25 ` [PATCH 02/10] wifi: ath12k: add reference counting for core attachment to hardware group Aditya Kumar Singh
2025-01-13 19:06 ` Jeff Johnson
2025-01-09 4:25 ` [PATCH 03/10] wifi: ath12k: fix failed to set mhi state error during reboot with hardware grouping Aditya Kumar Singh
2025-01-13 19:07 ` Jeff Johnson
2025-01-09 4:25 ` [PATCH 04/10] wifi: ath12k: fix firmware assert " Aditya Kumar Singh
2025-01-13 19:12 ` Jeff Johnson
2025-01-16 10:43 ` Aditya Kumar Singh [this message]
2025-01-09 4:25 ` [PATCH 05/10] wifi: ath12k: fix SLUB BUG - Object already free in ath12k_reg_free() Aditya Kumar Singh
2025-01-13 19:21 ` Jeff Johnson
2025-01-20 8:38 ` Aditya Kumar Singh
2025-01-09 4:25 ` [PATCH 06/10] wifi: ath12k: fix ath12k_core_pre_reconfigure_recovery() with grouping Aditya Kumar Singh
2025-01-13 19:22 ` Jeff Johnson
2025-01-09 4:25 ` [PATCH 07/10] wifi: ath12k: fix ATH12K_FLAG_REGISTERED flag handling Aditya Kumar Singh
2025-01-13 19:23 ` Jeff Johnson
2025-01-09 4:25 ` [PATCH 08/10] wifi: ath12k: handle ath12k_core_restart() with hardware grouping Aditya Kumar Singh
2025-01-13 19:23 ` Jeff Johnson
2025-01-09 4:25 ` [PATCH 09/10] wifi: ath12k: handle ath12k_core_reset() " Aditya Kumar Singh
2025-01-13 19:24 ` Jeff Johnson
2025-01-09 4:25 ` [PATCH 10/10] wifi: ath12k: reset MLO global memory during recovery Aditya Kumar Singh
2025-01-13 19:25 ` Jeff Johnson
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=4ef04d75-5ac8-4db4-8cde-25f9e097b020@quicinc.com \
--to=quic_adisi@quicinc.com \
--cc=ath12k@lists.infradead.org \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kvalo@kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=quic_hprem@quicinc.com \
--cc=quic_kvalo@quicinc.com \
--cc=quic_periyasa@quicinc.com \
/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
all inboxes | Powered by JetHome®