u-boot-toradex.git/lib/efi_driver, branch master

efi_driver: don't leak name in efi_bl_create_block_device()

2025-11-06T22:26:28+00:00

blk_create_devicef() uses a copy of parameter name.
We can use a local variable.

Reviewed-by: Bin Meng 
Reviewed-by: Ilias Apalodimas 
Signed-off-by: Heinrich Schuchardt

efi_driver: typo 'to be write'

2025-11-06T22:26:28+00:00

%s/to be write/to write/

Reviewed-by: Bin Meng 
Signed-off-by: Heinrich Schuchardt

efi_driver: correct formatting in efi_uc_stop()

2025-11-06T22:26:28+00:00

Correct indentation.

Reviewed-by: Bin Meng 
Signed-off-by: Heinrich Schuchardt

efi_loader: Separate device path into its own header

2025-05-25T09:27:18+00:00

These functions are useful for the EFI app. As a first step towards
making these available outside lib/efi_loader, create a separate header
file and include it where needed. Add proper comments to the functions,
since many are missing at present.

Signed-off-by: Simon Glass 
Reviewed-by: Heinrich Schuchardt

efi_driver: create a parent device for all EFI block devices

2025-02-20T10:07:44+00:00

Up to now root has been the parent device for all block devices created via
calling ConnectController(). This does not work well together with the
implementation of bootstd.

Add a dummy parent device for all EFI block devices.

With this change EFI block devices are also accessible via commands like
'cat', 'load', and 'ls'.

    => dm tree
     Class     Seq    Probed  Driver                Name
    -----------------------------------------------------------
     efi           0  [ + ]   EFI block driver      `-- efi
     blk           3  [ + ]   efi_blk                   `-- efi.efiblk#0
     partition     0  [ + ]   blk_partition                 `-- efi.efiblk#0:1

    => ls efiloader 0:1
           13   hello.txt
            7   u-boot.txt
    2 file(s), 0 dir(s)

    => cat efiloader 0:1 hello.txt
    Hello world!

    => efidebug dh
    0000000018df1700 (efi.efiblk#0:1)
      /VenHw(dbca4c98-6cb0-694d-0872-819c650cb7b8)/HD(1,MBR,0xd1535d21,0x1,0x7f)
      Block IO
      Simple File System

Adjust the event dump unit test to consider the new event spy.

Signed-off-by: Heinrich Schuchardt

efi_loader: use LOGC_EFI consistently

2025-01-26T10:06:56+00:00

The log category should be LOGC_EFI all over the EFI sub-system.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Ilias Apalodimas

efi_driver: use blk_create_devicef()

2024-10-18T15:05:19+00:00

The EFI block device driver is the only user of blk_create_device() outside
the block device uclass. Use blk_create_devicef() instead like other block
device drivers.

Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Simon Glass

efi_driver: provide SBI based runtime system reset

2024-02-28T13:38:47+00:00

On RISC-V systems system the Supervisory Binary Interface provides system
reset and poweroff. Use it at EFI runtime.

Signed-off-by: Heinrich Schuchardt

lib: Remove inclusion from these files

2023-12-21T13:54:37+00:00

After some header file cleanups to add missing include files, remove
common.h from all files in the lib directory. This primarily means just
dropping the line but in a few cases we need to add in other header
files now.

Reviewed-by: Simon Glass 
Signed-off-by: Tom Rini

efi_loader: make efi_delete_handle() follow the EFI spec

2023-07-28T09:36:37+00:00

The EFI doesn't allow removal of handles, unless all hosted protocols
are cleanly removed.  Our efi_delete_handle() is a bit intrusive.
Although it does try to delete protocols before removing a handle,
it doesn't care if that fails.  Instead it only returns an error if the
handle is invalid. On top of that none of the callers of that function
check the return code.

So let's rewrite this in a way that fits the EFI spec better.  Instead
of forcing the handle removal, gracefully uninstall all the handle
protocols.  According to the EFI spec when the last protocol is removed
the handle will be deleted.  Also switch all the callers and check the
return code. Some callers can't do anything useful apart from reporting
an error.  The disk related functions on the other hand, can prevent a
medium that is being used by EFI from removal.

The only function that doesn't check the result is efi_delete_image().
But that function needs a bigger rework anyway, so we can clean it up in
the future

Signed-off-by: Ilias Apalodimas 
Reviewed-by: Heinrich Schuchardt