Lines Matching full:eraseblock

110  * checksum of each logical eraseblock will be checked.
362  * @lnum: logical eraseblock number to read from
363  * @offset: offset within the logical eraseblock to read from
399  * @lnum: logical eraseblock number to read from
401  * @offset: offset within the logical eraseblock to read from
405  * This function reads data from offset @offset of logical eraseblock @lnum and
408  * eraseblock will be read and its CRC checksum will be checked (i.e., the CRC
409  * checksum is per-eraseblock). So checking may substantially slow down the
453  * @lnum: logical eraseblock number to read from
455  * @offset: offset within the logical eraseblock to read from
492  * @lnum: logical eraseblock number to write to
494  * @offset: offset within the logical eraseblock where to write
498  * logical eraseblock @lnum.
500  * This function takes care of physical eraseblock write failures. If write to
501  * the physical eraseblock write operation fails, the logical eraseblock is
502  * re-mapped to another physical eraseblock, the data is recovered, and the
545  * ubi_leb_change - change logical eraseblock atomically.
547  * @lnum: logical eraseblock number to change
551  * This function changes the contents of a logical eraseblock atomically. @buf
552  * has to contain new logical eraseblock data, and @len - the length of the
554  * eraseblock size, ant the logical eraseblock may be appended to more times
589  * ubi_leb_erase - erase logical eraseblock.
591  * @lnum: logical eraseblock number
593  * This function un-maps logical eraseblock @lnum and synchronously erases the
594  * correspondent physical eraseblock. Returns zero in case of success and a
626  * ubi_leb_unmap - un-map logical eraseblock.
628  * @lnum: logical eraseblock number
630  * This function un-maps logical eraseblock @lnum and schedules the
631  * corresponding physical eraseblock for erasure, so that it will eventually be
636  * eraseblock will contain all 0xFF bytes when UBI is initialized again. For
643  * In other words, when un-mapping a logical eraseblock, UBI does not store
645  * eraseblock as "un-mapped" in RAM. If UBI is detached before the physical
646  * eraseblock is physically erased, it will be mapped again to the same logical
647  * eraseblock when the MTD device is attached again.
650  * logical eraseblock has to be re-written. Then it is much more efficient to
652  * new data. Note, once new data has been written to the logical eraseblock,
654  * unclean reboot happens after the logical eraseblock has been un-mapped and
682  * ubi_leb_map - map logical eraseblock to a physical eraseblock.
684  * @lnum: logical eraseblock number
686  * This function maps an un-mapped logical eraseblock @lnum to a physical
687  * eraseblock. This means, that after a successful invocation of this
688  * function the logical eraseblock @lnum will be empty (contain only %0xFF
689  * bytes) and be mapped to a physical eraseblock, even if an unclean reboot
694  * eraseblock is already mapped, and other negative error codes in case of
721  * ubi_is_mapped - check if logical eraseblock is mapped.
723  * @lnum: logical eraseblock number
725  * This function checks if logical eraseblock @lnum is mapped to a physical
726  * eraseblock. If a logical eraseblock is un-mapped, this does not necessarily
728  * logical eraseblock may become mapped to the physical eraseblock it was last
778  * @lnum: logical eraseblock number to flush for
781  * eraseblock number pair. If either value is set to %UBI_ALL, then it acts as
783  * eraseblock numbers. It returns zero in case of success and a negative error