I'm not sure why you would add an API to allow setting this explicitly, that's not really how it is supposed to work according to the spec. New TLs are always supposed to start with an alignment requirement of 8 (2^3) and then automatically increase that value if a TE gets added that has a larger requirement. There should be no use case where you'd want to initially create a TL that already has a larger number in that field (it doesn't make any difference... in particular, note that just because the alignment field has a larger value doesn't mean that the start of the TL must be aligned to that larger boundary; the field is only used to preserve the offset from the next alignment boundary during relocation).
- [PATCH 09/14] bloblist: Checksum the entire bloblist Simon Glass
- [PATCH 10/14] bloblist: Handle alignment with a void entry Simon Glass
- [PATCH 06/14] bloblist: Drop the flags value Simon Glass
- [PATCH 11/14] bloblist: Reduce blob-header size Simon Glass
- Re: [PATCH 11/14] bloblist: Reduce blob-header size Julius Werner
- [PATCH 07/14] bloblist: Drop the spare values Simon Glass
- [PATCH 12/14] bloblist: Reduce bloblist header size Simon Glass
- [PATCH 08/14] bloblist: Change the checksum algorithm Simon Glass
- [PATCH 13/14] bloblist: Add alignment to bloblist_new() Simon Glass
- Re: [PATCH 13/14] bloblist: Add alignment to bloblist_n... Julius Werner
- [PATCH 14/14] bloblist: Update documentation and header comm... Simon Glass