mtd/ubi/kapi.c

116  * checksum of each logical eraseblock will be checked.
367  * @lnum: logical eraseblock number to read from
368  * @offset: offset within the logical eraseblock to read from
404  * @lnum: logical eraseblock number to read from
406  * @offset: offset within the logical eraseblock to read from
410  * This function reads data from offset @offset of logical eraseblock @lnum and
412  * whether the data has to be checked or not. If yes, the whole logical
458  * @lnum: logical eraseblock number to read from
460  * @offset: offset within the logical eraseblock to read from
498  * @lnum: logical eraseblock number to write to
500  * @offset: offset within the logical eraseblock where to write
504  * logical eraseblock @lnum.
507  * the physical eraseblock write operation fails, the logical eraseblock is
551  * ubi_leb_change - change logical eraseblock atomically.
553  * @lnum: logical eraseblock number to change
557  * This function changes the contents of a logical eraseblock atomically. @buf
558  * has to contain new logical eraseblock data, and @len - the length of the
559  * data, which has to be aligned. The length may be shorter than the logical
560  * eraseblock size, ant the logical eraseblock may be appended to more times
595  * ubi_leb_erase - erase logical eraseblock.
597  * @lnum: logical eraseblock number
599  * This function un-maps logical eraseblock @lnum and synchronously erases the
632  * ubi_leb_unmap - un-map logical eraseblock.
634  * @lnum: logical eraseblock number
636  * This function un-maps logical eraseblock @lnum and schedules the
641  * Unlike erase, the un-map operation does not guarantee that the logical
643  * example, if several logical eraseblocks are un-mapped, and an unclean reboot
644  * happens after this, the logical eraseblocks will not necessarily be
649  * In other words, when un-mapping a logical eraseblock, UBI does not store
650  * any information about this on the flash media, it just marks the logical
652  * eraseblock is physically erased, it will be mapped again to the same logical
656  * logical eraseblock has to be re-written. Then it is much more efficient to
658  * new data. Note, once new data has been written to the logical eraseblock,
660  * unclean reboot happens after the logical eraseblock has been un-mapped and
688  * ubi_leb_map - map logical eraseblock to a physical eraseblock.
690  * @lnum: logical eraseblock number
692  * This function maps an un-mapped logical eraseblock @lnum to a physical
694  * function the logical eraseblock @lnum will be empty (contain only %0xFF
699  * damaged because of an interrupted update, %-EBADMSG if the logical
727  * ubi_is_mapped - check if logical eraseblock is mapped.
729  * @lnum: logical eraseblock number
731  * This function checks if logical eraseblock @lnum is mapped to a physical
732  * eraseblock. If a logical eraseblock is un-mapped, this does not necessarily
734  * logical eraseblock may become mapped to the physical eraseblock it was last
784  * @lnum: logical eraseblock number to flush for
786  * This function executes all pending works for a particular volume id / logical
788  * a wildcard for all of the corresponding volume numbers or logical