diff options
author | Randall Spangler <rspangler@chromium.org> | 2013-05-21 11:03:29 -0700 |
---|---|---|
committer | ChromeBot <chrome-bot@google.com> | 2013-05-23 11:08:44 -0700 |
commit | a1006865e7f695ddd1c730cc9c6c6a6f109c43b9 (patch) | |
tree | 70f68e84e2340b7bf4210de177ee000ece27fda0 /board/bds/board.c | |
parent | bd8fec9bae8fc36cc1e46bf0417f2da00530b522 (diff) | |
download | chrome-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 'board/bds/board.c')
-rw-r--r-- | board/bds/board.c | 2 |
1 files changed, 1 insertions, 1 deletions
diff --git a/board/bds/board.c b/board/bds/board.c index 92372437a5..d0808f4f37 100644 --- a/board/bds/board.c +++ b/board/bds/board.c @@ -43,6 +43,6 @@ const struct gpio_info gpio_list[GPIO_COUNT] = { {"RECOVERYn", LM4_GPIO_D, (1<<1), GPIO_PULL_UP, NULL}, {"DEBUG_LED", LM4_GPIO_A, (1<<7), GPIO_OUT_LOW, NULL}, /* Unimplemented signals which we need to emulate for now */ - GPIO_SIGNAL_NOT_IMPLEMENTED("WRITE_PROTECT"), + GPIO_SIGNAL_NOT_IMPLEMENTED("WP"), GPIO_SIGNAL_NOT_IMPLEMENTED("ENTERING_RW"), }; |