On 5/5/26 16:18, Zhuoying Cai wrote:
[...]
> +typedef struct SecureIplCompAddrRange {
> + bool is_signed;
> + uint64_t start_addr;
> + uint64_t end_addr;
> +} SecureIplCompAddrRange;
> +
> +/*
> + * Custom struct for managing a list of secure IPL component address ranges.
> + * Tracks up to MAX_COMP_ENTRIES address ranges with an num counter.
> + */
> +typedef struct SecureIplCompAddrRangeList {
> + SecureIplCompAddrRange comp_addr_range[MAX_COMP_ENTRIES];
What about using a IplDeviceComponentEntry here? It has an addr (same
as start_addr), length (same as end_addr = start + length), and flags
(can be checked if it's signed).
In fact, couldn't the existing IplDeviceComponentEntry array inside the
IplDeviceComponentList be used? Then these two data structures aren't
needed.
> + int num;
> +} SecureIplCompAddrRangeList;
> +
--
Regards,
Collin
