summaryrefslogtreecommitdiff
path: root/test/flash.c
diff options
context:
space:
mode:
authorRandall Spangler <rspangler@chromium.org>2013-05-21 11:03:29 -0700
committerChromeBot <chrome-bot@google.com>2013-05-23 11:08:44 -0700
commita1006865e7f695ddd1c730cc9c6c6a6f109c43b9 (patch)
tree70f68e84e2340b7bf4210de177ee000ece27fda0 /test/flash.c
parentbd8fec9bae8fc36cc1e46bf0417f2da00530b522 (diff)
downloadchrome-ec-a1006865e7f695ddd1c730cc9c6c6a6f109c43b9.tar.gz
Move write protect GPIO handling to flash module
Write protect signal naming is now consistent across boards. New CONFIG_WP_ACTIVE_HIGH is present on systems where the write protect signal is active-high (e.g. Link). This will be used in the next CL, which moves flash_get_protect() to flash_common.c BUG=chrome-os-partner:15613 BRANCH=none TEST=flashinfo properly reports WP signal status Change-Id: I502ab033c3eb36661cc3ee97320874b3fbf6fc0d Signed-off-by: Randall Spangler <rspangler@chromium.org> Reviewed-on: https://gerrit.chromium.org/gerrit/56087 Reviewed-by: Vic Yang <victoryang@chromium.org>
Diffstat (limited to 'test/flash.c')
-rw-r--r--test/flash.c6
1 files changed, 2 insertions, 4 deletions
diff --git a/test/flash.c b/test/flash.c
index 02144e756c..5db8a6196c 100644
--- a/test/flash.c
+++ b/test/flash.c
@@ -66,11 +66,9 @@ int gpio_get_level(enum gpio_signal signal)
if (mock_wp == -1)
mock_wp = !!(system_get_scratchpad() & TEST_STATE_BOOT_WP_ON);
- if (strcasecmp(name, "WRITE_PROTECTn") == 0 ||
- strcasecmp(name, "WP_L") == 0)
+ if (strcasecmp(name, "WP_L") == 0)
return !mock_wp;
- if (strcasecmp(name, "WRITE_PROTECT") == 0 ||
- strcasecmp(name, "WP") == 0)
+ if (strcasecmp(name, "WP") == 0)
return mock_wp;
/* Signal other than write protect. Just return 0. */