Lines Matching full:eraseblock

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
92  * physical eraseblock is successfully erased, and returns.
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
111  * mapped to a physical eraseblock, the ioctl fails and returns error.
113  * Logical eraseblock unmap
116  * To unmap a logical eraseblock to a physical eraseblock, the %UBI_IOCEBUNMAP
118  * schedules corresponding physical eraseblock for erasure, and returns. Unlike
119  * the "LEB erase" command, it does not wait for the physical eraseblock being
122  * physical eraseblock after the UBI is run again.
124  * Check if logical eraseblock is mapped
127  * To check if a logical eraseblock is mapped to a physical eraseblock, the
281  * amount of eraseblock UBI reserves for handling new bad blocks. If the device
331  * eraseblock. This means, that the size of logical eraseblocks will be aligned
333  *	(UBI device logical eraseblock size) mod (@alignment) = 0.
335  * To put it differently, the logical eraseblock of this volume may be slightly
418  * @lnum: logical eraseblock number to change
419  * @bytes: how many bytes will be written to the logical eraseblock
442  * @lnum: logical eraseblock number to unmap