Searched refs:erasing (Results 1 – 16 of 16) sorted by relevance
17 Many flash memories support erasing small (4096 B) sectors. Depending19 to erasing whole blocks (32/64 KiB).21 small sectors. On the other hand erasing should be faster when using
78 shared[i].writing = shared[i].erasing = NULL; in lpddr_cmdset()268 if (mode == FL_ERASING && shared->erasing in get_chip()269 && shared->erasing->oldstate == FL_ERASING) { in get_chip()283 shared->erasing = chip; in get_chip()355 shared->writing = shared->erasing; in put_chip()368 shared->erasing = NULL; in put_chip()370 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
55 including the whole card. When erasing a large area it may60 is being erased, but erasing one partition will make74 size for erasing large areas.
96 struct flchip *erasing; member
164 erasing = 0, bad = 0, unchecked = 0; in __jffs2_dbg_superblock_counts() local251 erasing += c->sector_size; in __jffs2_dbg_superblock_counts()255 erasing += c->sector_size; in __jffs2_dbg_superblock_counts()259 erasing += c->sector_size; in __jffs2_dbg_superblock_counts()281 check(erasing); in __jffs2_dbg_superblock_counts()
61 * accidentally erasing critical flash sectors. We thus define
80 * accidentally erasing critical flash sectors. We thus define
101 * accidentally erasing critical flash sectors. We thus define
797 shared[i].writing = shared[i].erasing = NULL; in cfi_intelext_partition_fixup()1015 if (mode == FL_ERASING && shared->erasing in get_chip()1016 && shared->erasing->oldstate == FL_ERASING) { in get_chip()1030 shared->erasing = chip; in get_chip()1049 shared->writing = shared->erasing; in put_chip()1062 shared->erasing = NULL; in put_chip()1064 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
221 unsigned int erasing; member
109 versions of them are obsoleted without erasing them right away. As a result,202 written to without erasing it and previously written content that is obsolete203 but can't be overwritten without erasing the full LEB.228 erasing parts of the current tree and restoring old versions that are still on
239 and erasing nodes.256 When erasing a node, the user must call rb_erase_augmented() instead of
220 bool "Allow runtime disabling of kernel stack erasing"224 runtime to control kernel stack erasing for kernels built with
1456 This parameter can be used to control kernel stack erasing at the end1459 That erasing reduces the information which kernel stack leak bugs1465 0 Kernel stack erasing is disabled, STACKLEAK_METRICS are not updated.1466 1 Kernel stack erasing is enabled (default), it is performed before
484 block table before erasing any of the blocks.809 as you want to a page. The consecutive writes to a page, before erasing
15 read-write-erases) before erasing the commit record. Should the system