diff options
| author | Tom Hughes <tomhughes@chromium.org> | 2020-10-29 16:31:10 -0700 |
|---|---|---|
| committer | Commit Bot <commit-bot@chromium.org> | 2020-10-30 20:27:32 +0000 |
| commit | 7428f14d3db1d8c70c826f5adad25a4f6fbf7766 (patch) | |
| tree | bd798ba37c8da4844acca0c04e4514c33b169344 /driver/fingerprint | |
| parent | 8dcad3805d366c4044ede8aaec18c03544a19e4e (diff) | |
| download | chrome-ec-7428f14d3db1d8c70c826f5adad25a4f6fbf7766.tar.gz | |
include/config.h: Replace CONFIG_FP_SENSOR with CONFIG_FINGERPRINT_MCU
CONFIG_FP_SENSOR was only enabled for RW, but we need a way to know
whether the board is a fingerprint MCU when in RO as well.
"FINGERPRINT_MCU" is a bit more generic than FP_SENSOR. We still only
build the matching-related code for RW.
BRANCH=none
BUG=b:171370392
TEST=make buildall
Signed-off-by: Tom Hughes <tomhughes@chromium.org>
Change-Id: I808faa7a16522791cfb4eb9cc2e163d9eb994804
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2508860
Reviewed-by: Bhanu Prakash Maiya <bhanumaiya@google.com>
Diffstat (limited to 'driver/fingerprint')
| -rw-r--r-- | driver/fingerprint/fpc/build.mk | 4 |
1 files changed, 2 insertions, 2 deletions
diff --git a/driver/fingerprint/fpc/build.mk b/driver/fingerprint/fpc/build.mk index d5e3ede14e..fd4b45a6ff 100644 --- a/driver/fingerprint/fpc/build.mk +++ b/driver/fingerprint/fpc/build.mk @@ -15,9 +15,9 @@ else ifeq ($(CONFIG_FP_SENSOR_FPC1035),rw) include $(_fpc_cur_dir)bep/build.mk endif -ifeq ($(CONFIG_FP_SENSOR),rw) +ifneq ($(CONFIG_FINGERPRINT_MCU),) # Make sure output directory is created (in build directory) -dirs-y+="$(_fpc_cur_dir)" +dirs-rw+="$(_fpc_cur_dir)" # Only build these objects for the RW image all-obj-rw+=$(_fpc_cur_dir)fpc_sensor.o |