u-boot.git/lib/efi_driver/efi_uclass.c, branch next

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_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

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

efi_driver: use efi_close_protocol

2022-10-10T14:34:26+00:00

Avoid EFI_CALL() by using efi_close_protocol().

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

efi_driver: fix efi_uc_stop()

2022-10-10T14:34:25+00:00

We must always call EFI_EXIT() when returning from an EFIAPI function.

Fixes: 05ef48a2484b ("efi_driver: EFI block driver")
Signed-off-by: Heinrich Schuchardt 
Reviewed-by: Ilias Apalodimas

efi_driver: add init function to EFI block driver

2022-10-06T20:54:58+00:00

For handling added and removed block devices we need to register events
which has to be done when the driver is installed.

This patch only creates an empty init function that will be filled with
code later on. The function needs to be called before any EFI block devices
are used. Move the efi_driver_init() call to early init.

Signed-off-by: Heinrich Schuchardt

efi_driver: provide driver binding protocol to bind function

2022-10-06T20:54:57+00:00

DisconnectController() is based on the open protocol information created
when the driver opens a protocol with BY_CHILD_CONTROLLER or BY_DRIVER.

To create an open protocol information it is required to supply the handle
of the driver as agent handle. This information is available as field
DriverBindingHandle in the driver binding protocol.

Signed-off-by: Heinrich Schuchardt

efi_driver: simplify efi_uc_stop(), call efi_free_pool()

2022-10-06T20:54:57+00:00

We have exported efi_free_pool(). There is no need to use EFI_CALL().

Signed-off-by: Heinrich Schuchardt