ec_commands: Add chipset_{reset,shutdown}_reason

Move enums chipset_{reset,shutdown}_reason from chipset.h to
ec_commands.h for coreboot to use.

BUG=b:174443398
TEST=emerge-asurada chromeos-ec
TEST=make buildall -j
BRANCH=none

Change-Id: I8939ab86b4277170139e79f6806d9e70ce57964f
Signed-off-by: Yu-Ping Wu <yupingso@chromium.org>
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/2607150
Reviewed-by: Eric Yilun Lin <yllin@chromium.org>

1 files changed, 0 insertions, 64 deletions

diff --git a/include/chipset.h b/include/chipset.h
index e2c1421ec6..4ce52afb53 100644
--- a/include/chipset.h
+++ b/include/chipset.h
@@ -42,70 +42,6 @@ enum chipset_state_mask {
 				     CHIPSET_STATE_STANDBY),
 };
 
-/*
- * Reason codes used by the AP after a shutdown to figure out why it was reset
- * by the EC.  These are sent in EC commands.  Therefore, to maintain protocol
- * compatibility:
- * - New entries must be inserted prior to the _COUNT field
- * - If an existing entry is no longer in service, it must be replaced with a
- *   RESERVED entry instead.
- * - The semantic meaning of an entry should not change.
- * - Do not exceed 2^15 - 1 for reset reasons or 2^16 - 1 for shutdown reasons.
- */
-enum chipset_reset_reason {
-	CHIPSET_RESET_BEGIN = 0,
-	CHIPSET_RESET_UNKNOWN = CHIPSET_RESET_BEGIN,
-	/* Custom reason defined by a board.c or baseboard.c file */
-	CHIPSET_RESET_BOARD_CUSTOM,
-	/* Believe that the AP has hung */
-	CHIPSET_RESET_HANG_REBOOT,
-	/* Reset by EC console command */
-	CHIPSET_RESET_CONSOLE_CMD,
-	/* Reset by EC host command */
-	CHIPSET_RESET_HOST_CMD,
-	/* Keyboard module reset key combination */
-	CHIPSET_RESET_KB_SYSRESET,
-	/* Keyboard module warm reboot */
-	CHIPSET_RESET_KB_WARM_REBOOT,
-	/* Debug module warm reboot */
-	CHIPSET_RESET_DBG_WARM_REBOOT,
-	/* I cannot self-terminate.  You must lower me into the steel. */
-	CHIPSET_RESET_AP_REQ,
-	/* Reset as side-effect of startup sequence */
-	CHIPSET_RESET_INIT,
-	/* EC detected an AP watchdog event. */
-	CHIPSET_RESET_AP_WATCHDOG,
-	CHIPSET_RESET_COUNT,
-};
-
-/*
- * Hard shutdowns are logged on the same path as resets.
- */
-enum chipset_shutdown_reason {
-	CHIPSET_SHUTDOWN_BEGIN = BIT(15),
-	CHIPSET_SHUTDOWN_POWERFAIL = CHIPSET_SHUTDOWN_BEGIN,
-	/* Forcing a shutdown as part of EC initialization */
-	CHIPSET_SHUTDOWN_INIT,
-	/* Custom reason on a per-board basis. */
-	CHIPSET_SHUTDOWN_BOARD_CUSTOM,
-	/* This is a reason to inhibit startup, not cause shut down. */
-	CHIPSET_SHUTDOWN_BATTERY_INHIBIT,
-	/* A power_wait_signal is being asserted */
-	CHIPSET_SHUTDOWN_WAIT,
-	/* Critical battery level. */
-	CHIPSET_SHUTDOWN_BATTERY_CRIT,
-	/* Because you told me to. */
-	CHIPSET_SHUTDOWN_CONSOLE_CMD,
-	/* Forcing a shutdown to effect entry to G3. */
-	CHIPSET_SHUTDOWN_G3,
-	/* Force shutdown due to over-temperature. */
-	CHIPSET_SHUTDOWN_THERMAL,
-	/* Force a chipset shutdown from the power button through EC */
-	CHIPSET_SHUTDOWN_BUTTON,
-
-	CHIPSET_SHUTDOWN_COUNT,
-};
-
 enum critical_shutdown {
 	CRITICAL_SHUTDOWN_IGNORE,
 	CRITICAL_SHUTDOWN_HIBERNATE,