[M] Change in coreboot[main]: drivers/wifi: Support 320Mhz Bandwidth Enablement per MCC

[Jérémy Compostella (Code Review)]

Attention is currently required from: Bob Moragues, Bora Guvendik, Cliff Huang, Eric Lai, Hannah Williams, Poornima Tom, Ravishankar Sarawadi, Subrata Banik, YH Lin, [e-mail].

Jérémy Compostella has posted comments on this change by Poornima Tom. ( https://review.coreboot.org/c/coreboot/+/81790?usp=email )

Change subject: drivers/wifi: Support 320Mhz Bandwidth Enablement per MCC
......................................................................

Patch Set 11:

(3 comments)

File src/drivers/wifi/generic/acpi.c:

https://review.coreboot.org/c/coreboot/+/81790/comment/3c771358_c4b14d2d?usp... :
PS10, Line 542: s
> should be `const` as well?

Done

File src/include/sar.h:

https://review.coreboot.org/c/coreboot/+/81790/comment/2ba3fc17_4b775293?usp... :
PS10, Line 15: WBEM_REVISION
> which spec should decide if the revision may see an uprev in future ?

Document #559910 Intel Connectivity Platforms BIOS Guidelines define the WBEM table and it revisions. It currently support a single WBEM revision (revision 0).

The revision required for the platform would depend on system and requirement definitions.

https://review.coreboot.org/c/coreboot/+/81790/comment/770c2b0a_0955f174?usp... :
PS10, Line 15: WBEM_REVISION
> which spec should decide if the revision may see an uprev in future ?

Document #559910 Intel Connectivity Platforms BIOS Guidelines define all the variation / revision available. There is a currently just a single revision for WBEM.

The uprev decision would come a board / system requirement. Like an extra needed field if it ever happen on day.

I did not use the `MAX_WBEM_REVISION` approach because it does not make sense at this stage and that's something which can be done depending on how requirements evolve in the future.