From: Carol Soto <csoto@nvidia.com>
To: Sudeep Holla <sudeep.holla@kernel.org>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mochs@nvidia.com
Subject: Re: [PATCH] firmware: arm_ffa: Unmap Rx/Tx buffers on shutdown
Date: Mon, 24 Aug 2026 11:33:08 -0500 [thread overview]
Message-ID: <4436a4ae-de40-4355-95b5-f5104ad30dd4@nvidia.com> (raw)
In-Reply-To: <c5f0fe8e-faa2-48d5-b6a1-370ba36b19bc@nvidia.com>
On 8/19/26 2:13 PM, Carol Soto wrote:
>
> On 8/19/26 2:08 AM, Sudeep Holla wrote:
>> I had posted a single line patch here[1]. The original
>> author/reported never
>> got back.
>>
>> -- Regards, Sudeep [1]
>> https://lore.kernel.org/all/20260729-nostalgic-accurate-raccoon-ab7d7e@sudeepholla
>
> Hi Sudeep,
>
> Thanks for the pointer. I tried your patch from [1] and it fixes the
> kexec issue on my setup.
>
> I also tried limiting the shutdown patch to just RXTX_UNMAP, but that
> is not sufficient here.
> The next kernel can still fail notificaion setup with:
>
> ARM FF-A: Notification bitmap create error -13
>
> So I agree that using the normal FF-A cleanup patch from shutdown
> looks like the right approach,
> since it tears down the notification bitmap state as well as unmapping
> the Rx/Tx buffers.
>
> Are you planning to submit that change to resolve this issue?
>
> Thanks,
> Carol
Hi Suddep,
Just following up on the FF-A kexec issue. Do you plan to submit your
shutdown cleanup patch, or would you prefer that I send a v2 based on
that approach?
Thanks,
Carol
prev parent reply other threads:[~2026-08-24 16:33 UTC|newest]
Thread overview: 4+ messages / expand[flat|nested] mbox.gz Atom feed top
2026-08-18 22:44 [PATCH] firmware: arm_ffa: Unmap Rx/Tx buffers on shutdown Carol L Soto
2026-08-19 7:08 ` Sudeep Holla
2026-08-19 19:13 ` Carol Soto
2026-08-24 16:33 ` Carol Soto [this message]
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=4436a4ae-de40-4355-95b5-f5104ad30dd4@nvidia.com \
--to=csoto@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochs@nvidia.com \
--cc=sudeep.holla@kernel.org \
/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).