Home
last modified time | relevance | path

Searched refs:eraseblock (Results 1 – 9 of 9) sorted by relevance

/Linux-v4.19/include/linux/mtd/
Dnand.h76 unsigned int eraseblock; member
435 pos->eraseblock = do_div(tmp, nand->memorg.eraseblocks_per_lun); in nanddev_offs_to_pos()
436 pos->plane = pos->eraseblock % nand->memorg.planes_per_lun; in nanddev_offs_to_pos()
461 if (a->eraseblock != b->eraseblock) in nanddev_pos_cmp()
462 return a->eraseblock < b->eraseblock ? -1 : 1; in nanddev_pos_cmp()
487 ((pos->eraseblock + in nanddev_pos_to_offs()
510 (pos->eraseblock << nand->rowconv.eraseblock_addr_shift) | in nanddev_pos_to_row()
527 pos->eraseblock = 0; in nanddev_pos_next_target()
549 pos->eraseblock = 0; in nanddev_pos_next_lun()
563 if (pos->eraseblock >= nand->memorg.eraseblocks_per_lun - 1) in nanddev_pos_next_eraseblock()
[all …]
Drawnand.h1714 int nand_erase_op(struct nand_chip *chip, unsigned int eraseblock);
/Linux-v4.19/Documentation/ABI/stable/
Dsysfs-class-ubi38 Amount of available logical eraseblock. For example, one may
70 Maximum logical eraseblock size this UBI device may provide. UBI
71 volumes may have smaller logical eraseblock size because of their
79 Maximum physical eraseblock erase counter value.
148 Volume alignment - the value the logical eraseblock size of
150 logical eraseblock size is multiple of 2048. In other words,
151 volume logical eraseblock size is UBI device logical eraseblock
191 Count of physical eraseblock reserved for this volume.
219 Logical eraseblock size of this volume. Equivalent to logical
220 eraseblock size of the device aligned on the volume alignment
/Linux-v4.19/drivers/mtd/tests/
Dnandbiterrs.c73 static unsigned eraseblock; /* Eraseblock number for our page. */ variable
372 eraseblock = mtd_div_by_eb(offset, mtd); in mtd_nandbiterrs_init()
375 page_offset, offset, eraseblock); in mtd_nandbiterrs_init()
389 err = mtdtest_erase_eraseblock(mtd, eraseblock); in mtd_nandbiterrs_init()
402 err = mtdtest_erase_eraseblock(mtd, eraseblock); in mtd_nandbiterrs_init()
/Linux-v4.19/drivers/mtd/ubi/
DKconfig21 wear leveling by means of moving data from eraseblock with low erase
25 other flashes which have eraseblock life-cycle 100000 or more.
26 However, in case of MLC NAND flashes which typically have eraseblock
31 int "Maximum expected bad eraseblock count per 1024 eraseblocks"
/Linux-v4.19/Documentation/filesystems/
Dubifs.txt19 eraseblock, write to some offset within an eraseblock, and erase a whole
20 eraseblock. Block devices support 2 main operations - read a whole
22 3 The whole eraseblock has to be erased before it becomes possible to
/Linux-v4.19/Documentation/ABI/testing/
Dsysfs-class-mtd51 zero, this is the eraseblock size for the entire device.
53 can be used to determine the actual eraseblock layout.
81 For devices that have variable eraseblock sizes, this
/Linux-v4.19/fs/jffs2/
DREADME.Locking74 This is used to serialise access to the eraseblock lists, to the
75 per-eraseblock lists of physical jffs2_raw_node_ref structures, and
/Linux-v4.19/drivers/mtd/nand/raw/
Dnand_base.c2110 int nand_erase_op(struct nand_chip *chip, unsigned int eraseblock) in nand_erase_op() argument
2113 unsigned int page = eraseblock << in nand_erase_op()
4667 unsigned int eraseblock; in single_erase() local
4670 eraseblock = page >> (chip->phys_erase_shift - chip->page_shift); in single_erase()
4672 return nand_erase_op(chip, eraseblock); in single_erase()