diff options
author | Jack Rosenthal <jrosenth@chromium.org> | 2021-11-04 12:11:58 -0600 |
---|---|---|
committer | Commit Bot <commit-bot@chromium.org> | 2021-11-05 04:22:34 +0000 |
commit | 252457d4b21f46889eebad61d4c0a65331919cec (patch) | |
tree | 01856c4d31d710b20e85a74c8d7b5836e35c3b98 /chip/stm32/flash-regs.h | |
parent | 08f5a1e6fc2c9467230444ac9b582dcf4d9f0068 (diff) | |
download | chrome-ec-stabilize-14526.73.B-ish.tar.gz |
ish: Trim down the release branchstabilize-wristpin-14469.59.B-ishstabilize-voshyr-14637.B-ishstabilize-quickfix-14695.187.B-ishstabilize-quickfix-14695.124.B-ishstabilize-quickfix-14526.91.B-ishstabilize-14695.85.B-ishstabilize-14695.107.B-ishstabilize-14682.B-ishstabilize-14633.B-ishstabilize-14616.B-ishstabilize-14589.B-ishstabilize-14588.98.B-ishstabilize-14588.14.B-ishstabilize-14588.123.B-ishstabilize-14536.B-ishstabilize-14532.B-ishstabilize-14528.B-ishstabilize-14526.89.B-ishstabilize-14526.84.B-ishstabilize-14526.73.B-ishstabilize-14526.67.B-ishstabilize-14526.57.B-ishstabilize-14498.B-ishstabilize-14496.B-ishstabilize-14477.B-ishstabilize-14469.9.B-ishstabilize-14469.8.B-ishstabilize-14469.58.B-ishstabilize-14469.41.B-ishstabilize-14442.B-ishstabilize-14438.B-ishstabilize-14411.B-ishstabilize-14396.B-ishstabilize-14395.B-ishstabilize-14388.62.B-ishstabilize-14388.61.B-ishstabilize-14388.52.B-ishstabilize-14385.B-ishstabilize-14345.B-ishstabilize-14336.B-ishstabilize-14333.B-ishrelease-R99-14469.B-ishrelease-R98-14388.B-ishrelease-R102-14695.B-ishrelease-R101-14588.B-ishrelease-R100-14526.B-ishfirmware-cherry-14454.B-ishfirmware-brya-14505.B-ishfirmware-brya-14505.71.B-ishfactory-kukui-14374.B-ishfactory-guybrush-14600.B-ishfactory-cherry-14455.B-ishfactory-brya-14517.B-ish
In the interest of making long-term branch maintenance incur as little
technical debt on us as possible, we should not maintain any files on
the branch we are not actually using.
This has the added effect of making it extremely clear when merging CLs
from the main branch when changes have the possibility to affect us.
The follow-on CL adds a convenience script to actually pull updates from
the main branch and generate a CL for the update.
BUG=b:204206272
BRANCH=ish
TEST=make BOARD=arcada_ish && make BOARD=drallion_ish
Signed-off-by: Jack Rosenthal <jrosenth@chromium.org>
Change-Id: I17e4694c38219b5a0823e0a3e55a28d1348f4b18
Reviewed-on: https://chromium-review.googlesource.com/c/chromiumos/platform/ec/+/3262038
Reviewed-by: Jett Rink <jettrink@chromium.org>
Reviewed-by: Tom Hughes <tomhughes@chromium.org>
Diffstat (limited to 'chip/stm32/flash-regs.h')
-rw-r--r-- | chip/stm32/flash-regs.h | 109 |
1 files changed, 0 insertions, 109 deletions
diff --git a/chip/stm32/flash-regs.h b/chip/stm32/flash-regs.h deleted file mode 100644 index b0a46667a1..0000000000 --- a/chip/stm32/flash-regs.h +++ /dev/null @@ -1,109 +0,0 @@ -/* Copyright 2021 The Chromium OS Authors. All rights reserved. - * Use of this source code is governed by a BSD-style license that can be - * found in the LICENSE file. - */ - -#ifndef __CROS_EC_STM32_FLASH_REGS_H -#define __CROS_EC_STM32_FLASH_REGS_H - -#include <stdbool.h> - -/** - * Unlock the flash control register using the unlock sequence. - * - * If the flash control register has been disabled since the last reset when - * this function is called, a bus fault will be generated. - * - * See "3.5.1 Unlocking the Flash control register" in RM0402. - * See "4.9.2 FLASH key register for bank 1" in RM0433. - */ -void unlock_flash_control_register(void); - -/** - * Unlock the flash option bytes register using the unlock sequence. - * - * If the flash option bytes register has been disabled since the last reset - * when this function is called, a bus fault will be generated. - * - * See "3.6.2 Programming user option bytes" in RM0402. - * See "4.9.3 FLASH option key register" in RM0433. - */ -void unlock_flash_option_bytes(void); - -/** - * Lock the flash control register. - * - * If the flash control register has been disabled since the last reset when - * this function is called, a bus fault will be generated. - * - * See "3.5.1 Unlocking the Flash control register" in RM0402. - * See "4.9.4 Flash control register for bank 1" in RM0433. - */ -void lock_flash_control_register(void); - -/** - * Lock the flash option bytes register. - * - * If the flash option bytes register has been disabled since the last reset - * when this function is called, a bus fault will be generated. - * - * See "3.6.2 Programming user option bytes" in RM0402. - * See "4.9.7 FLASH option control register" in RM0433. - */ -void lock_flash_option_bytes(void); - -/** - * Disable the flash option bytes register. - * - * This function expects that bus faults have not already been ignored when - * called. - * - * Once this function is called any attempt at accessing the flash option - * bytes register will generate a bus fault until the next reset. - * - * See "3.6.2 Programming user option bytes" in RM0402. - * See "4.9.7 FLASH option control register" in RM0433. - */ -void disable_flash_option_bytes(void); - -/** - * Disable the flash control register. - * - * This function expects that bus faults have not already been ignored when - * called. - * - * Once this function is called any attempt at accessing the flash control - * register will generate a bus fault until the next reset. - * - * See "3.5.1 Unlocking the Flash control register" in RM0402. - * See "4.9.4 Flash control register for bank 1" in RM0433. - */ -void disable_flash_control_register(void); - -/** - * Check if the flash option bytes are locked. - * - * If the flash option bytes register has been disabled since the last reset - * when this function is called, a bus fault will be generated. - - * See "3.6.2 Programming user option bytes" in RM0402. - * See "4.9.7 FLASH option control register" in RM0433. - * - * @return true if option bytes are locked, false otherwise - */ -bool flash_option_bytes_locked(void); - -/** - * Check if the flash control register is locked. - * - * If the flash control register has been disabled since the last reset - * when this function is called, a bus fault will be generated. - * - * See "3.5.1 Unlocking the Flash control register" in RM0402. - * See "4.9.4 Flash control register for bank 1" in RM0433. - * - * @return true if register is locked, false otherwise - */ -bool flash_control_register_locked(void); - -#endif /* __CROS_EC_STM32_FLASH_REGS_H */ |