mtd/ubi/kapi.c

110  * checksum of each logical eraseblock will be checked.
382  * @lnum: logical eraseblock number to read from
383  * @offset: offset within the logical eraseblock to read from
419  * @lnum: logical eraseblock number to read from
421  * @offset: offset within the logical eraseblock to read from
425  * This function reads data from offset @offset of logical eraseblock @lnum and
428  * eraseblock will be read and its CRC checksum will be checked (i.e., the CRC
429  * checksum is per-eraseblock). So checking may substantially slow down the
473  * @lnum: logical eraseblock number to read from
475  * @offset: offset within the logical eraseblock to read from
512  * @lnum: logical eraseblock number to write to
514  * @offset: offset within the logical eraseblock where to write
518  * logical eraseblock @lnum.
520  * This function takes care of physical eraseblock write failures. If write to
521  * the physical eraseblock write operation fails, the logical eraseblock is
522  * re-mapped to another physical eraseblock, the data is recovered, and the
565  * ubi_leb_change - change logical eraseblock atomically.
567  * @lnum: logical eraseblock number to change
571  * This function changes the contents of a logical eraseblock atomically. @buf
572  * has to contain new logical eraseblock data, and @len - the length of the
574  * eraseblock size, ant the logical eraseblock may be appended to more times
609  * ubi_leb_erase - erase logical eraseblock.
611  * @lnum: logical eraseblock number
613  * This function un-maps logical eraseblock @lnum and synchronously erases the
614  * correspondent physical eraseblock. Returns zero in case of success and a
646  * ubi_leb_unmap - un-map logical eraseblock.
648  * @lnum: logical eraseblock number
650  * This function un-maps logical eraseblock @lnum and schedules the
651  * corresponding physical eraseblock for erasure, so that it will eventually be
656  * eraseblock will contain all 0xFF bytes when UBI is initialized again. For
663  * In other words, when un-mapping a logical eraseblock, UBI does not store
665  * eraseblock as "un-mapped" in RAM. If UBI is detached before the physical
666  * eraseblock is physically erased, it will be mapped again to the same logical
667  * eraseblock when the MTD device is attached again.
670  * logical eraseblock has to be re-written. Then it is much more efficient to
672  * new data. Note, once new data has been written to the logical eraseblock,
674  * unclean reboot happens after the logical eraseblock has been un-mapped and
702  * ubi_leb_map - map logical eraseblock to a physical eraseblock.
704  * @lnum: logical eraseblock number
706  * This function maps an un-mapped logical eraseblock @lnum to a physical
707  * eraseblock. This means, that after a successful invocation of this
708  * function the logical eraseblock @lnum will be empty (contain only %0xFF
709  * bytes) and be mapped to a physical eraseblock, even if an unclean reboot
714  * eraseblock is already mapped, and other negative error codes in case of
741  * ubi_is_mapped - check if logical eraseblock is mapped.
743  * @lnum: logical eraseblock number
745  * This function checks if logical eraseblock @lnum is mapped to a physical
746  * eraseblock. If a logical eraseblock is un-mapped, this does not necessarily
748  * logical eraseblock may become mapped to the physical eraseblock it was last
798  * @lnum: logical eraseblock number to flush for
801  * eraseblock number pair. If either value is set to %UBI_ALL, then it acts as
803  * eraseblock numbers. It returns zero in case of success and a negative error