Searched refs:erased (Results 1 – 25 of 29) sorted by relevance
12
81 STACKLEAK_ERASING OK: the rest of the thread stack is properly erased
53 OTP block cannot be erased.
60 is being erased, but erasing one partition will make
167 erased. Each Protection Register can be accessed multiple times to174 Lock Register bits cannot be erased. Therefore, when a Protection
50 key-erased {51 label = "key-erased";
66 key-erased {67 label = "key-erased";
101 memblock_free() call. The entry will be erased by reset_memblock_regions(),
64 If the device has to be fully erased before firmware flashing, user application
645 bool flash_op_err = false, erased; in qcom_spi_check_error() local664 erased = (erased_cw & ERASED_CW) == ERASED_CW; in qcom_spi_check_error()666 erased = false; in qcom_spi_check_error()668 if (!erased) in qcom_spi_check_error()
432 area. Those blocks must not be erased under any circumstances as the bad480 erased when the block is erased to be reused. So in case of powerloss587 block table is updated and the block is erased and everything is589 written and everything else in the block is ignored and erased.
183 If the flash comes erased by default and the previous erase was ignored,
125 erased.
65 erased FLASH results in ECC errors.
165 and last as the range that was erased and return the entry that existed
20 are erased on reboot.
39 key-erased {
38 key-erased {
51 key-erased {
57 key-erased {
60 key-erased {
56 key-erased {
28 3 The whole eraseblock has to be erased before it becomes possible to
29 don't actually get erased until the write-buffer has been flushed to
210 can then be mounted directly on a freshly erased partition and files can be
943 * required quirks, the bootloader will be erased right after card probe.