Searched refs:erase (Results 1 – 11 of 11) sorted by relevance
| /littlefs-3.5.0-3.4.0/bd/ |
| D | lfs_rambd.c | 19 (void*)(uintptr_t)cfg->erase, (void*)(uintptr_t)cfg->sync, in lfs_rambd_createcfg()
55 (void*)(uintptr_t)cfg->erase, (void*)(uintptr_t)cfg->sync, in lfs_rambd_create()
|
| D | lfs_filebd.c | 28 (void*)(uintptr_t)cfg->erase, (void*)(uintptr_t)cfg->sync, in lfs_filebd_createcfg()
59 (void*)(uintptr_t)cfg->erase, (void*)(uintptr_t)cfg->sync, in lfs_filebd_create()
|
| D | lfs_testbd.c | 26 (void*)(uintptr_t)cfg->erase, (void*)(uintptr_t)cfg->sync, in lfs_testbd_createcfg()
79 (void*)(uintptr_t)cfg->erase, (void*)(uintptr_t)cfg->sync, in lfs_testbd_create()
|
| /littlefs-3.5.0-3.4.0/tests/ |
| D | test_move.toml | 107 cfg.erase(&cfg, block) => 0;
183 cfg.erase(&cfg, block) => 0;
199 cfg.erase(&cfg, block) => 0;
275 cfg.erase(&cfg, block) => 0;
291 cfg.erase(&cfg, block) => 0;
545 cfg.erase(&cfg, block) => 0;
629 cfg.erase(&cfg, block) => 0;
645 cfg.erase(&cfg, block) => 0;
729 cfg.erase(&cfg, block) => 0;
745 cfg.erase(&cfg, block) => 0;
|
| D | test_orphans.toml | 28 cfg.erase(&cfg, block) => 0;
|
| D | test_evil.toml | 161 cfg.erase(&cfg, ctz.head) => 0;
|
| /littlefs-3.5.0-3.4.0/ |
| D | README.md | 46 .erase = user_provided_block_device_erase,
125 In the configuration struct, the `prog` and `erase` function provided by the
|
| D | lfs.h | 178 int (*erase)(const struct lfs_config *c, lfs_block_t block); member
|
| D | SPEC.md | 26 - In addition to the logical block size (which usually matches the erase
39 providing a backup during erase cycles in case power is lost. These two blocks
45 order to update the metadata without requiring an erase cycles. Note that
93 1. **Revision count (32-bits)** - Incremented every erase cycle. If both blocks
|
| D | lfs.c | 260 int err = lfs->cfg->erase(lfs->cfg, block); in lfs_bd_erase()
5325 (void*)(uintptr_t)cfg->erase, (void*)(uintptr_t)cfg->sync,
5355 (void*)(uintptr_t)cfg->erase, (void*)(uintptr_t)cfg->sync,
5812 (void*)(uintptr_t)cfg->erase, (void*)(uintptr_t)cfg->sync,
|
| D | DESIGN.md | 305 incrementally program new data onto erased blocks, but we need to erase a full
360 an erase), we still have the original entries if we lose power during the
417 During this compaction step we also erase the metadata block and increment
|
