summaryrefslogtreecommitdiff
path: root/include/flash.h
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 /include/flash.h
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 'include/flash.h')
-rw-r--r--include/flash.h5
1 files changed, 5 insertions, 0 deletions
diff --git a/include/flash.h b/include/flash.h
index 8969a56c8b..8f842cc6d1 100644
--- a/include/flash.h
+++ b/include/flash.h
@@ -88,6 +88,11 @@ int flash_physical_erase(int offset, int size);
int flash_physical_get_protect(int bank);
/**
+ * Return non-zero if entire flash is locked for the current boot.
+ */
+int flash_physical_get_all_protect_now(void);
+
+/**
* Set physical write protect status for the next boot.
*
* @param start_bank Start bank