mtd/ubi/kapi.c

117  * checksum of each logical eraseblock will be checked.
368  * @lnum: logical eraseblock number to read from
369  * @offset: offset within the logical eraseblock to read from
405  * @lnum: logical eraseblock number to read from
407  * @offset: offset within the logical eraseblock to read from
411  * This function reads data from offset @offset of logical eraseblock @lnum and
413  * whether the data has to be checked or not. If yes, the whole logical
459  * @lnum: logical eraseblock number to read from
461  * @offset: offset within the logical eraseblock to read from
499  * @lnum: logical eraseblock number to write to
501  * @offset: offset within the logical eraseblock where to write
505  * logical eraseblock @lnum.
508  * the physical eraseblock write operation fails, the logical eraseblock is
552  * ubi_leb_change - change logical eraseblock atomically.
554  * @lnum: logical eraseblock number to change
558  * This function changes the contents of a logical eraseblock atomically. @buf
559  * has to contain new logical eraseblock data, and @len - the length of the
560  * data, which has to be aligned. The length may be shorter than the logical
561  * eraseblock size, ant the logical eraseblock may be appended to more times
596  * ubi_leb_erase - erase logical eraseblock.
598  * @lnum: logical eraseblock number
600  * This function un-maps logical eraseblock @lnum and synchronously erases the
633  * ubi_leb_unmap - un-map logical eraseblock.
635  * @lnum: logical eraseblock number
637  * This function un-maps logical eraseblock @lnum and schedules the
642  * Unlike erase, the un-map operation does not guarantee that the logical
644  * example, if several logical eraseblocks are un-mapped, and an unclean reboot
645  * happens after this, the logical eraseblocks will not necessarily be
650  * In other words, when un-mapping a logical eraseblock, UBI does not store
651  * any information about this on the flash media, it just marks the logical
653  * eraseblock is physically erased, it will be mapped again to the same logical
657  * logical eraseblock has to be re-written. Then it is much more efficient to
659  * new data. Note, once new data has been written to the logical eraseblock,
661  * unclean reboot happens after the logical eraseblock has been un-mapped and
689  * ubi_leb_map - map logical eraseblock to a physical eraseblock.
691  * @lnum: logical eraseblock number
693  * This function maps an un-mapped logical eraseblock @lnum to a physical
695  * function the logical eraseblock @lnum will be empty (contain only %0xFF
700  * damaged because of an interrupted update, %-EBADMSG if the logical
728  * ubi_is_mapped - check if logical eraseblock is mapped.
730  * @lnum: logical eraseblock number
732  * This function checks if logical eraseblock @lnum is mapped to a physical
733  * eraseblock. If a logical eraseblock is un-mapped, this does not necessarily
735  * logical eraseblock may become mapped to the physical eraseblock it was last
785  * @lnum: logical eraseblock number to flush for
787  * This function executes all pending works for a particular volume id / logical
789  * a wildcard for all of the corresponding volume numbers or logical