From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Baochen Qiang <baochen.qiang@oss.qualcomm.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Jeff Johnson <jjohnson@kernel.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
Youssef Samir <quic_yabdulra@quicinc.com>,
Matthew Leung <quic_mattleun@quicinc.com>,
Yan Zhen <yanzhen@vivo.com>,
Alexander Wilhelm <alexander.wilhelm@westermo.com>,
Alex Elder <elder@kernel.org>, Kunwu Chan <chentao@kylinos.cn>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Siddartha Mohanadoss <smohanad@codeaurora.org>,
Sujeev Dias <sdias@codeaurora.org>,
Julia Lawall <julia.lawall@lip6.fr>,
John Crispin <john@phrozen.org>,
Muna Sinada <quic_msinada@quicinc.com>,
Venkateswara Naralasetty <quic_vnaralas@quicinc.com>,
Maharaja Kennadyrajan <quic_mkenna@quicinc.com>,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org
Cc: kernel@collabora.com
Subject: Re: [PATCH 2/3] bus: mhi: don't deinitialize and re-initialize again
Date: Tue, 8 Jul 2025 14:12:11 +0500 [thread overview]
Message-ID: <5c9843b5-d756-4a99-b93f-d32ed8f16e32@collabora.com> (raw)
In-Reply-To: <fdb9f1e7-bf8f-4018-b0ac-ac8a70d9b8ec@oss.qualcomm.com>
On 7/8/25 6:43 AM, Baochen Qiang wrote:
>
>
> On 7/7/2025 9:11 PM, Muhammad Usama Anjum wrote:
>>>>>>>> diff --git a/drivers/net/wireless/ath/ath11k/core.c b/drivers/net/wireless/ath/ath11k/core.c
>>>>>>>> index 4488e4cdc5e9e..bc4930fe6a367 100644
>>>>>>>> --- a/drivers/net/wireless/ath/ath11k/core.c
>>>>>>>> +++ b/drivers/net/wireless/ath/ath11k/core.c
>>>>>>>> @@ -2213,14 +2213,9 @@ static int ath11k_core_reconfigure_on_crash(struct ath11k_base *ab)
>>>>>>>> mutex_unlock(&ab->core_lock);
>>>>>>>>
>>>>>>>> ath11k_dp_free(ab);
>>>>>>>> - ath11k_hal_srng_deinit(ab);
>>>>>>>>
>>>>>>>> ab->free_vdev_map = (1LL << (ab->num_radios * TARGET_NUM_VDEVS(ab))) - 1;
>>>>>>>>
>>>>>>>> - ret = ath11k_hal_srng_init(ab);
>>>>>>>> - if (ret)
>>>>>>>> - return ret;
>>>>>>>> -
>>>>>>> while I agree there is no need of a dealloc/realloc, we can not simply remove calling the
>>>>>>> _deinit()/_init() pair. At least the memset() cleanup to hal parameters (e.g.
>>>>>> Why do is it being done in the resume handler? Shouldn't those parameters be cleaned up
>>>>>> in resume handler? So when device wakes up, its state is already correct.
>>>>>>
>>>>> Hmm... not quite understand your question. Can you elaborate?
>>>> I'm trying to understand the possibility of cleanup of hal in suspend handler. For example:
>>>> * The driver has been loaded and has been working fine.
>>>> * The user called suspend. So all devices would be suspended.
>>>> * In suspend handler of the ath11k, we should do the necessary cleanups of the states
>>>> like hal.
>>>> * When the device would resume after long time, the hal would have the correct state
>>>> already. So we'll not need to deinit and init again.
>>> The hal cleanup is not only needed by suspend/resume, but also a step of reset/recover
>>> process. So If we are moving the cleanup to suspend handler, similar stuff needs to be
>>> done for reset/recover as well.
>> It makes sense.
>>
>> So clearing the hal structure completely other than ab->hal.srn_config doesn't seem
>> right. I've also tested it and it crashes the whole system.
>>
>> On contrary, with only the current patch applied, there is no abnormality.
>>
>> num_shadow_reg_configured and avail_blk_resource are non-zero. If I make them 0,
>> driver still keeps on working.
>>
>> ab->hal.num_shadow_reg_configured = 0;
>> ab->hal.avail_blk_resource = 0;
>> ab->hal.current_blk_index = 0;
>>
>> As you have suggested setting these 3 to zero, is there any other variable in hal
>> structure which should be set to zero?
>
> IMO srng_config, rdp, wrp and srng_key may keep unchanged through suspend/reset, all other
> fields should be cleared/reinitialized.
memseting srng_list and shadow_reg_addr causes crashes. Please can you confirm why do you
think those should be memset. Here is WIP patch:
--- a/drivers/net/wireless/ath/ath11k/core.c
+++ b/drivers/net/wireless/ath/ath11k/core.c
@@ -2213,14 +2213,10 @@ static int ath11k_core_reconfigure_on_crash(struct ath11k_base *ab)
mutex_unlock(&ab->core_lock);
ath11k_dp_free(ab);
- ath11k_hal_srng_deinit(ab);
+ ath11k_hal_srng_clear(ab);
ab->free_vdev_map = (1LL << (ab->num_radios * TARGET_NUM_VDEVS(ab))) - 1;
- ret = ath11k_hal_srng_init(ab);
- if (ret)
- return ret;
-
clear_bit(ATH11K_FLAG_CRASH_FLUSH, &ab->dev_flags);
ret = ath11k_core_qmi_firmware_ready(ab);
diff --git a/drivers/net/wireless/ath/ath11k/hal.c b/drivers/net/wireless/ath/ath11k/hal.c
index b32de563d453a..d4be040acf2c8 100644
--- a/drivers/net/wireless/ath/ath11k/hal.c
+++ b/drivers/net/wireless/ath/ath11k/hal.c
@@ -1359,6 +1359,19 @@ void ath11k_hal_srng_deinit(struct ath11k_base *ab)
}
EXPORT_SYMBOL(ath11k_hal_srng_deinit);
+void ath11k_hal_srng_clear(struct ath11k_base *ab)
+{
+// --> both of these memset causes crashes
+// memset(ab->hal.srng_list, 0,
+// sizeof(ab->hal.srng_list) * HAL_SRNG_RING_ID_MAX);
+// memset(ab->hal.shadow_reg_addr, 0,
+// sizeof(ab->hal.shadow_reg_addr) * HAL_SHADOW_NUM_REGS);
+ ab->hal.avail_blk_resource = 0;
+ ab->hal.current_blk_index = 0;
+ ab->hal.num_shadow_reg_configured = 0;
+}
+EXPORT_SYMBOL(ath11k_hal_srng_clear);
+
void ath11k_hal_dump_srng_stats(struct ath11k_base *ab)
{
struct hal_srng *srng;
diff --git a/drivers/net/wireless/ath/ath11k/hal.h b/drivers/net/wireless/ath/ath11k/hal.h
index 601542410c752..839095af9267e 100644
--- a/drivers/net/wireless/ath/ath11k/hal.h
+++ b/drivers/net/wireless/ath/ath11k/hal.h
@@ -965,6 +965,7 @@ int ath11k_hal_srng_setup(struct ath11k_base *ab, enum hal_ring_type type,
struct hal_srng_params *params);
int ath11k_hal_srng_init(struct ath11k_base *ath11k);
void ath11k_hal_srng_deinit(struct ath11k_base *ath11k);
+void ath11k_hal_srng_clear(struct ath11k_base *ab);
void ath11k_hal_dump_srng_stats(struct ath11k_base *ab);
void ath11k_hal_srng_get_shadow_config(struct ath11k_base *ab,
u32 **cfg, u32 *len);
next prev parent reply other threads:[~2025-07-08 9:13 UTC|newest]
Thread overview: 27+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-06-30 7:43 [PATCH 0/3] bus: mhi: keep dma buffers through suspend/hibernation cycles Muhammad Usama Anjum
2025-06-30 7:43 ` [PATCH 1/3] bus: mhi: host: keep bhi buffer through suspend cycle Muhammad Usama Anjum
2025-07-01 10:25 ` Greg Kroah-Hartman
2025-07-02 15:24 ` Muhammad Usama Anjum
2025-07-08 9:47 ` Krishna Chaitanya Chundru
2025-07-10 14:14 ` Muhammad Usama Anjum
2025-06-30 7:43 ` [PATCH 2/3] bus: mhi: don't deinitialize and re-initialize again Muhammad Usama Anjum
2025-07-01 10:25 ` Greg Kroah-Hartman
2025-07-02 15:25 ` Muhammad Usama Anjum
2025-07-01 14:49 ` Jeff Johnson
2025-07-02 15:28 ` Muhammad Usama Anjum
2025-07-02 17:25 ` Jeff Johnson
2025-07-02 3:50 ` Baochen Qiang
2025-07-02 16:12 ` Muhammad Usama Anjum
2025-07-03 1:59 ` Baochen Qiang
2025-07-07 8:19 ` Muhammad Usama Anjum
2025-07-07 9:00 ` Baochen Qiang
2025-07-07 13:11 ` Muhammad Usama Anjum
2025-07-08 1:43 ` Baochen Qiang
2025-07-08 9:12 ` Muhammad Usama Anjum [this message]
2025-07-08 10:38 ` Baochen Qiang
2025-06-30 7:43 ` [PATCH 3/3] bus: mhi: keep device context through suspend cycles Muhammad Usama Anjum
2025-07-01 10:26 ` Greg Kroah-Hartman
2025-07-08 10:15 ` Krishna Chaitanya Chundru
2025-07-10 15:07 ` Muhammad Usama Anjum
2025-07-10 17:17 ` Krishna Chaitanya Chundru
2025-07-11 10:22 ` Muhammad Usama Anjum
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=5c9843b5-d756-4a99-b93f-d32ed8f16e32@collabora.com \
--to=usama.anjum@collabora.com \
--cc=alexander.wilhelm@westermo.com \
--cc=ath11k@lists.infradead.org \
--cc=baochen.qiang@oss.qualcomm.com \
--cc=chentao@kylinos.cn \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=john@phrozen.org \
--cc=julia.lawall@lip6.fr \
--cc=kernel@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_mattleun@quicinc.com \
--cc=quic_mkenna@quicinc.com \
--cc=quic_msinada@quicinc.com \
--cc=quic_vnaralas@quicinc.com \
--cc=quic_yabdulra@quicinc.com \
--cc=sdias@codeaurora.org \
--cc=smohanad@codeaurora.org \
--cc=yanzhen@vivo.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;
as well as URLs for NNTP newsgroup(s).