Lines Matching full:logical
72 * Logical eraseblock erase
75 * To erase a logical eraseblock, the %UBI_IOCEBER ioctl command of the
77 * unmaps the requested logical eraseblock, makes sure the corresponding
80 * Atomic logical eraseblock change
83 * Atomic logical eraseblock change operation is called using the %UBI_IOCEBCH
89 * Logical eraseblock map
92 * To map a logical eraseblock to a physical eraseblock, the %UBI_IOCEBMAP
94 * expected to be passed. The ioctl maps the requested logical eraseblock to
95 * a physical eraseblock and returns. Only non-mapped logical eraseblocks can
96 * be mapped. If the logical eraseblock specified in the request is already
99 * Logical eraseblock unmap
102 * To unmap a logical eraseblock to a physical eraseblock, the %UBI_IOCEBUNMAP
103 * ioctl command should be used. The ioctl unmaps the logical eraseblocks,
110 * Check if logical eraseblock is mapped
113 * To check if a logical eraseblock is mapped to a physical eraseblock, the
289 * The @alignment field specifies the required alignment of the volume logical
290 * eraseblock. This means, that the size of logical eraseblocks will be aligned
292 * (UBI device logical eraseblock size) mod (@alignment) = 0.
294 * To put it differently, the logical eraseblock of this volume may be slightly
297 * available space of logical eraseblocks.
301 * an integer number of blocks in logical eraseblocks of this UBI volume. With
377 * @lnum: logical eraseblock number to change
378 * @bytes: how many bytes will be written to the logical eraseblock
401 * @lnum: logical eraseblock number to unmap