mtd/ubi/kapi.c

110  * checksum of each logical eraseblock will be checked.
362  * @lnum: logical eraseblock number to read from
363  * @offset: offset within the logical eraseblock to read from
399  * @lnum: logical eraseblock number to read from
401  * @offset: offset within the logical eraseblock to read from
405  * This function reads data from offset @offset of logical eraseblock @lnum and
407  * whether the data has to be checked or not. If yes, the whole logical
453  * @lnum: logical eraseblock number to read from
455  * @offset: offset within the logical eraseblock to read from
492  * @lnum: logical eraseblock number to write to
494  * @offset: offset within the logical eraseblock where to write
498  * logical eraseblock @lnum.
501  * the physical eraseblock write operation fails, the logical eraseblock is
545  * ubi_leb_change - change logical eraseblock atomically.
547  * @lnum: logical eraseblock number to change
551  * This function changes the contents of a logical eraseblock atomically. @buf
552  * has to contain new logical eraseblock data, and @len - the length of the
553  * data, which has to be aligned. The length may be shorter than the logical
554  * eraseblock size, ant the logical eraseblock may be appended to more times
589  * ubi_leb_erase - erase logical eraseblock.
591  * @lnum: logical eraseblock number
593  * This function un-maps logical eraseblock @lnum and synchronously erases the
626  * ubi_leb_unmap - un-map logical eraseblock.
628  * @lnum: logical eraseblock number
630  * This function un-maps logical eraseblock @lnum and schedules the
635  * Unlike erase, the un-map operation does not guarantee that the logical
637  * example, if several logical eraseblocks are un-mapped, and an unclean reboot
638  * happens after this, the logical eraseblocks will not necessarily be
643  * In other words, when un-mapping a logical eraseblock, UBI does not store
644  * any information about this on the flash media, it just marks the logical
646  * eraseblock is physically erased, it will be mapped again to the same logical
650  * logical eraseblock has to be re-written. Then it is much more efficient to
652  * new data. Note, once new data has been written to the logical eraseblock,
654  * unclean reboot happens after the logical eraseblock has been un-mapped and
682  * ubi_leb_map - map logical eraseblock to a physical eraseblock.
684  * @lnum: logical eraseblock number
686  * This function maps an un-mapped logical eraseblock @lnum to a physical
688  * function the logical eraseblock @lnum will be empty (contain only %0xFF
693  * damaged because of an interrupted update, %-EBADMSG if the logical
721  * ubi_is_mapped - check if logical eraseblock is mapped.
723  * @lnum: logical eraseblock number
725  * This function checks if logical eraseblock @lnum is mapped to a physical
726  * eraseblock. If a logical eraseblock is un-mapped, this does not necessarily
728  * logical eraseblock may become mapped to the physical eraseblock it was last
778  * @lnum: logical eraseblock number to flush for
780  * This function executes all pending works for a particular volume id / logical
782  * a wildcard for all of the corresponding volume numbers or logical