From: Muhammad Usama Anjum <usama.anjum@collabora.com>
To: Krishna Chaitanya Chundru <quic_krichai@quicinc.com>,
Manivannan Sadhasivam <manivannan.sadhasivam@linaro.org>,
Johannes Berg <johannes@sipsolutions.net>,
Jeff Johnson <jjohnson@kernel.org>,
Jeffrey Hugo <quic_jhugo@quicinc.com>,
Yan Zhen <yanzhen@vivo.com>,
Youssef Samir <quic_yabdulra@quicinc.com>,
Qiang Yu <quic_qianyu@quicinc.com>, Alex Elder <elder@kernel.org>,
Greg Kroah-Hartman <gregkh@linuxfoundation.org>,
Kunwu Chan <chentao@kylinos.cn>,
Jeff Hugo <jeff.hugo@oss.qualcomm.com>
Cc: kernel@collabora.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
Subject: Re: [PATCH v2] bus: mhi: host: don't free bhie tables during suspend/hibernation
Date: Mon, 14 Apr 2025 12:32:34 +0500 [thread overview]
Message-ID: <7d6b074c-8499-4984-b235-d1285b006ab3@collabora.com> (raw)
In-Reply-To: <1c0b2217-49d9-360c-ed60-db517eaf2ccc@quicinc.com>
On 4/12/25 6:22 AM, Krishna Chaitanya Chundru wrote:
>
> On 4/12/2025 12:02 AM, Muhammad Usama Anjum wrote:
>> On 4/11/25 1:39 PM, Krishna Chaitanya Chundru wrote:
>>>
>>>
>>> On 4/11/2025 12:32 PM, Muhammad Usama Anjum wrote:
>>>> On 4/11/25 8:37 AM, Krishna Chaitanya Chundru wrote:
>>>>>
>>>>>
>>>>> On 4/10/2025 8:26 PM, Muhammad Usama Anjum wrote:
>>>>>> Fix dma_direct_alloc() failure at resume time during bhie_table
>>>>>> allocation. There is a crash report where at resume time, the memory
>>>>>> from the dma doesn't get allocated and MHI fails to re-initialize.
>>>>>> There may be fragmentation of some kind which fails the allocation
>>>>>> call.
>>>>>>
>>>>>> 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.
>>>>>>
>>>>>> The rddm is of constant size for a given hardware. While the
>>>>>> fbc_image
>>>>>> size depends on the firmware. If the firmware changes, we'll free and
>>>>> If firmware image will change between suspend and resume ?
>>>> Yes, correct.
>>>>
>>> why the firmware image size will change between suspend & resume?
>>> who will update the firmware image after bootup?
>>> It is not expected behaviour.
>> I was trying to research if the firmware can change or not. I've not
>> found any documentation on it.
>>
>> If the firmare is updated in filesystem before suspend/hibernate, would
>> the new firwmare be loaded the next time kernel resumes as the older
>> firmware is no where to be found?
>>
>> What do you think about this?
>>
> I don't think firmware can be updated before suspend/hibernate. I don't
> see any reason why it can be updated. If you think it can be updated
> please quote relevant doc.
I've not found any documentation on it. Let's wait for others to review
and it it cannot be updated, I'll remove this part.
--
Regards,
Usama
next prev parent reply other threads:[~2025-04-14 7:33 UTC|newest]
Thread overview: 24+ messages / expand[flat|nested] mbox.gz Atom feed top
2025-04-10 14:56 [PATCH v2] bus: mhi: host: don't free bhie tables during suspend/hibernation Muhammad Usama Anjum
2025-04-10 17:00 ` Greg Kroah-Hartman
2025-04-11 18:47 ` Muhammad Usama Anjum
2025-04-11 3:37 ` Krishna Chaitanya Chundru
2025-04-11 7:02 ` Muhammad Usama Anjum
2025-04-11 8:39 ` Krishna Chaitanya Chundru
2025-04-11 18:32 ` Muhammad Usama Anjum
2025-04-12 1:22 ` Krishna Chaitanya Chundru
2025-04-14 7:32 ` Muhammad Usama Anjum [this message]
2025-04-14 14:14 ` Jeff Hugo
2025-04-18 8:10 ` Muhammad Usama Anjum
2025-04-18 14:08 ` Jeff Hugo
2025-04-22 7:23 ` Muhammad Usama Anjum
2025-04-22 14:22 ` Jeff Hugo
2025-04-23 6:41 ` Muhammad Usama Anjum
2025-04-11 16:10 ` Jeff Hugo
2025-04-11 19:10 ` Muhammad Usama Anjum
2025-04-25 7:04 ` Manivannan Sadhasivam
2025-04-25 7:14 ` Muhammad Usama Anjum
2025-04-25 7:32 ` Manivannan Sadhasivam
2025-04-25 7:42 ` Muhammad Usama Anjum
2025-04-25 8:59 ` Manivannan Sadhasivam
2025-04-25 11:41 ` Muhammad Usama Anjum
2025-04-25 14:47 ` 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=7d6b074c-8499-4984-b235-d1285b006ab3@collabora.com \
--to=usama.anjum@collabora.com \
--cc=ath11k@lists.infradead.org \
--cc=chentao@kylinos.cn \
--cc=elder@kernel.org \
--cc=gregkh@linuxfoundation.org \
--cc=jeff.hugo@oss.qualcomm.com \
--cc=jjohnson@kernel.org \
--cc=johannes@sipsolutions.net \
--cc=kernel@collabora.com \
--cc=linux-arm-msm@vger.kernel.org \
--cc=linux-kernel@vger.kernel.org \
--cc=linux-wireless@vger.kernel.org \
--cc=manivannan.sadhasivam@linaro.org \
--cc=mhi@lists.linux.dev \
--cc=quic_jhugo@quicinc.com \
--cc=quic_krichai@quicinc.com \
--cc=quic_qianyu@quicinc.com \
--cc=quic_yabdulra@quicinc.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