[S] Change in coreboot[main]: vc/google/chromeos: Add configurable compression for logo file in cbfs

[Subrata Banik (Code Review)]

Attention is currently required from: Ashish Kumar Mishra, Julius Werner, Karthik Ramasubramanian, Shelley Chen.

Subrata Banik has posted comments on this change by Ashish Kumar Mishra. ( https://review.coreboot.org/c/coreboot/+/83420?usp=email )

Change subject: vc/google/chromeos: Add configurable compression for logo file in cbfs
......................................................................

Patch Set 2:

(1 comment)

Patchset:

PS2:
> Is there really a platform where the most efficient compression algorithm for ramstage is LZMA but for the logo is LZ4? They get loaded under very similar conditions, so usually what's best for one should be best for the other.
>
> I'd prefer to avoid having separate compression Kconfigs for every single file that all do their own thing. There should usually be a single answer per platform which algorithm is better that applies the same to all post-RAM files.

I don't think there is any good or golden answer to this because for 32MB platform, we can take liberty to use LZ4 for most blobs to gain boot time in exchange of SPI size growth bt that is not true for 16MB platform where the SPI is so full that even 10KB makes significant impact hence, we have to choose the optimal ones to ensure size is taking higher priority.