| /linux/drivers/mtd/spi-nor/ |
| H A D | Kconfig | 17 Many flash memories support erasing small (4096 B) sectors. Depending 19 to erasing whole blocks (32/64 KiB). 21 small sectors. On the other hand erasing should be faster when using
|
| /linux/drivers/mtd/lpddr/ |
| H A D | lpddr_cmds.c | 77 shared[i].writing = shared[i].erasing = NULL; in lpddr_cmdset() 267 if (mode == FL_ERASING && shared->erasing in get_chip() 268 && shared->erasing->oldstate == FL_ERASING) { in get_chip() 282 shared->erasing = chip; in get_chip() 354 shared->writing = shared->erasing; in put_chip() 367 shared->erasing = NULL; in put_chip() 369 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
|
| /linux/Documentation/driver-api/mmc/ |
| H A D | mmc-dev-attrs.rst | 55 including the whole card. When erasing a large area it may 60 is being erased, but erasing one partition will make 74 size for erasing large areas.
|
| /linux/include/linux/mtd/ |
| H A D | flashchip.h | 96 struct flchip *erasing; member
|
| /linux/fs/jffs2/ |
| H A D | debug.c | 164 erasing = 0, bad = 0, unchecked = 0; in __jffs2_dbg_superblock_counts() local 251 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()
|
| /linux/drivers/tty/ |
| H A D | n_tty.c | 102 unsigned char lnext:1, erasing:1, raw:1, real_raw:1, icanon:1; member 318 ldata->erasing = 0; in reset_buffer_flags() 907 if (ldata->erasing) { in finish_erasing() 909 ldata->erasing = 0; in finish_erasing() 984 if (!ldata->erasing) { in eraser() 986 ldata->erasing = 1; in eraser() 1790 ldata->erasing = 0; in n_tty_set_termios()
|
| /linux/drivers/media/pci/solo6x10/ |
| H A D | solo6x10-v4l2.c | 38 solo_dev->erasing = 1; in erase_on() 44 if (!solo_dev->erasing) in erase_off() 52 solo_dev->erasing = 0; in erase_off()
|
| H A D | solo6x10.h | 221 unsigned int erasing; member
|
| /linux/arch/arm/boot/dts/marvell/ |
| H A D | orion5x-maxtor-shared-storage-2.dts | 61 * accidentally erasing critical flash sectors. We thus define
|
| H A D | orion5x-lacie-ethernet-disk-mini-v2.dts | 80 * accidentally erasing critical flash sectors. We thus define
|
| H A D | orion5x-lacie-d2-network.dts | 101 * accidentally erasing critical flash sectors. We thus define
|
| /linux/drivers/mtd/chips/ |
| H A D | cfi_cmdset_0001.c | 793 shared[i].writing = shared[i].erasing = NULL; in cfi_intelext_partition_fixup() 1011 if (mode == FL_ERASING && shared->erasing in get_chip() 1012 && shared->erasing->oldstate == FL_ERASING) { in get_chip() 1026 shared->erasing = chip; in get_chip() 1045 shared->writing = shared->erasing; in put_chip() 1058 shared->erasing = NULL; in put_chip() 1060 } else if (shared->erasing == chip && shared->writing != chip) { in put_chip()
|
| /linux/Documentation/filesystems/ |
| H A D | ubifs-authentication.rst | 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 obsolete 203 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
|
| /linux/security/ |
| H A D | Kconfig.hardening | 152 bool "Allow runtime disabling of kernel stack erasing" 156 runtime to control kernel stack erasing for kernels built with
|
| /linux/Documentation/core-api/ |
| H A D | rbtree.rst | 239 and erasing nodes. 256 When erasing a node, the user must call rb_erase_augmented() instead of
|
| /linux/Documentation/admin-guide/sysctl/ |
| H A D | kernel.rst | 1500 This parameter can be used to control kernel stack erasing at the end 1503 That erasing reduces the information which kernel stack leak bugs 1509 0 Kernel stack erasing is disabled, KSTACK_ERASE_METRICS are not updated. 1510 1 Kernel stack erasing is enabled (default), it is performed before
|
| /linux/Documentation/driver-api/ |
| H A D | mtdnand.rst | 484 block table before erasing any of the blocks. 809 as you want to a page. The consecutive writes to a page, before erasing
|
| /linux/Documentation/filesystems/ext4/ |
| H A D | journal.rst | 15 read-write-erases) before erasing the commit record. Should the system
|
| /linux/Documentation/filesystems/xfs/ |
| H A D | xfs-online-fsck-design.rst | 89 format, which means that fsck can only respond to errors by erasing files until 134 inconsistencies in file metadata and directory tree by erasing things as needed
|