Home
last modified time | relevance | path

Searched full:eraseblocks (Results 1 – 25 of 33) sorted by relevance

12

/linux/drivers/mtd/ubi/
H A DKconfig20 erase counter value and the lowest erase counter value of eraseblocks
23 counter to eraseblocks with high erase counter.
32 int "Maximum expected bad eraseblock count per 1024 eraseblocks"
36 This option specifies the maximum bad physical eraseblocks UBI
37 expects on the MTD device (per 1024 eraseblocks). If the underlying
38 flash does not admit of bad eraseblocks (e.g. NOR flash), this value
43 expected bad eraseblocks per 1024 eraseblocks then can be calculated
45 (MaxNVB is basically the total count of eraseblocks on the chip).
48 about 1.9% of physical eraseblocks for bad blocks handling. And that
49 will be 1.9% of eraseblocks on the entire NAND chip, not just the MTD
[all …]
H A Dubi-media.h57 * initialization UBI finds out that there are available physical eraseblocks
59 * (the physical eraseblocks reserved for bad eraseblocks handling and other
60 * reserved physical eraseblocks are not taken). So, if there is a volume with
62 * eraseblocks will be zero after UBI is loaded, because all of them will be
68 * eraseblocks, depending of particular chip instance. Manufacturers of NAND
69 * chips usually guarantee that the amount of initial bad eraseblocks does not
72 * of good physical eraseblocks the NAND chip on the device will have, but this
78 * Note, first UBI reserves some amount of physical eraseblocks for bad
80 * means that the pool of reserved physical eraseblocks will always be present.
94 * physical eraseblocks, don't allow the wear-leveling
[all …]
H A Dvtbl.c12 * physical eraseblocks, type, etc. The volume table is stored in the so-called
16 * consists of two logical eraseblocks - LEB 0 and LEB 1. Each logical
34 * eraseblocks became bad for some reasons. Suppose we are attaching the
35 * corresponding MTD device, for some reason we find no logical eraseblocks
38 * eraseblocks went bad. So we cannot alarm the user properly.
597 * No eraseblocks belonging to this volume found. We in init_volumes()
610 * eraseblocks. Treat it as corrupted. in init_volumes()
760 * these eraseblocks. in check_attaching_info()
810 * No logical eraseblocks belonging to the layout volume were in ubi_read_volume_table()
H A Dattach.c19 * Logical eraseblocks are represented by &struct ubi_ainf_peb objects. These
25 * Corrupted physical eraseblocks are put to the @corr list, free physical
26 * eraseblocks are put to the @free list and the physical eraseblock to be
451 * eraseblocks. That was before UBI got into mainline. We do not in ubi_compare_lebs()
587 * Walk the RB-tree of logical eraseblocks of volume @vol_id to look in ubi_add_to_av()
613 * Make sure that the logical eraseblocks have different in ubi_add_to_av()
620 * eraseblocks, in which case we'll refuse the image in in ubi_add_to_av()
623 * logical eraseblocks because there was an unclean reboot. in ubi_add_to_av()
811 * not initialized yet. This function picks a physical eraseblocks from one of
834 * so forth. We don't want to take care about bad eraseblocks here - in ubi_early_get_peb()
[all …]
H A Deba.c21 * eraseblocks. The lock tree elements are &struct ubi_ltree_entry objects.
615 * it is an error to read unmapped logical eraseblocks. in ubi_eba_read_leb()
1101 * @used_ebs: how many logical eraseblocks will this volume contain
1112 * It is prohibited to write more than once to logical eraseblocks of static
1251 * This flash device does not admit of bad eraseblocks or in ubi_eba_atomic_leb_change()
1334 * volume deletion un-maps all the volume's logical eraseblocks, it will in ubi_eba_copy_leb()
1679 ubi_err(ubi, "no enough physical eraseblocks (%d, need %d)", in ubi_eba_init()
1694 /* No enough free physical eraseblocks */ in ubi_eba_init()
H A Dkapi.c523 * write finishes. UBI has a pool of reserved physical eraseblocks for this.
657 * example, if several logical eraseblocks are un-mapped, and an unclean reboot
658 * happens after this, the logical eraseblocks will not necessarily be
660 * mapped to the same physical eraseblocks again. So, this function has to be
H A Dvmt.c227 /* Calculate how many eraseblocks are requested */ in ubi_create_volume()
232 /* Reserve physical eraseblocks */ in ubi_create_volume()
439 * @reserved_pebs: new size in physical eraseblocks
484 /* Reserve physical eraseblocks */ in ubi_resize_volume()
H A Dupd.c197 * @used_ebs: how many logical eraseblocks will this volume contain (static
/linux/drivers/mtd/tests/
H A Dspeedtest.c30 MODULE_PARM_DESC(count, "Maximum number of eraseblocks to use "
213 "page size %u, count of eraseblocks %u, pages per " in mtd_speedtest_init()
243 /* Write all eraseblocks, 1 eraseblock at a time */ in mtd_speedtest_init()
261 /* Read all eraseblocks, 1 eraseblock at a time */ in mtd_speedtest_init()
283 /* Write all eraseblocks, 1 page at a time */ in mtd_speedtest_init()
301 /* Read all eraseblocks, 1 page at a time */ in mtd_speedtest_init()
323 /* Write all eraseblocks, 2 pages at a time */ in mtd_speedtest_init()
341 /* Read all eraseblocks, 2 pages at a time */ in mtd_speedtest_init()
359 /* Erase all eraseblocks */ in mtd_speedtest_init()
369 /* Multi-block erase all eraseblocks */ in mtd_speedtest_init()
H A Dstresstest.c48 /* Read or write up 2 eraseblocks at a time - hence 'ebcnt - 1' */ in rand_eb()
164 "page size %u, count of eraseblocks %u, pages per " in mtd_stresstest_init()
170 pr_err("error: need at least 2 eraseblocks\n"); in mtd_stresstest_init()
175 /* Read or write up 2 eraseblocks at a time */ in mtd_stresstest_init()
H A Dmtd_test.c50 pr_info("scanning for bad eraseblocks\n"); in mtdtest_scan_for_bad_eraseblocks()
57 pr_info("scanned %d eraseblocks, %d are bad\n", i, bad); in mtdtest_scan_for_bad_eraseblocks()
H A Dreadtest.c148 "page size %u, count of eraseblocks %u, pages per " in mtd_readtest_init()
168 /* Read all eraseblocks 1 page at a time */ in mtd_readtest_init()
H A Dtorturetest.c34 MODULE_PARM_DESC(ebcnt, "number of consecutive eraseblocks to torture");
186 pr_info("torture %d eraseblocks (%d-%d) of mtd%d\n", in tort_init()
258 /* Check if the eraseblocks contain only 0xFF bytes */ in tort_init()
/linux/include/linux/mtd/
H A Dubi.h45 * @size: how many physical eraseblocks are reserved for this volume
47 * @used_ebs: how many physical eraseblocks of this volume actually contain any
53 * @usable_leb_size: how many bytes are available in logical eraseblocks of
89 * eraseblocks if a volume may be less. The following equation is true:
149 * @leb_start: starting offset of logical eraseblocks within physical
150 * eraseblocks
H A Dnand.h23 * @eraseblocks_per_lun: number of eraseblocks per LUN (Logical Unit Number)
24 * @max_bad_eraseblocks_per_lun: maximum number of eraseblocks per LUN
541 * nanddev_eraseblocks_per_lun() - Get the number of eraseblocks per LUN
544 * Return: the number of eraseblocks per LUN.
553 * nanddev_eraseblocks_per_target() - Get the number of eraseblocks per target
556 * Return: the number of eraseblocks per target.
590 * nanddev_neraseblocks() - Get the total number of eraseblocks
593 * Return: the total number of eraseblocks exposed by @nand.
881 * want to iterate over all eraseblocks of a NAND device.
/linux/Documentation/ABI/stable/
H A Dsysfs-class-ubi40 eraseblocks.
47 Count of bad physical eraseblocks on the underlying MTD device.
108 Number of physical eraseblocks reserved for bad block handling.
124 Total number of good (not marked as bad) physical eraseblocks on
192 Equivalent to the volume size in logical eraseblocks.
/linux/fs/ubifs/
H A Dubifs-media.h243 /* Minimum number of logical eraseblocks in the log */
245 /* Minimum number of bud logical eraseblocks (one for each head) */
247 /* Minimum number of journal logical eraseblocks */
249 /* Minimum number of LPT area logical eraseblocks */
251 /* Minimum number of orphan area logical eraseblocks */
254 * Minimum number of main area logical eraseblocks (buds, 3 for the index, 1
259 /* Minimum number of logical eraseblocks */
629 * @log_lebs: log size in logical eraseblocks
714 * @empty_lebs: number of empty logical eraseblocks
715 * @idx_lebs: number of indexing logical eraseblocks
H A Dubifs.h506 * struct ubifs_lp_stats - statistics of eraseblocks in the main area.
1089 * @log_lebs: number of logical eraseblocks in the log
1115 * @leb_start: starting offset of logical eraseblocks within physical
1116 * eraseblocks
1120 * @leb_cnt: count of logical eraseblocks
1121 * @max_leb_cnt: maximum count of logical eraseblocks
H A Dlpt.c13 * contains the LEB properties tree, a table of LPT area eraseblocks (ltab), and
26 * eraseblocks reusable. In the case of the big model, dirty eraseblocks are
30 * LPT does not to be scanned looking for empty eraseblocks when UBIFS is first
/linux/Documentation/filesystems/
H A Dubifs.rst21 1 MTD devices represent flash devices and they consist of eraseblocks of
30 4 Eraseblocks become worn out after some number of erase cycles -
33 5 Eraseblocks may become bad (only on NAND flashes) and software should
45 is very similar to MTD devices - they still consist of large eraseblocks,
/linux/Documentation/devicetree/bindings/mtd/partitions/
H A Dredboot-fis.yaml28 device. On a flash memory with 32KB eraseblocks, 0 means the first
H A Dfixed-partitions.yaml61 but may differ if device has bad eraseblocks on a flash.
/linux/drivers/mtd/nand/
H A Dcore.c188 * Return: a positive number encoding the maximum number of eraseblocks on a
/linux/fs/jffs2/
H A Dbuild.c343 /* What number of 'very dirty' eraseblocks do we allow before we in jffs2_calc_trigger_levels()
/linux/drivers/mtd/
H A Dmtdswap.c32 * The number of free eraseblocks when GC should stop
37 * Number of free eraseblocks below which GC can also collect low frag

12