From: Sudeep Holla <sudeep.holla@kernel.org>
To: Carol Soto <csoto@nvidia.com>
Cc: linux-arm-kernel@lists.infradead.org,
linux-kernel@vger.kernel.org, mochs@nvidia.com,
Sudeep Holla <sudeep.holla@kernel.org>
Subject: Re: [PATCH] firmware: arm_ffa: Unmap Rx/Tx buffers on shutdown
Date: Tue, 1 Sep 2026 08:22:59 +0100 [thread overview]
Message-ID: <20260901-nimble-uber-walrus-7a3ac0@sudeepholla> (raw)
In-Reply-To: <4436a4ae-de40-4355-95b5-f5104ad30dd4@nvidia.com>
On Mon, Aug 24, 2026 at 11:33:08AM -0500, Carol Soto wrote:
>
> 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?
>
I was away for a while, I will post it as a proper patch soon. Sorry for the
delay.
--
Regards,
Sudeep
prev parent reply other threads:[~2026-09-01 7:23 UTC|newest]
Thread overview: 5+ 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
2026-09-01 7:22 ` Sudeep Holla [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=20260901-nimble-uber-walrus-7a3ac0@sudeepholla \
--to=sudeep.holla@kernel.org \
--cc=csoto@nvidia.com \
--cc=linux-arm-kernel@lists.infradead.org \
--cc=linux-kernel@vger.kernel.org \
--cc=mochs@nvidia.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