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
427  * whether the data has to be checked or not. If yes, the whole logical
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.
521  * the physical eraseblock write operation fails, the logical eraseblock is
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
573  * data, which has to be aligned. The length may be shorter than the logical
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
646  * ubi_leb_unmap - un-map logical eraseblock.
648  * @lnum: logical eraseblock number
650  * This function un-maps logical eraseblock @lnum and schedules the
655  * Unlike erase, the un-map operation does not guarantee that the logical
657  * example, if several logical eraseblocks are un-mapped, and an unclean reboot
658  * happens after this, the logical eraseblocks will not necessarily be
663  * In other words, when un-mapping a logical eraseblock, UBI does not store
664  * any information about this on the flash media, it just marks the logical
666  * eraseblock is physically erased, it will be mapped again to the same logical
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
708  * function the logical eraseblock @lnum will be empty (contain only %0xFF
713  * damaged because of an interrupted update, %-EBADMSG if the logical
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
800  * This function executes all pending works for a particular volume id / logical
802  * a wildcard for all of the corresponding volume numbers or logical