Lines Matching full:physical

92  * ubi_io_read - read data from a physical eraseblock.
95  * @pnum: physical eraseblock number to read from
96  * @offset: offset within the physical eraseblock from where to read
99  * This function reads data from offset @offset of physical eraseblock @pnum
206  * ubi_io_write - write data to a physical eraseblock.
209  * @pnum: physical eraseblock number to write to
210  * @offset: offset within the physical eraseblock where to write
214  * of physical eraseblock @pnum. If all the data were successfully written,
216  * error code. If %-EIO is returned, the physical eraseblock most probably went
252 		 * We write to the data area of the physical eraseblock. Make  in ubi_io_write()
299  * do_sync_erase - synchronously erase a physical eraseblock.
301  * @pnum: the physical eraseblock number to erase
303  * This function synchronously erases physical eraseblock @pnum and returns
305  * %-EIO is returned, the physical eraseblock most probably went bad.
351 /* Patterns to write to a physical eraseblock when torturing it */
355  * torture_peb - test a supposedly bad physical eraseblock.
357  * @pnum: the physical eraseblock number to test
359  * This function returns %-EIO if the physical eraseblock did not pass the
420 		 * physical eraseblock which means something is wrong with it.  in torture_peb()
432  * @pnum: physical eraseblock number to prepare
508  * ubi_io_sync_erase - synchronously erase a physical eraseblock.
510  * @pnum: physical eraseblock number to erase
511  * @torture: if this physical eraseblock has to be tortured
513  * This function synchronously erases physical eraseblock @pnum. If @torture
514  * flag is not zero, the physical eraseblock is checked by means of writing
516  * the physical eraseblock is erased more than once.
520  * codes in case of other errors. Note, %-EIO means that the physical
565  * ubi_io_is_bad - check if a physical eraseblock is bad.
567  * @pnum: the physical eraseblock number to check
569  * This function returns a positive number if the physical eraseblock is bad,
594  * ubi_io_mark_bad - mark a physical eraseblock as bad.
596  * @pnum: the physical eraseblock number to mark
675  * @pnum: physical eraseblock to read from
680  * This function reads erase counter header from physical eraseblock @pnum and
726 		 * 0xFF. If yes, this physical eraseblock is assumed to be  in ubi_io_read_ec_hdr()
730 			/* The physical eraseblock is supposedly empty */  in ubi_io_read_ec_hdr()
791  * @pnum: physical eraseblock to write to
794  * This function writes erase counter header described by @ec_hdr to physical
800  * case of failure. If %-EIO is returned, the physical eraseblock most probably
954  * @pnum: physical eraseblock number to read from
958  * This function reads the volume identifier header from physical eraseblock
1038  * @pnum: the physical eraseblock number to write to
1042  * physical eraseblock @pnum. This function automatically fills the
1047  * case of failure. If %-EIO is returned, the physical eraseblock probably went
1083  * self_check_not_bad - ensure that a physical eraseblock is not bad.
1085  * @pnum: physical eraseblock number to check
1087  * This function returns zero if the physical eraseblock is good, %-EINVAL if
1109  * @pnum: physical eraseblock number the erase counter header belongs to
1148  * @pnum: the physical eraseblock number to check
1192  * @pnum: physical eraseblock number the volume identifier header belongs to
1233  * @pnum: the physical eraseblock number to check
1283  * @pnum: physical eraseblock number the data were written to
1284  * @offset: offset within the physical eraseblock the data were written to
1348  * @pnum: the physical eraseblock number to check
1349  * @offset: the starting offset within the physical eraseblock to check
1353  * @offset of the physical eraseblock @pnum, and a negative error code if not