From: Manivannan Sadhasivam <mani@kernel.org>
To: Jeff Johnson <jjohnson@kernel.org>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>,
Youssef Samir <quic_yabdulra@quicinc.com>,
Matthew Leung <quic_mattleun@quicinc.com>,
Carl Vanderlip <quic_carlv@quicinc.com>,
Yan Zhen <yanzhen@vivo.com>,
Jacek Lawrynowicz <jacek.lawrynowicz@linux.intel.com>,
Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kunwu Chan <chentao@kylinos.cn>,
"Dr. David Alan Gilbert" <linux@treblig.org>,
Troy Hanson <quic_thanson@quicinc.com>,
Manivannan Sadhasivam <mani@kernel.org>,
Muhammad Usama Anjum <usama.anjum@collabora.com>
Cc: kernel@collabora.com, sebastian.reichel@collabora.com,
Jeff Johnson <jeff.johnson@oss.qualcomm.com>,
Baochen Qiang <quic_bqiang@quicinc.com>,
Sumit Garg <sumit.garg@kernel.org>,
mhi@lists.linux.dev, linux-arm-msm@vger.kernel.org,
linux-kernel@vger.kernel.org, linux-wireless@vger.kernel.org,
ath11k@lists.infradead.org, ath12k@lists.infradead.org
Subject: Re: [PATCH v6] bus: mhi: host: don't free bhie tables during suspend/hibernation
Date: Tue, 17 Jun 2025 12:58:51 +0530 [thread overview]
Message-ID: <175014516328.16478.17449149106590025798.b4-ty@kernel.org> (raw)
In-Reply-To: <20250516184952.878726-1-usama.anjum@collabora.com>
On Fri, 16 May 2025 23:49:31 +0500, Muhammad Usama Anjum wrote:
> Fix dma_direct_alloc() failure at resume time during bhie_table
> allocation because of memory pressure. There is a report where at
> resume time, the memory from the dma doesn't get allocated and MHI
> fails to re-initialize.
>
> To fix it, don't free the memory at power down during suspend /
> hibernation. Instead, use the same allocated memory again after every
> resume / hibernation. This patch has been tested with resume and
> hibernation both.
>
> [...]
Applied, thanks!
[1/1] bus: mhi: host: don't free bhie tables during suspend/hibernation
commit: df75d6d7ce922645e674f5d591c7333f11027cdc
Note: I've modified the patch little bit to rename __mhi_unprepare_keep_dev to
mhi_deinit_dev_ctxt() and also reworded the description.
Best regards,
--
Manivannan Sadhasivam <mani@kernel.org>
next prev parent reply other threads:[~2025-06-17 7:29 UTC|newest]
Thread overview: 6+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-05-16 18:49 Muhammad Usama Anjum
2025-05-16 19:08 ` Jeff Hugo
2025-05-28 5:25 ` Muhammad Usama Anjum
2025-06-13 11:34 ` Muhammad Usama Anjum
2025-06-17 7:28 ` Manivannan Sadhasivam [this message]
2025-07-19 3:24 ` Manivannan Sadhasivam
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=175014516328.16478.17449149106590025798.b4-ty@kernel.org \
--to=mani@kernel.org \
--cc=ath11k@lists.infradead.org \
--cc=ath12k@lists.infradead.org \
--cc=chentao@kylinos.cn \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jacek.lawrynowicz@linux.intel.com \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=jeff.johnson@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=kernel@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=linux@treblig.org \
--cc=mhi@lists.linux.dev \
--cc=quic_bqiang@quicinc.com \
--cc=quic_carlv@quicinc.com \
--cc=quic_mattleun@quicinc.com \
--cc=quic_thanson@quicinc.com \
--cc=quic_yabdulra@quicinc.com \
--cc=sebastian.reichel@collabora.com \
--cc=sumit.garg@kernel.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®