Akash Asthana has posted comments on this change. ( https://review.coreboot.org/c/coreboot/+/25372 )
Change subject: sdm845: Add QUPv3 FW load & config ......................................................................
Patch Set 78:
(1 comment)
https://review.coreboot.org/c/coreboot/+/25372/6/src/mainboard/google/cheza/... File src/mainboard/google/cheza/qupv3_config.c:
https://review.coreboot.org/c/coreboot/+/25372/6/src/mainboard/google/cheza/... PS6, Line 18: struct se_cfg se_mappings[QUPV3_SE_MAX] =
But this is only a problem if we try to load different firmware onto the same QUP instance, right? T […]
Since coreboot is a single-threaded environment, loading of FW dynamically from respective protocol init function seems to be technically possible.
Also, we want to discuss below security concerns wrt FW driver.
We have a mechanism to lock FW content[RAM registers] from reading/writing after loading it to SE, to ensure that HLOS or non-secured environment cannot load bogus FWs to SEs.
To lock FW content we need to write to registers 1) se_geni_fw_multilock_msa 2) se_geni_fw_multilock_protns that is possible only from the secured environment. In mobile, we are loading FW from TZ(secured environment) hence we are able to lock it. We want to explore our options in coreboot.
We have a few more queries regarding the usage of the above features(dynamic loadability of FW) and scenarios.
I feel it's better to discuss it on call, can we setup a meeting for it?