public inbox for u-boot@lists.denx.de
 help / color / mirror / Atom feed
From: Abdellatif El Khlifi <abdellatif.elkhlifi@arm.com>
To: ilias.apalodimas@linaro.org, xypron.glpk@gmx.de
Cc: sjg@chromium.org, Drew.Reed@arm.com, u-boot@lists.denx.de, nd@arm.com
Subject: Adding EFI runtime support to the Arm's FF-A bus
Date: Thu, 14 Dec 2023 15:53:46 +0000	[thread overview]
Message-ID: <20231214155346.GB295924@e130802.arm.com> (raw)

Hi guys,

I'd like to ask for advice regarding adding EFI RT support to the Arm's FF-A bus
in U-Boot.

The objective is to enable the FF-A messaging APIs in EFI RT to be used for
comms with the secure world. This will help getting/setting EFI variables
through FF-A.

The existing FF-A APIs in U-Boot call the DM APIs (which are not available at RT).

Two possible solutions:

1/ having the entire U-Boot in RT space (as Simon stated in this discussion[1])

2/ Create an RT variant for the FF-A APIs needed.
      These RT variant don't call the DM APIs
      (e.g: ffa_mm_communicate_runtime, ffa_sync_send_receive_runtime, ...)

What do you recommend please ?

[1]: https://lore.kernel.org/all/CAPnjgZ21qLnSFcCJ9rPQXEfQf-NjMBF3kYUDBBOc6WUQXQtDEA@mail.gmail.com/

Cheers,
Abdellatif

             reply	other threads:[~2023-12-14 15:53 UTC|newest]

Thread overview: 23+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2023-12-14 15:53 Abdellatif El Khlifi [this message]
2023-12-14 16:47 ` Adding EFI runtime support to the Arm's FF-A bus Mark Kettenis
2023-12-14 19:47   ` Ilias Apalodimas
2023-12-18 15:01     ` Simon Glass
2023-12-18 20:59       ` Heinrich Schuchardt
2023-12-19 10:11         ` Michael Walle
2023-12-19 12:27           ` Mark Kettenis
2023-12-19 12:47             ` Michael Walle
2023-12-19 15:40               ` Tom Rini
2023-12-20  6:17               ` Ilias Apalodimas
2023-12-20 15:43                 ` Peter Robinson
2023-12-20 22:57                   ` Shantur Rathore
2023-12-21  6:29                     ` Ilias Apalodimas
2023-12-21 14:36                       ` Shantur Rathore
2023-12-27 14:06                         ` Ilias Apalodimas
2023-12-19 15:22         ` Abdellatif El Khlifi
2023-12-20  4:47         ` Simon Glass
2023-12-18 16:59     ` Abdellatif El Khlifi
2024-01-08 14:12       ` Abdellatif El Khlifi
2024-01-08 14:27         ` Heinrich Schuchardt
2024-01-08 14:35           ` Ilias Apalodimas
2024-01-08 16:34             ` Abdellatif El Khlifi
2023-12-18 17:01   ` Abdellatif El Khlifi

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=20231214155346.GB295924@e130802.arm.com \
    --to=abdellatif.elkhlifi@arm.com \
    --cc=Drew.Reed@arm.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=nd@arm.com \
    --cc=sjg@chromium.org \
    --cc=u-boot@lists.denx.de \
    --cc=xypron.glpk@gmx.de \
    /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