Searched refs:erased (Results 1 – 19 of 19) sorted by relevance
| /Linux-v5.4/drivers/mtd/nand/raw/ |
| D | sunxi_nand.c | 761 int step, u32 status, bool *erased) in sunxi_nfc_hw_ecc_correct() argument
767 *erased = false; in sunxi_nfc_hw_ecc_correct()
779 *erased = true; in sunxi_nfc_hw_ecc_correct()
806 bool erased; in sunxi_nfc_hw_ecc_read_chunk() local
834 &erased); in sunxi_nfc_hw_ecc_read_chunk()
835 if (erased) in sunxi_nfc_hw_ecc_read_chunk()
956 bool erased; in sunxi_nfc_hw_ecc_read_chunks_dma() local
960 i, status, &erased); in sunxi_nfc_hw_ecc_read_chunks_dma()
966 if (oob_required && !erased) { in sunxi_nfc_hw_ecc_read_chunks_dma()
976 if (erased) in sunxi_nfc_hw_ecc_read_chunks_dma()
|
| D | qcom_nandc.c | 1733 bool flash_op_err = false, erased; in parse_read_errors() local
1770 erased = (erased_cw & ERASED_CW) == ERASED_CW ? in parse_read_errors()
1779 erased = erased_chunk_check_and_fixup(data_buf, in parse_read_errors()
1782 erased = false; in parse_read_errors()
1785 if (!erased) in parse_read_errors()
|
| /Linux-v5.4/Documentation/ABI/testing/ |
| D | pstore | 33 will be saved elsewhere and erased from persistent store
|
| /Linux-v5.4/drivers/mtd/nand/onenand/ |
| D | Kconfig | 52 OTP block cannot be erased.
|
| /Linux-v5.4/Documentation/driver-api/mmc/ |
| D | mmc-dev-attrs.rst | 60 is being erased, but erasing one partition will make
|
| /Linux-v5.4/drivers/mtd/chips/ |
| D | Kconfig | 165 erased. Each Protection Register can be accessed multiple times to
172 Lock Register bits cannot be erased. Therefore, when a Protection
|
| /Linux-v5.4/Documentation/core-api/ |
| D | librs.rst | 65 erased FLASH results in ECC errors.
|
| D | xarray.rst | 77 been stored to, one that has been erased and one that has most recently
|
| /Linux-v5.4/Documentation/driver-api/ |
| D | mtdnand.rst | 430 area. Those blocks must not be erased under any circumstances as the bad
478 erased when the block is erased to be reused. So in case of powerloss
585 block table is updated and the block is erased and everything is
587 written and everything else in the block is ignored and erased.
|
| /Linux-v5.4/Documentation/media/uapi/v4l/ |
| D | vidioc-g-edid.rst | 132 erased.
|
| /Linux-v5.4/Documentation/filesystems/ |
| D | ubifs.txt | 22 3 The whole eraseblock has to be erased before it becomes possible to
|
| D | ubifs-authentication.rst | 225 the flash and have not yet been erased. This is possible, because every commit
|
| /Linux-v5.4/Documentation/admin-guide/blockdev/ |
| D | ramdisk.rst | 20 are erased on reboot.
|
| /Linux-v5.4/fs/jffs2/ |
| D | README.Locking | 29 don't actually get erased until the write-buffer has been flushed to
|
| /Linux-v5.4/Documentation/arm/sa1100/ |
| D | assabet.rst | 210 can then be mounted directly on a freshly erased partition and files can be
|
| /Linux-v5.4/fs/reiserfs/ |
| D | README | 116 in a destructive way that erased the value of his contributions, and
|
| /Linux-v5.4/Documentation/admin-guide/ |
| D | bcache.rst | 208 16 bytes were erased at offset 0x1018 (bcache)
255 …/dev/nvme0n1p4: 16 bytes were erased at offset 0x00001018 (bcache): c6 85 73 f6 4e 1a 45 ca 82 65 …
|
| /Linux-v5.4/Documentation/media/kapi/ |
| D | cec-core.rst | 172 are to be erased. Otherwise the given logical address should be programmed.
|
| /Linux-v5.4/Documentation/power/ |
| D | swsusp.rst | 344 from a failed or aborted resume is erased from the swap device.
|
