[<prev] [next>] [<thread-prev] [thread-next>] [day] [month] [year] [list]
Message-ID: <CAHUa44GewV_GcBWk89foNu8EPVgQ03LvOTxzjgp5Smis34GWdA@mail.gmail.com>
Date: Wed, 25 Oct 2023 13:55:38 +0200
From: Jens Wiklander <jens.wiklander@...aro.org>
To: Sudeep Holla <sudeep.holla@....com>
Cc: linux-arm-kernel@...ts.infradead.org, linux-kernel@...r.kernel.org,
Coboy Chen <coboy.chen@...iatek.com>,
Lorenzo Pieralisi <lpieralisi@...nel.org>
Subject: Re: [PATCH 0/4] firmware: arm_ffa: Few fixes for FF-A notification support
Hi Sudeep,
On Tue, Oct 24, 2023 at 12:56 PM Sudeep Holla <sudeep.holla@....com> wrote:
>
> Hi,
>
> These are set of small fixes around FF-A notification support that are
> currently queued in -next. It is mostly to take care of absence of
> the notification support in the firmware as well as allowing them to be
> optional and continue initialisation even when the notification fails.
>
> Regards,
> Sudeep
>
> Signed-off-by: Sudeep Holla <sudeep.holla@....com>
> ---
> Sudeep Holla (4):
> firmware: arm_ffa: Allow FF-A initialisation even when notification fails
> firmware: arm_ffa: Setup the partitions after the notification initialisation
> firmware: arm_ffa: Add checks for the notification enabled state
> firmware: arm_ffa: Fix FFA notifications cleanup path
>
> drivers/firmware/arm_ffa/driver.c | 65 ++++++++++++++++++++++++++-------------
> 1 file changed, 44 insertions(+), 21 deletions(-)
Works as expected with and without FF-A notifications enabled in the
secure world.
Tested-by: Jens Wiklander <jens.wiklander@...aro.org>
Cheers,
Jens
> ---
> base-commit: bcefd1bf63b1ec9bb08067021cf47f0fad96f395
> change-id: 20231024-ffa-notification-fixes-9d5cf1e131ef
>
> Best regards,
> --
> Regards,
> Sudeep
>
Powered by blists - more mailing lists