5b0929f9d7
vboot code changes have eliminated the redundant call to WP the EC-RO region as protecting RW flash implies protecting both RO and RW flash, so the call to protect RO is redundant. google/rex currently takes about 17 ms to lock down the EC. Along with vboot changes, this patch drops argument to choose between RO and RW slot to protect while calling into `vb2ex_ec_protect()`. It ensures vb2ex_ec_protect() is explicitly meant for protecting RW regions. w/o this patch: 517:waiting for EC to allow higher power draw 846,196 (17,297) w/ this patch: 517:waiting for EC to allow higher power draw 838,258 (9,719) Additionally, update vboot submodule to upstream main to avoid the compilation error. Updating from commit id 35f50c3154e5: Fix build error when compiling without -DNDEBUG to commit id 034907b279c9db: vboot_reference: eliminate redundant call to write protect EC-RO Change-Id: I2974f0cb43ba800c2aaeac4876ebaa052b5ee793 Signed-off-by: Subrata Banik <subratabanik@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/75521 Tested-by: build bot (Jenkins) <no-reply@coreboot.org> Reviewed-by: Himanshu Sahdev <himanshu.sahdev@intel.com> Reviewed-by: Harsha B R <harsha.b.r@intel.com> Reviewed-by: Julius Werner <jwerner@chromium.org> |
||
|---|---|---|
| .. | ||
| amd_blobs@acf7395452 | ||
| arm-trusted-firmware@4c985e8674 | ||
| blobs@9df5910d68 | ||
| chromeec@e486b388a7 | ||
| cmocka@8931845c35 | ||
| ffs@3ec70fbc45 | ||
| fsp@6f2f17f3d3 | ||
| intel-microcode@2be47edc99 | ||
| intel-sec-tools@0031ac7344 | ||
| libgfxinit@066e52eeaa | ||
| libhwbase@8be5a82b85 | ||
| opensbi@5019fd124b | ||
| qc_blobs@33cc4f2fd8 | ||
| stm@1f3258261a | ||
| vboot@034907b279 | ||