From: Baochen Qiang <baochen.qiang@oss.qualcomm.com>
To: Muhammad Usama Anjum <usama.anjum@collabora.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
Youssef Samir <quic_yabdulra@quicinc.com>,
Matthew Leung <quic_mattleun@quicinc.com>,
Alexander Wilhelm <alexander.wilhelm@westermo.com>,
Kunwu Chan <chentao@kylinos.cn>,
Krishna Chaitanya Chundru <krishna.chundru@oss.qualcomm.com>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
Yan Zhen <yanzhen@vivo.com>, Sujeev Dias <sdias@codeaurora.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Siddartha Mohanadoss <smohanad@codeaurora.org>,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org
Cc: kernel@collabora.com
Subject: Re: [PATCH v2 0/3] bus: mhi: keep dma buffers through suspend/hibernation cycles
Date: Wed, 16 Jul 2025 11:36:45 +0800 [thread overview]
Message-ID: <bb1a5f3a-5ac0-434b-8da4-e43c996cfa30@oss.qualcomm.com> (raw)
In-Reply-To: <20250715132509.2643305-1-usama.anjum@collabora.com>
On 7/15/2025 9:25 PM, Muhammad Usama Anjum wrote:
> When there is memory pressure during resume and no DMA memory is
> available, the ath11k driver fails to resume. The driver currently
> frees its DMA memory during suspend or hibernate, and attempts to
> re-allocate it during resume. However, if the DMA memory has been
> consumed by other software in the meantime, these allocations can
> fail, leading to critical failures in the WiFi driver. It has been
> reported [1].
>
> Although I have recently fixed several instances [2] [3] to ensure
> DMA memory is not freed once allocated, we continue to receive
> reports of new failures.
>
> In this series, 3 more such cases are being fixed. There are still
> some cases which I'm trying to fix. They can be discussed separately.
>
> [1] https://lore.kernel.org/all/ead32f5b-730a-4b81-b38f-93d822f990c6@collabora.com
> [2] https://lore.kernel.org/all/20250428080242.466901-1-usama.anjum@collabora.com
> [3] https://lore.kernel.org/all/20250516184952.878726-1-usama.anjum@collabora.com
>
> Muhammad Usama Anjum (3):
> bus: mhi: host: keep bhi buffer through suspend cycle
> bus: mhi: host: keep bhie buffer through suspend cycle
> bus: mhi: keep device context through suspend cycles
>
> drivers/bus/mhi/host/boot.c | 44 ++++++++++++++++++++-------------
> drivers/bus/mhi/host/init.c | 41 ++++++++++++++++++++++++++----
> drivers/bus/mhi/host/internal.h | 2 ++
> include/linux/mhi.h | 2 ++
> 4 files changed, 67 insertions(+), 22 deletions(-)
>
changelog missing
next prev parent reply other threads:[~2025-07-16 3:36 UTC|newest]
Thread overview: 12+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-07-15 13:25 Muhammad Usama Anjum
2025-07-15 13:25 ` [PATCH v2 1/3] bus: mhi: host: keep bhi buffer through suspend cycle Muhammad Usama Anjum
2025-07-16 3:41 ` Baochen Qiang
2025-07-16 9:34 ` Greg Kroah-Hartman
2025-07-17 10:00 ` Muhammad Usama Anjum
2025-07-17 11:50 ` Greg Kroah-Hartman
2025-07-15 13:25 ` [PATCH v2 2/3] bus: mhi: host: keep bhie " Muhammad Usama Anjum
2025-07-16 9:35 ` Greg Kroah-Hartman
2025-07-15 13:25 ` [PATCH v2 3/3] bus: mhi: keep device context through suspend cycles Muhammad Usama Anjum
2025-07-16 9:35 ` Greg Kroah-Hartman
2025-07-16 3:36 ` Baochen Qiang [this message]
2025-07-17 10:01 ` [PATCH v2 0/3] bus: mhi: keep dma buffers through suspend/hibernation cycles 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=bb1a5f3a-5ac0-434b-8da4-e43c996cfa30@oss.qualcomm.com \
--to=baochen.qiang@oss.qualcomm.com \
--cc=alexander.wilhelm@westermo.com \
--cc=chentao@kylinos.cn \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=kernel@collabora.com \
--cc=krishna.chundru@oss.qualcomm.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mani@kernel.org \
--cc=mhi@lists.linux.dev \
--cc=quic_mattleun@quicinc.com \
--cc=quic_yabdulra@quicinc.com \
--cc=sdias@codeaurora.org \
--cc=smohanad@codeaurora.org \
--cc=usama.anjum@collabora.com \
--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
all inboxes | Powered by JetHome®