u-boot.lists.denx.de archive mirror
 help / color / mirror / Atom feed
From: Paul Barker <paul.barker@sancloud.com>
To: Heinrich Schuchardt <xypron.glpk@gmx.de>, u-boot@lists.denx.de
Subject: Re: [RFC PATCH 0/2] Support UEFI SPI I/O protocol
Date: Sat, 9 Jul 2022 11:35:42 +0100	[thread overview]
Message-ID: <48a2305b-2eb3-6731-6ede-fc89cd82a16c@sancloud.com> (raw)
In-Reply-To: <920AB316-3630-4487-B26E-F3ACF4579488@gmx.de>

Hi Heinrich,

On 08/07/2022 21:33, Heinrich Schuchardt wrote:
> Hello Paul,
> 
> up to now U-Boot does not implement any part of the PI specification. Please, explain why we should implement this protocol.

Implementing this protocol allows a UEFI application to interact with a 
device on the SPI bus. Similar protocols exist in the main UEFI 
specification for passing commands to an NVMe or SD/eMMC device. The 
code here is self-contained and easy to enable/disable at compile time.

Our goal in adding support for this protocol is to allow our UEFI 
application to interact with the Micron Authenta flash device on the 
SanCloud BBE Lite board and other future platforms. The application will 
link against mbedtls to provide cryptographic functions so isolating our 
application code in this way helps to keep the u-boot code size small.

> For all EFI protocols there should be a test that can be run in our Gitlab CI showing that it is working correctly.

I'm intending to add test cases based on the mock/sandbox SPI driver 
before this is submitted as a final/non-RFC patch series. I'd like to 
get some feedback on the overall approach at this stage as that will 
influence how the tests interact with the implementation.

Thanks,

-- 
Paul Barker
Principal Software Engineer
SanCloud Ltd

e: paul.barker@sancloud.com
w: https://sancloud.com/

      reply	other threads:[~2022-07-09 10:35 UTC|newest]

Thread overview: 8+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-07-08  9:45 [RFC PATCH 0/2] Support UEFI SPI I/O protocol Paul Barker
2022-07-08  9:45 ` [RFC PATCH 1/2] efi_loader: Add SPI I/O protocol support Paul Barker
2022-07-08 20:21   ` Tom Rini
2022-07-11 13:12   ` Ilias Apalodimas
2022-07-11 13:25     ` Paul Barker
2022-07-08  9:45 ` [RFC PATCH 2/2] arm: dts: am335x-sancloud-bbe-lite: UEFI SPI export Paul Barker
2022-07-08 20:33 ` [RFC PATCH 0/2] Support UEFI SPI I/O protocol Heinrich Schuchardt
2022-07-09 10:35   ` Paul Barker [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=48a2305b-2eb3-6731-6ede-fc89cd82a16c@sancloud.com \
    --to=paul.barker@sancloud.com \
    --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;
as well as URLs for NNTP newsgroup(s).