All of lore.kernel.org
 help / color / mirror / Atom feed
From: Paul Barker <paul.barker@sancloud.com>
To: Simon Glass <sjg@chromium.org>, Paul Barker <paul.barker@sancloud.com>
Cc: u-boot@lists.denx.de, Tom Rini <trini@konsulko.com>,
	Heinrich Schuchardt <xypron.glpk@gmx.de>,
	Ilias Apalodimas <ilias.apalodimas@linaro.org>,
	Jagan Teki <jagan@amarulasolutions.com>
Subject: Re: [PATCH v5 1/3] efi_loader: Add SPI I/O protocol support
Date: Wed, 14 Dec 2022 09:57:27 +0000	[thread overview]
Message-ID: <6371bab6-f9a1-6a59-7d50-d2a872092794@sancloud.com> (raw)
In-Reply-To: <CAPnjgZ2Gn8Bq_wg_uA_axo1bk2qvx0RVLo7P++sAinQr9k7W3A@mail.gmail.com>

On 14/12/2022 04:39, Simon Glass wrote:
> Hi Paul,
> 
> On Wed, 23 Nov 2022 at 10:50, Paul Barker <paul.barker@sancloud.com> wrote:
>>
>> This addition allows UEFI applications running under u-boot to access
>> peripherals on SPI busses. It is based on the UEFI Platform
>> Initialization (PI) Specification, Version 1.7 Errata A (April 2020).
>> Only the core functionality required to discover SPI peripherals and
>> communicate with them is currently implemented. Other functionality such
>> as the legacy SPI controller interface and the ability to update the SPI
>> peripheral object associated with a particular SPI I/O protocol object
>> is currently unimplemented.
>>
>> The following protocols are defined:
>> * EFI_SPI_CONFIGURATION_PROTOCOL
>> * EFI_SPI_IO_PROTOCOL
>> * EFI_LEGACY_SPI_CONTROLLER_PROTOCOL
>>
>> Since there are no open source implementations of these protocols to use
>> as an example, educated guesses/hacks have been made in cases where the
>> UEFI PI specification is unclear and these are documented in comments.
>>
>> This implementation has been tested on the SanCloud BBE Lite and allowed
>> a UEFI test application to successfully communicate with a Micron
>> Authenta flash device connected via the SPI bus.
>>
>> Signed-off-by: Paul Barker <paul.barker@sancloud.com>
>> ---
>>  MAINTAINERS                       |   6 +
>>  configs/am335x_evm_defconfig      |   1 +
>>  include/efi_api.h                 |   4 +
>>  include/efi_loader.h              |   4 +
>>  include/efi_spi_protocol.h        | 166 +++++++++
>>  lib/efi_loader/Kconfig            |   8 +
>>  lib/efi_loader/Makefile           |   1 +
>>  lib/efi_loader/efi_setup.c        |   6 +
>>  lib/efi_loader/efi_spi_protocol.c | 576 ++++++++++++++++++++++++++++++
>>  lib/uuid.c                        |   4 +
>>  10 files changed, 776 insertions(+)
>>  create mode 100644 include/efi_spi_protocol.h
>>  create mode 100644 lib/efi_loader/efi_spi_protocol.c
> 
> This should have a sandbox test as well. See test/dm/spi.c or sf.c for examples.

Hi Simon,

There is a test case in patch 2 of this series, is that what you're
looking for? It was split out as requested in the review of v3 of this
series.

Thanks,

-- 
Paul Barker
Principal Software Engineer
SanCloud Ltd

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


  reply	other threads:[~2022-12-14  9:57 UTC|newest]

Thread overview: 19+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2022-11-23 17:50 [PATCH v5 0/3] Support UEFI SPI I/O protocol Paul Barker
2022-11-23 17:50 ` [PATCH v5 1/3] efi_loader: Add SPI I/O protocol support Paul Barker
2022-12-13  7:15   ` Ilias Apalodimas
2022-12-24 12:25     ` Paul Barker
2022-12-24 14:09       ` Heinrich Schuchardt
2023-01-11 13:02         ` Paul Barker
2022-12-14  4:39   ` Simon Glass
2022-12-14  9:57     ` Paul Barker [this message]
2022-12-15 14:24       ` Simon Glass
2022-11-23 17:50 ` [PATCH v5 2/3] efi_selftest: Add tests for SPI " Paul Barker
2022-12-15 14:24   ` Simon Glass
2022-11-23 17:50 ` [PATCH v5 3/3] arm: dts: am335x-sancloud-bbe-lite: UEFI SPI export Paul Barker
2022-12-20 15:55   ` Rob Herring
2022-12-24 12:03     ` Paul Barker
2022-12-24 16:51       ` Tom Rini
2023-01-03 19:27       ` Rob Herring
2023-01-11 12:19         ` Paul Barker
2022-12-12  9:29 ` [PATCH v5 0/3] Support UEFI SPI I/O protocol Paul Barker
2022-12-12  9:41   ` Ilias Apalodimas

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=6371bab6-f9a1-6a59-7d50-d2a872092794@sancloud.com \
    --to=paul.barker@sancloud.com \
    --cc=ilias.apalodimas@linaro.org \
    --cc=jagan@amarulasolutions.com \
    --cc=sjg@chromium.org \
    --cc=trini@konsulko.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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.