summaryrefslogtreecommitdiff
path: root/src/mainboard/ibase/mb899/Kconfig
diff options
context:
space:
mode:
authorJon Murphy <jpmurphy@google.com>2024-11-25 13:48:02 -0700
committerJon Murphy <jpmurphy@google.com>2024-11-28 18:35:19 +0000
commit4f2c280e1d881e2d526c867f75c8216b60e7751b (patch)
tree3dbf56cf9a21acddce97ff6ca59df1465e82cd1d /src/mainboard/ibase/mb899/Kconfig
parent0b617c930082d00595a2d7427bc8ce7af6a9f9e9 (diff)
mb/google/zork: Update FP enable
Add/update FP enable/disable based on SKU ID. This is meant to resolve a UMA issue with devices that had the FPMCU populated on non-fp devices. Since the FPMCU is present, and the firmware enables the power GPIO's based on variant, not SKU, the devices were reporting data on fingerprint errantly. Specify the SKUs which should not have a FP sensor and default to true to maintain the legacy behavior for undefined devices and limit risk. Variants which do not have FP SKUs will be unaffected. BUG=b:354769653 TEST=Flash to zork, test FP. Disable test SKU, flash on zork, test FP. To test, run `ectool --name=cros_fp version` in the shell When enabled, the fpmcu fw version should be displayed. When disabled, an error should be displayed because the fpmcu is inaccessible. Change-Id: Ic6dc71013a1c0d5ee5263109eed87a1b31800232 Signed-off-by: Jon Murphy <jpmurphy@google.com> Reviewed-on: https://review.coreboot.org/c/coreboot/+/85294 Reviewed-by: Karthik Ramasubramanian <kramasub@google.com> Tested-by: build bot (Jenkins) <no-reply@coreboot.org>
Diffstat (limited to 'src/mainboard/ibase/mb899/Kconfig')
0 files changed, 0 insertions, 0 deletions