Lines Matching full:eraseblock

109  * checksum of each logical eraseblock will be checked.
361  * @lnum: logical eraseblock number to read from
362  * @offset: offset within the logical eraseblock to read from
398  * @lnum: logical eraseblock number to read from
400  * @offset: offset within the logical eraseblock to read from
404  * This function reads data from offset @offset of logical eraseblock @lnum and
407  * eraseblock will be read and its CRC checksum will be checked (i.e., the CRC
408  * checksum is per-eraseblock). So checking may substantially slow down the
452  * @lnum: logical eraseblock number to read from
454  * @offset: offset within the logical eraseblock to read from
491  * @lnum: logical eraseblock number to write to
493  * @offset: offset within the logical eraseblock where to write
497  * logical eraseblock @lnum.
499  * This function takes care of physical eraseblock write failures. If write to
500  * the physical eraseblock write operation fails, the logical eraseblock is
501  * re-mapped to another physical eraseblock, the data is recovered, and the
544  * ubi_leb_change - change logical eraseblock atomically.
546  * @lnum: logical eraseblock number to change
550  * This function changes the contents of a logical eraseblock atomically. @buf
551  * has to contain new logical eraseblock data, and @len - the length of the
553  * eraseblock size, ant the logical eraseblock may be appended to more times
588  * ubi_leb_erase - erase logical eraseblock.
590  * @lnum: logical eraseblock number
592  * This function un-maps logical eraseblock @lnum and synchronously erases the
593  * correspondent physical eraseblock. Returns zero in case of success and a
625  * ubi_leb_unmap - un-map logical eraseblock.
627  * @lnum: logical eraseblock number
629  * This function un-maps logical eraseblock @lnum and schedules the
630  * corresponding physical eraseblock for erasure, so that it will eventually be
635  * eraseblock will contain all 0xFF bytes when UBI is initialized again. For
642  * In other words, when un-mapping a logical eraseblock, UBI does not store
644  * eraseblock as "un-mapped" in RAM. If UBI is detached before the physical
645  * eraseblock is physically erased, it will be mapped again to the same logical
646  * eraseblock when the MTD device is attached again.
649  * logical eraseblock has to be re-written. Then it is much more efficient to
651  * new data. Note, once new data has been written to the logical eraseblock,
653  * unclean reboot happens after the logical eraseblock has been un-mapped and
681  * ubi_leb_map - map logical eraseblock to a physical eraseblock.
683  * @lnum: logical eraseblock number
685  * This function maps an un-mapped logical eraseblock @lnum to a physical
686  * eraseblock. This means, that after a successful invocation of this
687  * function the logical eraseblock @lnum will be empty (contain only %0xFF
688  * bytes) and be mapped to a physical eraseblock, even if an unclean reboot
693  * eraseblock is already mapped, and other negative error codes in case of
720  * ubi_is_mapped - check if logical eraseblock is mapped.
722  * @lnum: logical eraseblock number
724  * This function checks if logical eraseblock @lnum is mapped to a physical
725  * eraseblock. If a logical eraseblock is un-mapped, this does not necessarily
727  * logical eraseblock may become mapped to the physical eraseblock it was last
777  * @lnum: logical eraseblock number to flush for
780  * eraseblock number pair. If either value is set to %UBI_ALL, then it acts as
782  * eraseblock numbers. It returns zero in case of success and a negative error