[PATCH 5/7] configs: qcom: enable FIT capsule support by default

[Balaji Selvanathan]

Hi Ilias,

On 5/22/2026 12:16 PM, Ilias Apalodimas wrote:
> Hi Balaji,
>
> On Fri, 22 May 2026 at 09:10, Balaji Selvanathan
> <balaji.selvanathan at oss.qualcomm.com> wrote:
>> Switch from CONFIG_EFI_CAPSULE_FIRMWARE_RAW to
>> CONFIG_EFI_CAPSULE_FIRMWARE_FIT in the default Qualcomm
>> configuration.
>>
>> Signed-off-by: Balaji Selvanathan <balaji.selvanathan at oss.qualcomm.com>
>> ---
>>   configs/qcom_defconfig | 2 +-
>>   1 file changed, 1 insertion(+), 1 deletion(-)
>>
>> diff --git a/configs/qcom_defconfig b/configs/qcom_defconfig
>> index d0d54ec5a70..25059d2e6b4 100644
>> --- a/configs/qcom_defconfig
>> +++ b/configs/qcom_defconfig
>> @@ -9,7 +9,7 @@ CONFIG_SYS_LOAD_ADDR=0xA0000000
>>   # CONFIG_EFI_HAVE_RUNTIME_RESET is not set
>>   CONFIG_EFI_RUNTIME_UPDATE_CAPSULE=y
>>   CONFIG_EFI_CAPSULE_ON_DISK=y
>> -CONFIG_EFI_CAPSULE_FIRMWARE_RAW=y
>> +CONFIG_EFI_CAPSULE_FIRMWARE_FIT=y
> Why? The reason we added FIT back then is that we lacked capsule
> authentication. Is there a reason you prfer FIT images in a capsule?
>
> Thanks
> /Ilias

We want to use the existing FIT based framework (in efi_firmware.c), 
where we store binaries of multiple firmware in a single FIT image and 
then we place that FIT image in a capsule's payload. By this way, we can 
update multiple firmware ('s partitions) using a single capsule.

Regards,

Balaji

>>   CONFIG_BUTTON_CMD=y
>>   CONFIG_FIT=y
>>   CONFIG_FIT_VERBOSE=y
>>
>> --
>> 2.34.1
>>