Lines Matching full:logical

109  * checksum of each logical eraseblock will be checked.
361  * @lnum: logical eraseblock number to read from
362  * @offset: offset within the logical eraseblock to read from
398  * @lnum: logical eraseblock number to read from
400  * @offset: offset within the logical eraseblock to read from
404  * This function reads data from offset @offset of logical eraseblock @lnum and
406  * whether the data has to be checked or not. If yes, the whole logical
452  * @lnum: logical eraseblock number to read from
454  * @offset: offset within the logical eraseblock to read from
491  * @lnum: logical eraseblock number to write to
493  * @offset: offset within the logical eraseblock where to write
497  * logical eraseblock @lnum.
500  * the physical eraseblock write operation fails, the logical eraseblock is
544  * ubi_leb_change - change logical eraseblock atomically.
546  * @lnum: logical eraseblock number to change
550  * This function changes the contents of a logical eraseblock atomically. @buf
551  * has to contain new logical eraseblock data, and @len - the length of the
552  * data, which has to be aligned. The length may be shorter than the logical
553  * eraseblock size, ant the logical eraseblock may be appended to more times
588  * ubi_leb_erase - erase logical eraseblock.
590  * @lnum: logical eraseblock number
592  * This function un-maps logical eraseblock @lnum and synchronously erases the
625  * ubi_leb_unmap - un-map logical eraseblock.
627  * @lnum: logical eraseblock number
629  * This function un-maps logical eraseblock @lnum and schedules the
634  * Unlike erase, the un-map operation does not guarantee that the logical
636  * example, if several logical eraseblocks are un-mapped, and an unclean reboot
637  * happens after this, the logical eraseblocks will not necessarily be
642  * In other words, when un-mapping a logical eraseblock, UBI does not store
643  * any information about this on the flash media, it just marks the logical
645  * eraseblock is physically erased, it will be mapped again to the same logical
649  * logical eraseblock has to be re-written. Then it is much more efficient to
651  * new data. Note, once new data has been written to the logical eraseblock,
653  * unclean reboot happens after the logical eraseblock has been un-mapped and
681  * ubi_leb_map - map logical eraseblock to a physical eraseblock.
683  * @lnum: logical eraseblock number
685  * This function maps an un-mapped logical eraseblock @lnum to a physical
687  * function the logical eraseblock @lnum will be empty (contain only %0xFF
692  * damaged because of an interrupted update, %-EBADMSG if the logical
720  * ubi_is_mapped - check if logical eraseblock is mapped.
722  * @lnum: logical eraseblock number
724  * This function checks if logical eraseblock @lnum is mapped to a physical
725  * eraseblock. If a logical eraseblock is un-mapped, this does not necessarily
727  * logical eraseblock may become mapped to the physical eraseblock it was last
777  * @lnum: logical eraseblock number to flush for
779  * This function executes all pending works for a particular volume id / logical
781  * a wildcard for all of the corresponding volume numbers or logical