Lines Matching full:physical

105  * ubi_io_read - read data from a physical eraseblock.
108  * @pnum: physical eraseblock number to read from
109  * @offset: offset within the physical eraseblock from where to read
112  * This function reads data from offset @offset of physical eraseblock @pnum
219  * ubi_io_write - write data to a physical eraseblock.
222  * @pnum: physical eraseblock number to write to
223  * @offset: offset within the physical eraseblock where to write
227  * of physical eraseblock @pnum. If all the data were successfully written,
229  * error code. If %-EIO is returned, the physical eraseblock most probably went
265 		 * We write to the data area of the physical eraseblock. Make  in ubi_io_write()
312  * do_sync_erase - synchronously erase a physical eraseblock.
314  * @pnum: the physical eraseblock number to erase
316  * This function synchronously erases physical eraseblock @pnum and returns
318  * %-EIO is returned, the physical eraseblock most probably went bad.
364 /* Patterns to write to a physical eraseblock when torturing it */
368  * torture_peb - test a supposedly bad physical eraseblock.
370  * @pnum: the physical eraseblock number to test
372  * This function returns %-EIO if the physical eraseblock did not pass the
433 		 * physical eraseblock which means something is wrong with it.  in torture_peb()
445  * @pnum: physical eraseblock number to prepare
521  * ubi_io_sync_erase - synchronously erase a physical eraseblock.
523  * @pnum: physical eraseblock number to erase
524  * @torture: if this physical eraseblock has to be tortured
526  * This function synchronously erases physical eraseblock @pnum. If @torture
527  * flag is not zero, the physical eraseblock is checked by means of writing
529  * the physical eraseblock is erased more than once.
533  * codes in case of other errors. Note, %-EIO means that the physical
571  * ubi_io_is_bad - check if a physical eraseblock is bad.
573  * @pnum: the physical eraseblock number to check
575  * This function returns a positive number if the physical eraseblock is bad,
600  * ubi_io_mark_bad - mark a physical eraseblock as bad.
602  * @pnum: the physical eraseblock number to mark
681  * @pnum: physical eraseblock to read from
686  * This function reads erase counter header from physical eraseblock @pnum and
732 		 * 0xFF. If yes, this physical eraseblock is assumed to be  in ubi_io_read_ec_hdr()
736 			/* The physical eraseblock is supposedly empty */  in ubi_io_read_ec_hdr()
797  * @pnum: physical eraseblock to write to
800  * This function writes erase counter header described by @ec_hdr to physical
806  * case of failure. If %-EIO is returned, the physical eraseblock most probably
965  * @pnum: physical eraseblock number to read from
969  * This function reads the volume identifier header from physical eraseblock
1049  * @pnum: the physical eraseblock number to write to
1053  * physical eraseblock @pnum. This function automatically fills the
1058  * case of failure. If %-EIO is returned, the physical eraseblock probably went
1094  * self_check_not_bad - ensure that a physical eraseblock is not bad.
1096  * @pnum: physical eraseblock number to check
1098  * This function returns zero if the physical eraseblock is good, %-EINVAL if
1120  * @pnum: physical eraseblock number the erase counter header belongs to
1159  * @pnum: the physical eraseblock number to check
1203  * @pnum: physical eraseblock number the volume identifier header belongs to
1244  * @pnum: the physical eraseblock number to check
1294  * @pnum: physical eraseblock number the data were written to
1295  * @offset: offset within the physical eraseblock the data were written to
1359  * @pnum: the physical eraseblock number to check
1360  * @offset: the starting offset within the physical eraseblock to check
1364  * @offset of the physical eraseblock @pnum, and a negative error code if not