linux-kernel.vger.kernel.org archive mirror
 help / color / mirror / Atom feed
From: Jens Wiklander <jens.wiklander@linaro.org>
To: Sumit Garg <sumit.garg@linaro.org>
Cc: linux-kernel@vger.kernel.org, op-tee@lists.trustedfirmware.org,
	Jerome Forissier <jerome.forissier@linaro.org>,
	Sudeep Holla <sudeep.holla@arm.com>,
	Marc Bonnici <marc.bonnici@arm.com>,
	Olivier Deprez <Olivier.Deprez@arm.com>,
	Lorenzo Pieralisi <lpieralisi@kernel.org>
Subject: Re: [PATCH 0/2] OP-TEE FF-A notifications
Date: Thu, 2 Nov 2023 12:59:25 +0100	[thread overview]
Message-ID: <20231102115925.GA1233092@rayden> (raw)
In-Reply-To: <CAFA6WYOYRQ4BgyUE90EwAVULsa=qDkZ4C=0rX49e-E3LOvyz6Q@mail.gmail.com>

Hi Sumit,

On Mon, Oct 30, 2023 at 11:32:47AM +0530, Sumit Garg wrote:
> Hi Jens,
> 
> On Thu, 26 Oct 2023 at 13:34, Jens Wiklander <jens.wiklander@linaro.org> wrote:
> >
> > Hi all,
> >
> > This patchset adds support for using FF-A notifications as a delivery
> > mechanism of asynchronous notifications from OP-TEE running in the secure
> > world. Support for asynchronous notifications via the SMC ABI was added in
> > [1], here we add the counterpart needed when using the the FF-A ABI.
> >
> > Support for FF-A notifications is added with [2] and this patch set is based
> > on Sudeeps tree at [3].
> 
> It's good to see FF-A notifications support coming through. The good
> aspect here is that FF-A uses a common secure world SGI for
> notifications and doesn't have to deal with platform specific reserved
> SPI for notifications.
> 
> From OP-TEE point of view I think most of the secure SGI donation base
> would be common, so can we switch the SMC ABI to use this donated
> secure world SGI for notifications too?

The SMC ABI driver picks up the interrupt used for notification from
device-tree, so there's a chance that it just works if a donated SGI is
supplied instead. We'll need some changes in the secure world side of
OP-TEE, but they wouldn't affect the ABI.

Cheers,
Jens

> 
> -Sumit
> 
> >
> > [1] https://lore.kernel.org/lkml/20211103090255.998070-1-jens.wiklander@linaro.org/
> > [2] https://lore.kernel.org/linux-arm-kernel/20231005-ffa_v1-1_notif-v4-0-cddd3237809c@arm.com/
> > [3] https://git.kernel.org/pub/scm/linux/kernel/git/sudeep.holla/linux.git/tag/?h=ffa-updates-6.7
> >     commit bcefd1bf63b1 ("firmware: arm_ffa: Upgrade the driver version to v1.1")
> >
> > Thanks,
> > Jens
> >
> > Jens Wiklander (2):
> >   optee: provide optee_do_bottom_half() as a common function
> >   optee: ffa_abi: add asynchronous notifications
> >
> >  drivers/tee/optee/call.c          | 31 ++++++++++-
> >  drivers/tee/optee/ffa_abi.c       | 91 ++++++++++++++++++++++++++++++-
> >  drivers/tee/optee/optee_ffa.h     | 28 ++++++++--
> >  drivers/tee/optee/optee_private.h |  9 ++-
> >  drivers/tee/optee/smc_abi.c       | 36 ++----------
> >  5 files changed, 153 insertions(+), 42 deletions(-)
> >
> >
> > base-commit: bcefd1bf63b1ec9bb08067021cf47f0fad96f395
> > --
> > 2.34.1
> >

  reply	other threads:[~2023-11-02 11:59 UTC|newest]

Thread overview: 16+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-10-26  8:04 [PATCH 0/2] OP-TEE FF-A notifications Jens Wiklander
2023-10-26  8:04 ` [PATCH 1/2] optee: provide optee_do_bottom_half() as a common function Jens Wiklander
2023-10-30  6:53   ` Sumit Garg
2023-10-26  8:04 ` [PATCH 2/2] optee: ffa_abi: add asynchronous notifications Jens Wiklander
2023-11-06 11:08   ` Sumit Garg
2023-10-30  6:02 ` [PATCH 0/2] OP-TEE FF-A notifications Sumit Garg
2023-11-02 11:59   ` Jens Wiklander [this message]
2023-11-02 12:16     ` Sumit Garg
2023-11-02 13:16       ` Jens Wiklander
2023-11-02 14:05         ` Sumit Garg
2023-11-03  8:02           ` Jens Wiklander
2023-11-03  8:53             ` Sumit Garg
2023-11-06  8:39               ` Jens Wiklander
2023-11-06 10:51                 ` Sumit Garg
2023-11-07 11:46 ` Sudeep Holla
2023-11-07 17:06   ` Jens Wiklander

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=20231102115925.GA1233092@rayden \
    --to=jens.wiklander@linaro.org \
    --cc=Olivier.Deprez@arm.com \
    --cc=jerome.forissier@linaro.org \
    --cc=linux-kernel@vger.kernel.org \
    --cc=lpieralisi@kernel.org \
    --cc=marc.bonnici@arm.com \
    --cc=op-tee@lists.trustedfirmware.org \
    --cc=sudeep.holla@arm.com \
    --cc=sumit.garg@linaro.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).