Lines Matching full:logical

86  * Logical eraseblock erase
89  * To erase a logical eraseblock, the %UBI_IOCEBER ioctl command of the
91  * unmaps the requested logical eraseblock, makes sure the corresponding
94  * Atomic logical eraseblock change
97  * Atomic logical eraseblock change operation is called using the %UBI_IOCEBCH
103  * Logical eraseblock map
106  * To map a logical eraseblock to a physical eraseblock, the %UBI_IOCEBMAP
108  * expected to be passed. The ioctl maps the requested logical eraseblock to
109  * a physical eraseblock and returns.  Only non-mapped logical eraseblocks can
110  * be mapped. If the logical eraseblock specified in the request is already
113  * Logical eraseblock unmap
116  * To unmap a logical eraseblock to a physical eraseblock, the %UBI_IOCEBUNMAP
117  * ioctl command should be used. The ioctl unmaps the logical eraseblocks,
124  * Check if logical eraseblock is mapped
127  * To check if a logical eraseblock is mapped to a physical eraseblock, the
322  * The @alignment field specifies the required alignment of the volume logical
323  * eraseblock. This means, that the size of logical eraseblocks will be aligned
325  *	(UBI device logical eraseblock size) mod (@alignment) = 0.
327  * To put it differently, the logical eraseblock of this volume may be slightly
330  * available space of logical eraseblocks.
334  * an integer number of blocks in logical eraseblocks of this UBI volume. With
410  * @lnum: logical eraseblock number to change
411  * @bytes: how many bytes will be written to the logical eraseblock
434  * @lnum: logical eraseblock number to unmap