Apologies I just noticed a few things [...]
> > > > +config EFI_VARIABLE_SF_STORE > > + bool "Store non-volatile UEFI variables in SPI Flash" > > + depends on SPI_FLASH > > + help > > + Select this option if you want non-volatile UEFI variables to be > > + stored in SPI Flash. > > + > > + Define CONFIG_EFI_VARIABLE_SF_OFFSET as offset in SPI Flash to > > use as > > + the storage for variables. CONFIG_EFI_VAR_BUF_SIZE defines the > > space > > + needed. > > + > > + Note that SPI Flash devices have a limited number of program/erase > > + cycles. Frequent updates to UEFI variables may cause excessive > > wear > > + and can permanently damage the flash device, particularly on SPI > > NAND > > + or low-end SPI NOR parts without wear leveling. This option > > should be > > + used with care on such systems, and is not recommended for > > platforms > > + where UEFI variables are updated frequently. > > + > > config EFI_MM_COMM_TEE > > bool "UEFI variables storage service via the trusted world" > > depends on OPTEE > > @@ -152,7 +170,7 @@ endchoice > > > > config EFI_RT_VOLATILE_STORE > > bool "Allow variable runtime services in volatile storage (e.g RAM)" > > - depends on EFI_VARIABLE_FILE_STORE > > + depends on EFI_VARIABLE_FILE_STORE || EFI_VARIABLE_SF_STORE > > help > > When EFI variables are stored on file we don't allow > > SetVariableRT, > > since the OS doesn't know how to write that file. At the same time > > @@ -193,6 +211,20 @@ config FFA_SHARED_MM_BUF_ADDR > > the MM SP in secure world. > > It is assumed that the MM SP knows the address of the shared MM > > communication buffer. > > > > +config EFI_VARIABLE_SF_OFFSET > > + hex "EFI variables in SPI flash offset" > > + depends on EFI_VARIABLE_SF_STORE > > + help > > + Offset from the start of the SPI Flash where EFI variables will > > be stored. > > + This should be aligned to the sector size of SPI Flash. > > + > > +config EFI_VARIABLE_SF_DEVICE_INDEX > > + int "Device Index for target SPI Flash" Dont we need a depend here as well? [...] Thanks /Ilias
